Player profile
Coterie
An Apache-2.0 self-hosted team of persistent Claude Code agents on one Debian host, with separate Unix accounts, shared MCP memory, per-agent mailboxes and browser terminals.
Profile
Where it fits
Coterie gives each agent its own Unix account, home and terminal on one Debian host. A shared MCP memory server supplies identity, team state, unread mail and recent handoffs, with a hashed manifest recording the material sent at boot.
A coordination daemon delivers boot prompts and notifies idle agents of mail. A browser portal shows the agent terminals together, while persistent memory and handoffs support work across session restarts.
Builder web analytics
Measure outcomes from Coterie-assisted work
Coterie coordinates agent work and handoffs. Separately configured product analytics can help a team assess the user-facing results of a deployed change.
This is an optional workflow, not a native Coterie integration with Agent Analytics. Configure product tracking and analytics access separately; the listing does not install tracking or report Coterie agent activity.
First loop to measure
- a team coordinates a product change through agent mail and handoffs
- the reviewed change is deployed to a separately instrumented surface
- a human or an agent with configured analytics access reads measured results
- the team uses that evidence to choose the next task
Copyable prompt
If product tracking and analytics access are already configured, report observed outcomes for the deployed change and their limitations. Otherwise, identify what is missing. Do not assume a native integration or infer causation from a before-and-after comparison.