Team trajectory review
Review trajectories, not just PRs
Share sessions across devices and teammates, watch replays together, and comment on the exact step — the review happens where the work happened, not in a diff that lost the context.
Team and personal sessions
Sessions group by team and by member. A teammate's run is one click from replay — with permissions controlling who can view, comment, or edit.
Comments in context
Comments anchor to a step of the trajectory — an edit, a command, a decision — not to a line in a diff that has already lost the why.
Fork and continue
Pick up a teammate's session where they left off: fork it into your own workspace with full context and keep going.
Cross-device sync
Your record follows you between machines; team collaboration runs on self-hosted Supabase, so the data stays on infrastructure you control.
Onboarding by replay
New members watch how the codebase actually gets built — the accumulated record is legible, so context transfers without a meeting.
Shared accountability
Humans, agents, and teams collaborate around shared context and aligned goals — the organizational thesis ORG-2 is named for.