Agents
Agents that own the work.
An Access agent isn’t a chatbot that answers questions. It has a job, the connections that job needs, and the notes it should already know. You talk to it in Chat. It does the work — queries, messages, tickets, the next step — and you stay in the loop.
The default Access agent is ready as soon as you open Chat. It can see everything you’ve connected. A named agent is for a job you want someone to keep: an on-call digest, a schema steward, a person who already knows how you like the summary.
How to create one
Ask Chat:
Make an agent that queries Postgres and posts a Slack summary when error rates spike.
Or create one in Agents. Give it a name, a short description, the connections it should use, and the instructions.
Pick it in the Chat composer, or type @ on a new chat and choose the agent. After the first message, the thread stays on that agent — start a new chat to switch.
What it can do
Use your connections. Search your notes. Remember facts from past chats when dreaming is on. Write a workflow when the job should become code. Inspect what already ran.
In Chat, the agent is told which connections to use. When a workflow asks a named agent for judgment, Access enforces that list.
Open the agent → Memory to see what it has kept, correct a note, or turn dreaming off. See Memory.
Bring your own
You can also point Cursor or Claude at Access. They use the same connections, through one MCP server. See Bring your own agents.
When to use which
| Use | Choose |
|---|---|
| One question, any connection | Default Access agent |
| A job someone should keep | Named agent |
| Steps you already know, on a schedule | A workflow — code, not a canvas |
A workflow can ask an agent as a step. An agent can draft and run a workflow. They work together; they are not the same thing.