Guides
Step-by-step guides for taking an agent from a local recipe to production and improving it with real evidence.
If Introspection is new to you, begin with the Quickstart, then read how Introspection works. Come back here for the repeatable guides: each one walks through one outcome and links to the relevant concept, SDK, or CLI reference when you need more detail.
The four guides
| Goal | Guide | Outcome |
|---|---|---|
| Build a recipe and move each change to production | Agent development lifecycle | An owned recipe, proven locally, running as an approved production version. |
| Put the agent into your product | Integrate into a full-stack app | A server or browser integration with identity, reconnect, and production feedback. |
| Give the agent your source code | Work with repositories | A runtime that checks out your repositories and can open pull requests against them. |
| Fix what production reveals | Learn from production | Evidence traced to a focused recipe change, and a calibrated measure that keeps it fixed. |
Each guide is one outcome end to end. When a step depends on a platform resource — runtimes, judges, experiments, observations — follow its link for the full explanation and return to keep building.
Create projects and connect GitHub in the dashboard. Use the CLI for recipe, runtime, task, and evidence work. Merge recipe changes through Git when they are ready for production.
Next
- Agent development lifecycle: start a recipe, or move the next change from local development to production.
- Integrate into a full-stack app: connect the runtime to your product and its users.
Related
- How Introspection works: entity definitions and relationships.
- JavaScript SDK: programmatic contracts used by the examples.
- CLI: the commands used throughout the guides.
Last updated on