Skip to Content
Platform
ReferenceUsing a coding agent

Using a coding agent

Your coding agent drives Introspection through the CLI, which also serves its workflows.

Setup

npm install -g @introspection-ai/cli # Node.js 24 or later introspection setup # Pi, Recipes, and a discovery skill for each detected coding agent introspection skills # the workflows the coding agent reads introspection login # you approve in the browser

Mention Introspection in your request so the coding agent uses it:

Use Introspection to create a refund agent.

Workflows

The coding agent loads the workflow that matches your request. Each one works on your agent, the agent you build with Introspection.

create

Builds a new recipe for your agent and tests it locally, including the tests and evals it needs. Use it when you need a new agent, from scratch or from a template.

Use Introspection to create an agent that drafts replies to support tickets and escalates refund requests. Test it locally with representative cases.

migrate

Ports your agent from another framework or host to an Introspection recipe, keeping its approved behavior. Use it when you have an agent built on another framework or host.

Use Introspection to migrate the support agent in ./support-agent to a recipe, keeping its current behavior.

improve

Makes one diagnosed change to your agent’s recipe: its behavior, prompts, tools, configuration, tests, evals, or judges. Use it when your deployed agent misbehaves, or needs a new tool or capability.

Use Introspection to find out why the support agent escalated refunds it should have answered last week, and fix the cause.

optimize

Searches prompts, skills, configuration, and model settings for your agent against a stable eval, and keeps the best candidate. Use it when you want better eval scores, or a cheaper model to match a stronger one.

Use Introspection to optimize the support agent so a cheaper model matches its current eval scores.

deploy

Changes which version of your agent an environment serves, including its runtime, bindings, and credentials. Use it when you want a version to serve staging or production, or to roll one back.

Use Introspection to deploy the support agent, verify it in staging, then release it to production.

operate

Inspects, explains, or changes your agent’s live state, such as bindings, credentials, and connectors, without changing its recipe. Use it when you need to know why one of your agent’s tasks failed, or to change a live binding, credential, or connector.

Use Introspection to explain why yesterday's support agent tasks failed.

Permissions

There is no read-only login, so limit the coding agent with its own permissions.

In .claude/settings.json:

{ "permissions": { "allow": ["Bash(introspection skills:*)", "Bash(introspection conversations get:*)", "Bash(introspection events list:*)"], "deny": ["Bash(introspection runtimes update:*)", "Bash(introspection runtimes delete:*)", "Bash(introspection api-keys:*)", "Bash(introspection members:*)"], "ask": ["Bash(introspection:*)"] } }
Last updated on