scott sync is the primary onboarding action for the Scott agent plugin. From your development machine, run:
curl -fsSL https://tryscott.ai/install | sh
scott sync
scott sync reads recent local coding-agent sessions, uploads the relevant context to Scott, starts a Sync Chat review, and opens /sync.
Install plus scott sync is the exception to the agent-first workflow. Push and pull should stay agent-invoked because they depend on the active thread context.
What sync does
- Finds supported local agent session history
- Uploads recent sessions from the last 14 days
- Creates unsynthesized planspaces that Scott can reason over
- Starts a Sync Chat review of recent themes and priorities
- Prints a URL to
/sync
Run sync from the development machine where the agent sessions happened. Hosted browser agents cannot read your local history.
What to ask Sync Chat
After sync finishes, ask questions like:
What have I been working on lately?
Which of these sessions should become team-facing planspaces?
What patterns or repeated ideas do you see across my recent agent work?
Write up the strongest prototype as a planspace for team review.
Add code context
Sync Chat works from session history by default. For code-aware answers, connect repositories with the Scott GitHub App.
When to run sync again
Run scott sync whenever you want Scott to refresh its view of local agent work:
- after a day of active agent sessions
- before planning what to share with the team
- before a design review or sprint planning meeting
- when switching machines or agents
Sync vs push
Use scott sync to onboard broad recent history. Use Push when one current thread is ready to become a team-readable planspace.
