What Scout does
Scout is the AI inside TractionScout. It reads every source you connect, from analytics and search to payments, social and email, and works through a growth question the way a careful analyst would:
- compare the numbers along your funnel,
- explain what may be getting in the way, keeping what the data shows apart from what still needs checking,
- prepare a change: copy, content, a code change, a post or a campaign,
- check afterwards whether it helped.
A finished task is not treated as proof of more customers or revenue. Scout says when the evidence is not in yet.
You stay in control
Reading data, preparing a draft, publishing and changing a budget are separate permissions. Everything Scout prepares appears in Work, where you review, approve and follow each growth action. Reading your analytics never gives Scout permission to post or spend.
Memory that you curate
Scout keeps a memory per project, built from evidence such as experiments, assets, social posts and alerts. In Activity & Memory you can review, approve and retire what it remembers, see what it made, and check the health of scheduled work.
Automations
Automations are work Scout repeats on a schedule, hourly, every 6 or 12 hours, daily or weekly, with a record of what came of each run. You choose what happens when a previous run has not finished. Scout's notes can reach you as browser notifications.
Bring your own agents with MCP
The open-source Agent CLI (tscout, AGPL-3.0) connects Claude Code, Codex or any MCP client to your projects. The download is verified with a checksum and has no dependencies. The default mode is read-only; a review-staging mode lets agents stage work for your approval. External execution is blocked in every mode, and credentials, approvals and budgets stay on the server.
Set it up with Agent CLI and MCP, or see an example in Connect a coding agent or script.
