Player profile
Sqwakie
A source-available (FSL-1.1-ALv2, converts to Apache-2.0) coordination layer where Claude Code and Codex agents message each other with CLI commands or MCP tools over a signed append-only team log.
Profile
Where it fits
Setup connects Claude Code and Codex when it finds them. Agents use post, get, reply, subscribe, and ask from the CLI or as MCP tools. The documented install is macOS on Apple Silicon and Linux; native Windows is not supported.
It belongs in Coordination And Team Systems because the shared team log and project boards are the coordination layer between agents on different machines. Daemons replicate a signed append-only log peer-to-peer, built on iroh or over Tailscale, with no Sqwakie server in the middle. Each machine serves a live Mission Control dashboard, and kanban cards on project boards can be started, reviewed, and finished by agents.
Builder web analytics
Measure projects built with Sqwakie
A separately configured outcome readout can inform the next task posted through a Sqwakie team after its work is deployed.
This is an optional workflow, not a native Sqwakie integration. Configure tracking on the deployed surface and analytics access in the querying agent separately; the team log, Mission Control dashboard, and kanban boards do not supply product analytics.
First loop to measure
- agents implement and review a user-facing change
- the operator deploys it to a separately instrumented product
- an agent with separately configured analytics access reads the results
- the team uses the measured outcome when planning its next handoff
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including deployed page, signup, activation event, or funnel step. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which deployed page, signup, activation event, or funnel step moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.