On this page

Coding agents in your dock

Moor watches your Claude Code and Codex sessions — in the terminal, in VS Code, and in the Claude and ChatGPT apps — and Cursor, Windsurf, Gemini CLI, Aider and OpenCode, by reading the files each keeps on your Mac, and Trae, through hooks you connect (see Trae). It only reads them, and nothing is sent anywhere.

The Agents widget: “storefront” is editing a file, “api” needs you; beside it, the icon-size widget with a badge of 1
At a glance: which project's agent is working, and which one is waiting for you.
See which agent needs you, and jump straight to it.

Setting it up

Add the Agents widget, or Agent Dock (see below), to a dock (⌃⌥E → Add). That's it — there's nothing to connect, except for Trae. Choose which agents it shows, and whether to be notified when an agent finishes, by clicking the widget while editing.

What you see

Agent Dock

Agent Dock is a second widget for the two agents Moor can read best, Claude Code and Codex. It lists every session from the last 30 minutes as a row, with a state and the agent's last line:

StateMeans
Waiting for youThe agent finished its turn or was interrupted, in the last ten minutes
FailedIt was working, then went silent for ten minutes: stuck, or its app quit mid-turn
WorkingIt's busy now, and the row says what it's doing
DoneIt finished more than ten minutes ago, or its files can't say

Rows are sorted with what needs you first, and each state has its own symbol, so you never rely on colour. The icon size shows a number for the sessions waiting for you; the wide sizes show the headline (“2 waiting for you”) and the projects; click for the full list. Click a row to jump to that session, the same way the Agents widget does: sessions in the Claude app and the Codex app open on that exact chat, and sessions in a terminal or editor bring their window forward.

Agent Dock only reads. There's no approve or stop button. Everything it shows comes from files the agents keep on your Mac, and nothing leaves it.

The Agents widget above shows more tools (Cursor, Windsurf, Gemini CLI, Aider, OpenCode and Trae as well) and badges the apps they run in. Use either, or both.

What each agent shows

Moor only claims what an agent's own files show. Where they can't tell “busy” from “waiting for you”, the session says Active 3m ago (or Open) instead, and never gets a badge or a notification.

AgentRead fromWorkingNeeds you
Claude Code~/.claude/projectsYesYes
Codex~/.codex/sessionsYesYes
Gemini CLI~/.gemini/tmp/…/chatsYes, while it thinks or runs toolsAfter an error or a cancelled tool. A finished reply shows as Active, because Gemini records a tool call only once it ends, so a reply waiting on your approval looks the same.
Cursor~/.cursor/projects/…/agent-transcriptsNo: shows ActiveOnly when the transcript marks the turn ended (newer versions)
Windsurf~/.codeium/windsurf/cascadeNo: shows ActiveNo. Cascade's conversations are encrypted, so Moor sees only when it was last active. The project is named when exactly one Windsurf workspace is in use.
Aider.aider.chat.history.md in the project, found through the running aiderYes, from your message until its reply is writtenYes, once it has replied. An Aider open but idle for over 30 minutes shows as Open.
OpenCode~/.local/share/opencode/opencode.db (read-only)Yes, from your message until it stops working: tool steps count as workingYes, once its reply is finished (or failed)
TraeIts hooks, once connected (below)Yes, from your message through every tool stepYes, when it finishes or asks for your OK

Older Gemini CLI versions keep only the prompts you typed (logs.json), so those sessions show as Active.

Trae

Trae keeps its agent's sessions encrypted, so Moor learns about them from Trae's own hooks instead:

  1. Click the Agents widget while editing, and press Connect Trae. Moor adds its hooks to ~/.trae/hooks.json, next to any hooks already there.
  2. In Trae, switch hooks on once: the gear icon at the top right → Hooks → Configured Hooks, then Enable. Trae asks before it runs any hooks, and Moor can't do this step for you.

Each hook saves what Trae's agent just did (your prompt, a tool step, finished, or waiting for your OK) to a folder under /tmp that only you can read. That's the one place Trae's sandbox lets a hook write, and Moor reads it from there. Disconnect removes only Moor's hooks.

Jumping to an agent

Moor finds the agent's process, follows it up to the app it runs in, and raises the window titled for that session or folder. VS Code, Cursor and Windsurf focus the window with that folder open. Needs Accessibility for picking the right window.

During calls

On a call, Moor holds agent sounds and bounces until it ends (Settings → Automation → During calls), so a finished agent doesn't interrupt your meeting.

Shortcuts

“Agents Waiting for Me” returns the sessions that need you — handy for Siri or a menu bar Shortcut. Search (⌃⌥F) also finds agent sessions by project.

Letting agents control Moor

Agents can also set Moor up for you: “put a dock on the left with Xcode, Terminal and the Agents widget”. Add Moor's MCP server to Claude Code with claude mcp add moor -- moor mcp (Codex, Cursor and others work too). See MCP and API.

This page as Markdown: /docs/agents.md