Agents
An agent is any program that does a task's work: a coding tool, your own model loop or a bot that never touches code. With the Jaah Agent SDK you write that program once, register it, and Jaah runs it on your nodes under the same governance as its built-in runners — its log, questions, credentials and usage all land on the task like any other run. The SDK is open source, in the Jaah Agent SDK repository; the connectors every organization shares live in the Jaah Agent Connectors repository.
- How agents work — what an SDK agent is, how Jaah runs it, what Jaah records for it, the security gate, and the failure codes a run can end with.
- Build an agent with the SDK — the quick start: write a hello agent in Python or TypeScript, register it, pick it on a task and run it.
- Agent SDK reference — every field of the manifest, every SDK call and every error.
- Contribute a catalog connector — how a connector reaches the shared catalog, and how to turn one on for your organization.
- Install an agent from the ACP registry — browse the public ACP registry, install an agent at a pinned version, and remove it.
- Change or remove a custom agent — change its ref or folder, refresh, disable or delete it.
- Set a project's default agent — choose the agent that runs a project's tasks when they pick none.
- Fix a custom agent whose refresh failed — read why Jaah could not pin its newest commit, fix it and refresh until it shows Active.
- Check which agents can take work — read the Catalog tab to see which agents are on, what they take and cost, and whether a node and an account can run them.
- Set environment variables on a custom agent — add, change or remove the settings Jaah passes to the agent on every run, such as its model.
- Delete an agent that is still in use — see which projects and tasks still use it, move them to another agent, or disable it instead.
- Limit what intelligent routing can pick — cap the routing mode your projects may use, and the runners and model tiers routing picks from.
- Replace an agent removed from the catalog — pick another agent for the projects and tasks that named a withdrawn connector, so their tasks start again.
- Get an agent your plan leaves out — spot a built-in agent marked Not on plan or a hidden Registry tab, compare it, and get the plan changed.
- Register an agent from a private repository — give your GitHub connection access, pick the repository on New agent and register it.
- Move a custom agent to SDK v2 — bring an agent marked Unsupported back into service: port its repository, refresh it and check it shows Active.
- Check which version an agent runs — read the version and commit Jaah pinned for a custom agent, or a registry agent's installed version.
The tasks an agent runs are ordinary tasks, and it runs on your nodes in a task's worktree.