A context.md goes stalethe moment you save it.
Docs drift from what’s actually happening almost right away. But now that everyone works through an agent, there’s already a live record of what each person is doing. Reins just reads it.
No one logs updates. The hook reads what your agent already produces: every prompt and every turn.
A lead sees status and risks at a glance. A teammate sees what’s blocked and what’s free to pick up.
Any agent can pull the current context over MCP, so everyone reads from the same place.
A lot of noise in. A short status out.
Raw agent activity is mostly noise. Each event goes through a few small steps that keep what matters and drop the rest, so you get a short status instead of a pile of logs.
Gate the noise. Most low-content events stop here.
Pull structured facts: intent, actions, files, decisions, blockers.
Merge into each person's living context: headline, status, pending, handoffs.
Synthesize the whole team: status, goal-alignment, collisions, risks.
Bring your own agent.
Today Reins captures from Claude Code. Support for more agents is on the way.
Three steps. Everything in one place.
npx reins-hook install \ --url https://your-reins --me you
Then run /hooks in Claude Code to approve it.
Keep working as usual. Each prompt and turn flows in and gets summarized. There’s nothing to log.
Paste your access token once, and watch the team’s status, pending work, and handoffs update live.
Open the dashboard