Chapter 8 — Production and trust

This chapter answers: what runs where, what AgentWitch can see, and what honest limits you should expect in production at https://www.agentwitch.com.

It is written for team leads, security reviewers, and solo makers who want clarity before they pair a Mac or save a Playbook. Vocabulary: Chapter 0.

Trust boundaries below enable all four pillars: easy authoring only works if you know what the composer will touch; learn from usage requires honest Run records; efficient memory must not leak one teammate’s context into another’s Task without policy; team learning needs clear rules for shared Library / Marketplace installs on paired Macs.

---

#Production vs repository name

Canonical hosting: Repository name and hosting.

Production Mac clients use a fixed WebSocket target: wss://www.agentwitch.com/api/agent-witch/ws (install bundle 103+). Local dev uses http://localhost:3000 with the same path on your machine.

---

#Four deployables (engineering map)

Users mostly see Mac and Runs. Under the hood:

Full table: AgentWitch deployables.

---

#Trust boundary: cloud vs Mac

Browser (you)  ──HTTPS──►  AgentWitch Cloud + Postgres (runs, workflows, accounts)
                              │
                              │ WebSocket hub (paired computer only)
                              ▼
Mac (AWI)  ──►  real shell / writer CLI in folders YOU chose
              ──►  harness files under ~/.agent-witch/harness/
              ──►  local bridge (AWB) only on loopback — not exposed to the internet

On the cloud, AgentWitch stores account data, Run metadata, workflow graphs, your checkpoint answers, and dispatch queue state (see ADR 0005 in architecture index).

On the Mac, AgentWitch executes Tasks and workflow agent steps: shell sessions, CLI tools, and file writes implied by the agent (including harness install). The console streams terminal output to your browser; it does not silently substitute cloud compute for Mac work unless you configure Cursor Cloud as an explicit target.

Dispatch overview: Mac harness, workflow, and agent dispatch.

---

#Pairing and “This computer”

Claiming a Mac creates a pairing token on the machine. The cloud stores a hash only. The browser learns “this computer” by comparing that hash to the local bridge /identity probe—not by guessing from IP or hostname.

• You must run Connect this computer while signed in to link an install to your account.
• Another person’s account on the same physical Mac gets a different token; hostname alone is not proof of ownership.

How AWC knows this computer · AWB localhost identity and CORS.

---

#Honest run UX (no fake success)

AgentWitch commits to honest progress labels on live Runs:

• Connecting / In progress / Waiting on you while work is not finished.
• Terminal outcome chips (Success, Failed, Stopped, etc.) only after a real end state.

Locked product strings: Run UX honesty.

The New task composer uses the same honesty for Mac readiness: if the computer is offline, reconnecting, needs an update, or unreachable (DNS), Send is blocked with a clear reason—not a silent queue failure.

Send readiness reason codes.

---

#Mid-run input ([[AWAITING_INPUT]])

During a Run, the agent may pause and ask a question in the terminal. The browser prompts you; the Mac waits for your answer over the hub protocol. AgentWitch does not invent answers on your behalf.

Workflow checkpoints (Chapter 6) are a higher-level version of the same idea—planned human nodes instead of ad hoc terminal gates.

---

#Cursor Cloud (optional second target)

Mac is the default trusted executor for local repos and CLIs. Cursor Cloud dispatch uses stored API keys and a cloud executor identity—it is an optional path for teams that configure it, not a hidden replacement for your laptop.

Writer routing (continuation vs memory limits): Writer dispatch cascade routing.

---

#Data you should treat as sensitive

• Pairing tokens and Mac install directories (~/.agent-witch, dev ~/.local-agent-witch).
• Project folders you attach to Tasks (source code, secrets in .env if the agent reads them).
• Workflow uploads (PDFs/images) stored server-side for a bounded time with signed agent download URLs (workflow file upload).
• Session cookies for your AgentWitch account—same as any SaaS console.

AgentWitch is built for teams who accept that running an agent on a computer is equivalent to giving a developer shell access in the chosen folder, mediated by your prompts and playbooks.

#Pillars and data (honest summary)

---

#Multi-instance production (brief)

AgentWitch Cloud may run on more than one server replica. Writer dispatch requires the live Mac WebSocket on the node handling your send request. During deploys or load balancing, you may briefly see Reconnecting even when AWI on the computer is healthy. The product fails closed rather than dropping Tasks on the wrong node. A second deploy that starts while the first is still applying database updates waits and continues, instead of failing because that update was already saved.

User impact and mitigations: AWC Mac reconnecting vs local live · OPEN-002 in AgentWitch KNOWN_ISSUES.

---

#Install bundle updates (trust + safety)

The cloud publishes an install bundle version; your Mac reports what it runs. When the computer is behind, the composer blocks Send with Update needed until you update—so you are not dispatching with known-fixed client bugs.

Update flows use the local bridge and LaunchAgents; a bad update historically could break the plist (AGENT-067)—modern bundles heal on start. See Update local and LaunchAgent plist.

---

#Related reading

• System Q&A index
• Local bridge doc — ports, wake, harness install API
• Chapter 9 — Troubleshooting — DNS, reconnecting, bundle mismatch

---

#Query aliases

• AgentWitch production trust what runs on computer vs cloud
• www.agentwitch.com security pairing token harness
• honest run UX send blocked Mac offline
• Cursor Cloud vs Mac dispatch AgentWitch
• tin cay AgentWitch, du lieu o dau may Mac hay cloud
• agentwitch.com production khac agent-witch repo
• Mac pairing tokenHash this computer trust
• chan Send khi Mac reconnecting update needed
• bon tru cot tin cay, du lieu memory team learning bao mat