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.
AgentWitch is not one cloud bot everyone shares. Each person keeps an agent on their computer. 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 computer, 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 a project and choose New task
- Projects → open a project → New task (or /projects?intent=new-task)
- Under Who receives this task, pick your company — not My Mac (self)
- Select the teammate who owns the repo on their computer
- Pick their published workflow (e.g. Repo branch standup)
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 Reports in their browsers
3. Their computer runs; you watch the terminal
- After dispatch (or approval), command.claude.run reaches their AgentWitch client
- With session continuation, Claude reuses the warmed writer session
- Terminal stream chunks appear in your browser while they work locally
- Result lands in Reports for both requester and executor views
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 Reports in their browser to review the prompts and results for their runs.