Player profile
OpenRig
An Apache-2.0 local coordination system where YAML RigSpecs define coding-agent teams, their communication edges, and continuity, with a daemon, CLI, TUI, and MCP server managing native agents in tmux.
Profile
Where it fits
OpenRig models a team as pods, members, edges, and continuity in a YAML RigSpec. Native coding-agent sessions run in tmux, while rig send, broadcast, and chatroom provide communication through the local coordination layer.
It belongs in Coordination And Team Systems because the reusable team topology and its communication paths are the central objects. The shipped conveyor mixes Claude Code and Codex across intake, planning, build, and review, and the README documents topology snapshot and restore.
Builder web analytics
Measure projects built with OpenRig
A separately configured outcome readout can inform the next task sent through an OpenRig team after its work is deployed.
This is an optional workflow, not a native OpenRig integration. Configure tracking on the deployed surface and analytics access in the querying agent separately; RigSpecs, chatrooms, and topology snapshots do not supply product analytics.
First loop to measure
- team members 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.