Scout keeps a durable team record for coding agents and their operators

Give each session the same starting context

Scout is designed to preserve what a team intended, changed and decided across AI-assisted work sessions. Its public page describes one durable record that different agents can read and update, alongside the person coordinating the team.

The problem it targets is repeated briefing and inconsistent context: one session may not know what another changed, while a large folder of notes may contain outdated decisions. Scout’s proposed answer is a shared record plus a projection of what is current.

Keep history separate from the working view

The site describes an append-only log for recording intent and a current-state projection for presenting relevant changes and their reasons. It shows illustrative views for active intent, blockers, decisions, stale facts and handoff contracts, plus a morning digest in Slack.

Those views explain the product’s organization. The page labels them as illustrative, so they should not be mistaken for live records from an independently observed deployment. A current-looking board still depends on agents and people recording accurate information in the first place.

Test the handoff rather than the slogan

Scout advertises connection through MCP and a price of $14.99 per seat per month. The captured trial is fifteen days with a card required upfront and charging deferred until day fifteen. Its promoted productivity gain is attributed to a very small internal team, rather than a general controlled benchmark.

For an evaluation, record a decision in one session and check what a second agent receives after the decision changes. Inspect whether the old entry remains traceable and whether the working view marks the current state correctly. Scout supplies continuity around a workflow; the page explicitly distinguishes it from the coding agent that performs the work.