What it gives
An agent performs a task on the board from a short description: it builds a diagram from words or turns a selection into cards. The work runs on the server, not in your tab.
When to use
- You need to turn text into a diagram quickly.
- You need to lay out selected notes as kanban cards.
- You need to repeat the same action on a schedule.
How it works
An agent is a separate principal owned by a person. It has no rights of its own: a task receives the owner's access at the moment it runs.
The order: an organisation administrator enables agents, you create an agent, set a task with a description and a budget, and the server runs it. A diagram skill calls the model and writes the journal; a cards skill runs without a model and leaves an agent-write audit record. Changes arrive as a change set — a package of operations with progress; you can stop it and resume it.
The budget is mandatory: a task without a limit on tokens, cost, actions or time is not created.
Example
Input: a board and a selection of eight notes. Action: the task "turn the selection into cards", a budget of 40 actions. Result: eight cards, an audit record and an event for the webhook.
What you can configure
The agent (name, state), the task budget, the skill, the schedule. Provider keys are stored in the organisation or with the person and are never returned to the interface.
Limitations
- Agents are off by default; an organisation administrator enables them.
- A task can be set only from an account with edit permission on the board.
- An agent cannot do more than the person on whose behalf it acts.
- Agent records produce events, but object changes and deletions do not.
Practical instructions
Connect an integration — how to collect agent activity through events.