The Global Assistant
The global Assistant sits above every project on this machine and on the hosts it may work on: how to open it, which hosts it reaches, its fixed tool set, what it can do to agents it did not launch, arming a notice for the next agent that waits, and its confirmations.
What it is
The global Assistant is one Daintree Assistant above every project on this machine and on the hosts you let it work on. It has no project of its own. Each project keeps its own assistants, which plan the work and launch workers into worktrees; the global Assistant sits above them, reads the state of agents across every project and host in one call, steers work wherever it runs, and can arm a notice for the next agent that starts waiting.
It runs Claude Code, Codex or Antigravity on your own subscription, like your project assistants. What sets it apart is its reach and its limits: a fixed, narrower tool set that reaches each project through that project's host, under the host's ownership rules.
Opening it
Open the Assistant panel (Command-L Control-L Control-L ) and choose Global in the header's Project and Global switch, or right-click the toolbar's Assistant button and pick Open global assistant. Canopy can show it too. Either way it doesn't start on its own: press Start global assistant. It picks up its last conversation when there is one, provided it runs on the same agent as before.
There is exactly one global Assistant, with one conversation and no session picker. Every window on this machine shows the same terminal, and one window at a time holds its input. Another window says Another window has this assistant's input and offers Take input; when the window holding it closes, input passes to the window you focused most recently that can type there. The run belongs to the app, not to a window, so closing the window you started it in or switching project leaves it running. A window on a remote host can't show it: open it from a window on this machine.
The header's … menu has Clear conversation, which starts a new one, and Stop global assistant, which stops it in every window. Both forget the conversation. Quitting Daintree ends the run and keeps the conversation for the next start; nothing restarts it for you after a restart or an update. While the panel shows a project, the Global side of the switch carries a mark when the global Assistant is working.
Which agent runs it
It uses the Assistant settings your project assistants use: the agent and model under Agent, the custom CLI arguments, the bypass switch and Daintree confirmations. It runs the Assistant agent chosen there, or your default agent, or failing those another supported agent that is installed and new enough. When a change to those settings changes the agent it would run, it stops, and the next start uses the new one. Give it a name and emoji of its own under Name and emoji; the name replaces Global on the switch.
Which hosts it reaches
This machine is always one of them, as the host local: the global Assistant reaches its projects whenever they are reachable. A remote host is reached only while two switches agree, one on each machine:
| Machine | Setting | Default |
|---|---|---|
| This machine, per host | Settings > Hosts, the host's page, Let the assistant work on this host (macOS and Linux) | On |
| The host | Settings > Daintree Assistant > Security > Let other machines' assistants work here (where Host mode is available) | On |
With the first one off, a call to that host is refused: only you can turn it back on. The host's switch lets an assistant on a machine it serves run Daintree's tools there, within the host's own tool sets, including finding, starting and messaging the assistants that run there. Project assistants reach hosts through the same two switches.
When a host's link is down, the global Assistant can try to bring it back: it wakes the host where you set up a wake and starts Daintree there where Host mode is on, waits up to two minutes and reports what it saw. It never changes the host's settings to do it.
Its tool set
The global Assistant names no project, so it can't call a project's tools directly. While Daintree control is on, its own daintree server gives it seven tools, whatever the Tool set setting says:
| Tool | What it does |
|---|---|
host.list | The hosts it knows, local included, whether each is reachable, and each reachable host's projects and, when asked, their agents. |
host.call | Runs one of a project's tools on that project's host. |
host.status | Reads the state of agents in up to 64 projects on any hosts in one answer, with their handbacks and, if asked, the last lines of their screens. Each project is read as host.call would read it there. |
host.watch | Arms one notice for a host's link, its capacity, or the next agent that starts waiting (see below). |
host.bringBack | Tries to wake a host whose link is down and start Daintree there. |
host.settings | Reads a remote host's own settings and changes a short list of them, such as its default agent and Canopy. Every change is previewed first and asks you, unless you handed host settings changes over under Ask, except for…. |
mcp.surface | Reports what the server took its session for, so it can tell when something other than the global Assistant answered. |
Everything else goes through host.call, and the host admits it the way it would admit another machine's assistant. The call runs at your Tool set, so it can do no more on a host than your assistant could here, and less where the host says so. On top of that, the global Assistant has an allowlist of its own. It can read worktrees, issues, pull requests, CI and terminals; create worktrees and launch agents into them; at Full, run recipes and resource teardowns, which are confirm-gated; start and message the project assistants; and act on agents through the owned tools described below.
Some project tools it never gets, because they act on something it neither launched nor was handed: project.runCommand and project checks, the unscoped terminal tools (send, keys, close, kill, restart), worktree.delete for any worktree, worktree labels and the active worktree, resource provisioning, Dev Preview, plugin reloads, CopyTree to the clipboard, the diagnostics review, reopening your own agent sessions, and the project's links, which are its own assistant's to keep.
The Allow this tool banner never appears for the global Assistant, and Settings > Daintree Assistant shows its live session without grants: Its tool set and grants can't be shown or approved here.
Agents it didn't launch
On worktrees and restarts the global Assistant acts only on what it launched: worktree.deleteOwned, worktree.retireOwned and the owned restarts refuse anything else, and handing it a terminal doesn't change that. Reaching agents someone else launched is narrower and checked on every call:
- Prompts, keys and interrupts reach any agent terminal in a project it can reach, but each names the run it read. If the agent was restarted or replaced since, the call is refused, and if someone has typed into it since the agent last settled, their draft is left alone and the call is refused. A plain shell or another assistant is refused too. A slash command goes in only as one of a few fixed forms, such as
/compact. - A busy agent refuses a send. The global Assistant can ask Daintree to hold one message per agent and type it at that agent's next idle prompt, for 30 minutes by default. It is dropped if anyone else sends the agent input, the run changes or the global Assistant's session ends.
- Revealing an agent's panel to you writes nothing, so it never waits on a draft.
- A Claude Code update an agent has installed can be applied by typing
/restartonce at its empty prompt, after you approve. - Closing reaches an agent it didn't launch only when nothing is typed in it. One whose stop handed the work back closes as your Daintree confirmations allow; one stopped on an error, such as a usage limit, asks you every time. Working agents, agents waiting on an approval or a question, drafts and plain shells are refused.
After a restart, it can list each project's closed agent sessions and reopen one into a panel of its own. Sessions you closed yourself are left alone. To give it a terminal outright, right-click the terminal and use Hand to orchestrator > Global Assistant; it can then type and press Enter, interrupt and read the last message, from any project, but still can't close it.
Hearing when agents wait
Rather than polling, the global Assistant arms a notice with host.watch and ends its turn. Armed with agentsWaiting, the notice fires for the next agent that starts waiting on an approval or a question, on every host it controls and on this machine, or on one host or project. Daintree types the notice into the global Assistant's prompt when it fires. Agents already waiting when it arms are returned straight away instead, for it to handle then.
Each notice is one shot: it arms again after handling one. The watch only listens to what this machine already hears from its hosts. It never connects to, holds or wakes a host, and it acts on nothing when it fires. The same tool watches a host's link (for work held until a host comes back) or its memory and CPU. A watch lasts 30 minutes by default and at most six hours. Project assistants can arm the same watch; the global Assistant is the one with no project of its own to tend, so it is the natural place to hold it.
Messages from project assistants
A project assistant on this machine can raise work that reaches past its project with the global Assistant. It can find it and send it a message, and read whether it is busy, but not read its screen. The message arrives prefixed From the Daintree Assistant of the project …, so the global Assistant treats it as another assistant asking, not as you. It decides within what you asked of it, brings you what only you can settle, and answers with the handback the project assistant asked for or by messaging that assistant back.
Confirmations
A confirm-gated action runs on the host where it is called, and asks in the window on this machine that holds the global Assistant's input, or failing that the last window to show it. With no window showing it, nobody can be asked, and the call doesn't run unless your settings already allow it. Your Daintree confirmations setting on this machine applies to its calls on every host, as it does to a project assistant's. A confirmation nobody answered never counts as a yes: the call fails, and the global Assistant says it can't tell whether you declined or missed it.
Some actions ask whatever the setting says: adding agent accounts, closing an agent stopped on an error, and changing a host's settings (which Ask, except for… can hand over, but Never ask doesn't cover).