Team dispatch · 6 min read

Agent to agent inside your company

You send the task from the browser. Your teammate's Mac runs Claude on their files.

Agent Witch is not one cloud bot everyone shares. Each person keeps an agent on their Mac. Inside a company group, you become the requester and pick a teammate plus their published workflow — Claude runs on their machine with their repo paths and files.

Featured workflow: Repo branch standup

Template in Marketplace: Repo branch standup (teammate Mac)
Fields: repo path on their Mac, branch name, optional since date
Teammate publishes it to Library; you pick it under their assistant when sending
Try this prompt: summarize commits on feature/checkout for yesterday's standup

1. Open Send a task and choose the company

Home → Send a task (or /?sendTask=1)
Under Who receives this task, pick your company — not My Mac (self)
Select the teammate who owns the repo on their Mac
Pick their published workflow (e.g. Repo branch standup)

Send a task form with company, teammate, and workflow selected — Send a task to Alex Chen at Acme Design Co with the Repo branch standup workflow.

2. Approval when policy requires it

Group dispatch policy can be open or approval
If approval: job stays pending until the executor (or manager) taps Approve
Executor must be online after approval for Claude to start
Both sides see the run in Job history in their browsers

Dispatch approval modal for a teammate task — Pending repo standup request from Jamie Lee.

3. Their Mac runs; you watch the terminal

After dispatch (or approval), command.claude.run reaches their Agent Witch client
With session continuation, Claude reuses the warmed writer session
Terminal stream chunks appear in your browser while they work locally
Result lands in Job history for both requester and executor views

Live terminal showing Claude output on teammate Mac — Standup bullets streaming from Alex's Mac.

Agent-to-agent process (inside one company)

Requester agent (browser): composes prompt, picks executor + capability, sends over WebSocket/API
Company gate: shared group membership and optional approval policy
Executor agent (Mac): receives command.claude.run, streams terminal output back
No mystery VM — executor is always a named person and Mac

How team dispatch stays trustworthy

Team dispatch uses your signed-in company group, memberships, and published capabilities. Each person opens Job history in their browser to review the prompts and results for their runs.