Donezo logoDonezo Download

Agents

Where your agents live, how you work with them, and how they pass work to each other.

Workspaces and groups

A workspace is a set of agents that can message each other. Agents in different workspaces cannot, unless you move one across. A group is only a label that keeps workspaces tidy, such as "work" and "hobby".

The canvas

The Canvas tab of a workspace shows every agent as a card.

The canvas of the acme-shop workspace. A director card and a QA reviewer card sit in a shared frame with a dashed amber arrow between them. The director is selected and its panel is open on the right.
Two agents in the same project folder share a frame. The dashed arrow is a queued message.

Sub-agents and verifiers do not get cards. They appear in the director's panel and on the Team tab.

Terminal cards

Each card holds a live terminal running the agent's CLI, in its project folder. Type in it as you would anywhere else.

The header shows the status dot, the name, and the model and effort. The dropdown on the right chooses which past session of this folder the card resumes. The strip on the left has:

A Claude card's header also shows how full its context is and how much of it came from the prompt cache, for example 14% · cache 90%. Hover it for the token count and cost. The top bar shows your Claude plan usage, 5h 11% · week 32%, and turns amber at 80%. The numbers come from Claude Code's status line, so inside the terminal you see the same line at the bottom. If you already set up your own status line, Donezo leaves it alone, and that card's meter updates only from background runs. Antigravity cards have no meter.

One conversation, one writer. A message for an agent whose terminal is open is typed into that terminal after its current turn ends and you have stopped typing. A half-typed line is never mixed in: the message waits until you send or clear it. The card header counts the messages that are waiting. If a background run is going when you open the terminal, it says terminal opens when it finishes and opens by itself. Close the terminal and waiting messages run in the background again. An Antigravity terminal cannot tell Donezo when a turn ends, so a message for it closes the terminal, runs in the background, and the terminal reopens afterwards.

The agent panel

Click a card to open its panel on the right. Double-click a card's name, or use the pencil in the panel, to rename it; the old name keeps working for agents that remember it.

The box at the bottom sends the agent a message as a background run.

The editor

The editor button on an agent card opens that agent's project in a card beside its terminal: files on the left, tabs on top, a status bar at the bottom. It looks like VS Code and uses Vim's modes. Underneath it is Neovim with a bundled setup, so there is nothing to configure, and your own Neovim and tmux setups are not read or changed.

The editor card on the acme-shop project. A file tree with icons and git status letters is on the left, tabs for orders.py and cart.py are on top, Python code is in the middle. A blue status bar at the bottom shows the NORMAL mode label and the hint Press i to type, Esc to stop, F1 for actions.

The first time, the card says Downloading the editor… while it fetches about 12 MB from GitHub. It opens by itself, and later opens skip this step. If the download fails, the card says why: see what to do.

Click a file, press i and type. Press Esc when you stop, then save with :w or Ctrl S. The editor is always in one of three modes, named at the left of the status bar:

Prefer to just type? Turn off Vim modes. A dot in place of a tab's × means unsaved changes. Closing that tab asks whether to save, with buttons to click.

ActionKeys
See every action, searchableF1
SaveCtrl S or :w
Find a file by nameCtrl P
Search all filesCtrl Shift F or F4
Find in this file/
Show or hide the sidebarCtrl B
Undo, redou or Ctrl Z, Ctrl R
Select allggVG
Copy, cut and paste inside the editory, d, p
Paste from your browser's clipboardCtrl Shift V
Comment a line or selectiongc or Ctrl /
Indent, outdent>, <
Close the tabClick its ×, or Alt W
Next tab, previous tabClick it, or Alt . and Alt ,
Work in the file tree: new, rename, deleteF3, then a, r, d; Esc to return

Everything else is plain Vim: counts, operators, registers, : commands, and Ctrl A, Ctrl X on numbers. Space is the leader key, with mappings for files, search and git.

Ctrl V follows the mode: it starts a block in Normal and Visual, and pastes from your browser's clipboard in Insert, on the : line and in a terminal. To insert a key literally, use Ctrl Q. Ctrl C on a Visual selection copies it to your browser's clipboard.

Ctrl W, Ctrl T and Ctrl N belong to your browser, so use :wincmd for Vim's window commands. Ctrl K opens the dashboard's command palette. Copying needs the page to be on localhost or HTTPS, because browsers only let those pages write to the clipboard.

Language features start by themselves when a server such as pyright or gopls is already installed. Without one the editor still colours code by file type, and shows no error.

Source Control

The tabs at the top of the card switch between Files and Source Control. With one git repository, Source Control opens the diff straight away. A project can hold several repositories, side by side or one inside another. Then you get a list of each one with its branch and number of changes, and clean ones say clean. Repositories inside folders like node_modules are left out.

Source Control in the editor card. A panel lists the backend repository on branch main with 3 changes and the web repository on branch feature/login with 1 change, each with its changed files and a status letter.

Click a file to see its diff, or a repository to see all of its changes. ← Back at the top right returns to the list, and R in the list refreshes it. A folder with no repository says so.

Turn off Vim modes

Press F1 and pick Turn off Vim modes to type straight away, as in VS Code. Esc no longer stops typing. Click to place the cursor, drag to select, and typing replaces the selection. The choice is remembered. Pick Use Vim modes to switch back. F1 always lists the keys for the style you are in.

ActionKeys with Vim modes off
Find in this fileCtrl F
Undo, redoCtrl Z, Ctrl Y
Select allCtrl A
Copy, cut, paste, with your browser's clipboardCtrl C, Ctrl X, Ctrl V
Indent, outdentTab, Shift Tab
Work in the file tree: new, rename, deleteF3, then A, F2, Delete; Esc to return

Keeping your work

With tmux installed, reloading the page or restarting the server keeps your open files and unsaved text. Closing the card with its × ends the editor and loses unsaved text, and it asks first. Without tmux, which includes Windows, closing or reloading the browser tab also ends the editor, as the card's tooltip says, so save first.

Quitting from inside, with :q, :qa, :wq or ZZ, closes the card. The file tree does not count as a window, so :q on the last file quits. With unsaved text Vim refuses and says so. The editor button opens the card again.

New agent

New agent is in the sidebar, on Home, and in the command palette. It asks for three things: see Start a director for a walk-through.

Models and effort

The model decides which CLI runs the agent.

Effort is how hard the model thinks before answering. Higher costs more and takes longer. It is under Effort (reasoning) in the dialog, and the dialog only offers levels that model accepts: up to max on Claude and up to high on Gemini. Some Gemini models carry a fixed level in their name. The default is high. You can change both later in the agent's Overview.

Agent-to-agent handoffs

Agents hand work to each other with the send_signal tool from the signal server. Donezo delivers the message as a new run for the receiver.

Before asking, an agent can look up what its colleagues already know with search_knowledge. It searches the memory files and recorded decisions of the agents in the same workspace and names who wrote each result. It only reads, and never looks in other workspaces. Each search (the words asked and which items came back) is logged in the local database so the Knowledge tab can draw it.

To see that knowledge at a glance, open the Knowledge tab. It draws the workspace's agents, their memory files and their recorded decisions as a graph. Lines show who owns what, which memories link to each other. Arrows between agents show who asked whom for something (solid, expects a reply) and who reported to or answered whom (dashed); thicker means more messages. Thin dotted "looked up" lines run from an agent to the memories and decisions its searches found. Hover an arrow or line for its latest messages or searches, hover a node for its details (an agent also lists its recent searches that found nothing), and drag it around; the tab never changes anything.

You can message an agent too: use the box in its panel, or Send a message in Activity.

Command palette

Press Ctrl K (⌘ K on a Mac), or click Search or run… at the top of the sidebar. It works even with the cursor inside a terminal.

The command palette over Home. It lists items that need you, then agents and workspaces, with a search box on top and keyboard hints at the bottom.
The palette lists what needs you first, then agents, workspaces and actions.

Use ↑ ↓ to move, ↵ to open and esc to close. Typing narrows the list and highlights the best match.