AGNT5 learning path

Use this path when you are new to AGNT5 and want a clear order through the docs. AGNT5 is organized around three jobs: build durable agentic workflows, run them in managed environments, and improve them from production evidence. Each stage below links to the task pages you need without turning the docs into a course.

1. Run a working workflow

Start with a small project that produces a visible trace: the recorded execution path of a workflow run, including steps, model calls, timing, and cost.

1. Install the CLI: install agnt5, verify the binary, and authenticate.
2. Hacker News digest quickstart: create a workflow project, run it in an AGNT5 Cloud dev environment, and inspect the trace.
3. Build with AI coding agents: give Codex, Claude Code, Cursor, Windsurf, Cline, or Copilot an AGNT5-aware task prompt.

Outcome: you have seen a workflow run and can inspect what happened.

2. Learn the build model

AGNT5 code is built from a few primitives. A workflow is a durable program, a function is a retryable unit of work, an agent reasons and calls tools, and a prompt keeps model instructions versioned with code.

• Workflows: compose checkpointed steps, durable sleep, parallel work, state, and triggers.
• Functions: wrap deterministic work with retries, backoff, timeouts, and trace visibility.
• Agents: configure model instructions, tools, handoffs, and loop limits.
• Tools: expose typed actions that agents can call.
• Prompts: keep prompt text runnable from Python or TypeScript and tied to production versions.

Outcome: you can choose the smallest AGNT5 primitive for the behavior you need.

3. Build locally

Use local development when you are changing workflow behavior and want fast feedback before deploying. Keep secrets outside git, run the worker with hot reload, and trigger runs from Studio, the CLI, or the API.

1. Local development: run agnt5 dev, trigger local runs, and watch traces.
2. Human-in-the-loop: pause workflows for approvals, selections, and follow-up input.
3. Webhooks: receive signed external events and route them into workflows.
4. Integrations: store credentials once and scope them to a workspace, project, or environment.

Outcome: your project runs locally with the inputs, prompts, approvals, events, and credentials it needs.

4. Go live

Move from local development to a managed AGNT5 environment when you need a worker that runs outside your laptop. A deployment is your worker running in AGNT5 Cloud with environment-scoped configuration and observable runs.

1. Deploying: set secrets, deploy a worker, verify it, and trigger a run.
2. Run with AGNT5: understand the run-time surfaces for deployments, runs, traces, logs, and metrics.
3. Event sources: connect Sentry, Stripe, GitHub, Slack, or any Standard Webhooks publisher.

Outcome: your workflow can run in a managed environment and receive production inputs.

5. Operate with trust

After a workflow is live, use AGNT5’s run data to debug behavior and understand reliability. A run is one workflow execution; its trace, logs, metrics, and cost records are the evidence you use to operate it.

• Runs and traces: list runs, describe one run, and open it in Studio.
• Trace inspection: inspect model calls, tool calls, inputs, outputs, retries, and timing.
• Logs: stream deployment logs or fetch logs scoped to a run.
• Metrics: monitor executions, success rate, latency, and LLM cost.

Outcome: you can answer what happened during a production run and where to look next.

6. Improve behavior

Use production evidence to decide whether a prompt, model, or workflow change is better than the current version. Improvement work starts with real runs and ends with a measured decision.

1. Improve with AGNT5: understand datasets, scorers, experiments, and prompt changes.
2. Prompts: commit production prompts and select versions from code.
3. Workflows: structure agentic work so it can be observed and evaluated.

Outcome: you can turn observed behavior into safer prompt, model, and workflow changes.

Next steps

• Quickstart: create and run the first workflow in the path.
• Build with AGNT5: jump into the authoring docs when you know what you want to build.
• Run with AGNT5: deploy and operate a workflow outside local development.
• Improve with AGNT5: use production run data to measure behavior changes.