Skip to Content
Platform
Get StartedConcepts

Concepts

A short list of terms covers the whole product. Each links to the page that uses it.

Build

TermMeaning
RecipeThe files in Git that define an agent: instructions, skills, tools, MCP servers, judges. The same recipe runs on your machine and in Introspection. Create a recipe
AgentA role in a recipe with a model, instructions, tools, and skills. A recipe can hold several. Agents
PiThe open-source agent harness that runs a recipe, locally and in each task’s sandbox. pi.dev 
RecipesThe Pi package that adds recipe support to Pi. introspection setup installs it.
SkillA recipe skill tells your agent how to do part of its job (Skills). A workflow skill tells your coding agent how to work with Introspection (Using a coding agent).

Run

TermMeaning
RuntimeThe named, deployable agent built from a recipe. In the API, a “runtime group” (runtime_group_id). Deploy your agent
VersionOne immutable build of a runtime from one commit. In the API, runtime_id is a version ID.
Environmentdevelopment, staging, or production. Development runs the files on your machine through introspection dev. Staging and production follow the default branch unless pinned. Test before production
Pin and yankPin fixes the version an environment serves; yank takes a version out of service. Roll back a release
BindingAn endpoint, variable, or credential a runtime gets per environment. The agent can use a credential but never reads it. Bindings
ConnectionAn endpoint in Bindings: a model provider, MCP server, or connector. A user connection is one end user’s authorized account on a connector.
TaskOne unit of agent work, run in its own sandbox.
RunOne turn of a task.
ConversationThe saved transcript of a task, with the same ID. Find a conversation
SandboxThe isolated environment for one task. Its filesystem is temporary. The sandbox
RunnerThe SDK session your app opens against a runtime to start and read tasks. Run tasks from your backend
MemberA person or agent in your organization. Projects & members
End userYour customer’s user that a task acts for (identity.user_id in the SDK, --subject in the CLI). The first task for one creates a customer member. How agents act

Improve

TermMeaning
TraceThe OpenTelemetry record of one turn: model calls, tool calls, and subagents as spans.
Observation and patternAn observation notes behavior in one conversation; a pattern groups observations that recur. Recurring problems
Annotation and datasetLabels and comments on steps of conversations, grouped by tag. Label production steps
Judge and judgementA recipe-owned quality check, and one result of it. Calibrate a judge
EvalA suite of cases replayed against a change before you ship it. Run and compare evals
ExperimentLive traffic split between versions of one runtime, compared with a judge. Run an experiment
Control plane and data planeWhere configuration and identity live, and where agents run and their records are stored. Choose where your data runs

Find it in the dashboard

SidebarWhat you do there
RuntimesSee versions, pin, roll back, yank. Ship
BindingsConnect providers, MCP servers, and connectors; set variables and secrets. Bindings
RepositoriesRegister repositories agents may clone and change. Repositories
ConversationsRead any task end to end. Conversations
Events, PatternsFeedback, observations, judgements, recurring behavior. Patterns
MetricsUsage, reliability, and cost. Metrics
More → Files, UsersOutputs and memory; your end users. Files
DatasetsLabel production examples as a team. Annotate
JudgesPass rates and live settings. Judges
ExperimentsCompare versions on live traffic (shown once a judge exists). Experiments
SettingsProject, Connectors, Applications, API keys. Members and integrations are organization settings. Identity & access
Last updated on