Threads
Create or reopen the conversation that owns the context for a piece of work.
ChuskyDeveloper reference
Build around the agent.
Keep every state visible.
The Chusky API gives your product a clear contract for starting work, streaming progress, asking for approval, and recovering the result. Use it from a trusted server and keep your own customer identity in charge.
The surface
Small primitives. A complete work loop.
Most integrations begin with a thread and a run. Add the surrounding primitives only when your product needs them: files for context, approvals for control, tasks for continuity, and delivery events for follow-through.
Runs
Send an objective, stream progress, inspect tool activity, and receive the final result.
Approvals
Present an exact action for review and continue only after the owner decides.
Files and artifacts
Attach verified inputs and retrieve the documents, images, or exports the agent creates.
Tasks and delivery
Track work that continues beyond the current request and the channels it reaches.
Work with other agents
A handoff can cross the conversation.
Other agents can reach Chusky through MCP and A2A. These are ways to bring a job into the same system of connected tools, budgets, saved work, and human approvals.
An entry point, with a clear identity.
Keep the caller and project scope attached to the work. A handoff should say whose context can be used and which tools are allowed, rather than exposing every connection to every agent.
A result that stays connected.
Keep the job references and progress available to the caller. Longer work can continue with its steps and evidence preserved, rather than disappearing when the first exchange ends.
Request lifecycle
A run is more than a response.
Your interface can render the work as it happens instead of waiting for a single opaque answer.
01
Authenticate
Your server identifies the project and the end user.
02
Start
Chusky accepts the objective and begins a tracked run.
03
Review
An exact approval pauses the run when the action matters.
04
Recover
The final result and artifacts remain available after the stream ends.
Production boundary
Keep credentials and identity on the server.
Project keys authorize your application. The stable end-user identity determines which private threads, files, memories, approvals, and connections the run may use. Never place project keys in browser code.
Project key
Identifies your Chusky project.
User identity
Scopes private work to your authenticated user.
Approval boundary
Keeps consequential actions reviewable.
Run events
Makes progress and recovery renderable.