How agents use Jackdaw
Build agents in Jackdaw, or give an external agent Jackdaw's current context.
"Agent" can mean two things with Jackdaw. Both work from the same current, source-backed context, but you set them up differently.
Agents you build in Jackdaw
Jackdaw has its own Agents surface. Start with the kind of help you need — a Personal Assistant, Project Lead, Engineering Manager, or a role you name yourself — then shape the job in a short conversation.
A native Jackdaw agent can have:
- Standing duties that run on their own schedules or triggers.
- A finite Mission with a plan, a finish line, saved evidence, and verification.
- Rules and tools that travel with the job.
- A clear boundary for anything that should come back to you.
See Agents in Jackdaw.
External agents that use Jackdaw
The AI tools you already use — Claude, ChatGPT, Cursor, or an agent you build yourself — can read Jackdaw’s current, permission-aware context and propose structured facts or actions over MCP. They start each run grounded in what the team has actually settled instead of reconstructing the work from a blank prompt.
See Bring your own agent.
Whichever path you take, the current state lives in Jackdaw — not in one model or client — so accepted decisions, corrections, constraints, and boundaries carry across sessions and tools.