AgentLayer▸docs
Use it

Sync

One pass through every maintenance step, in dependency order, ending in a status block and, when something needs you, a few closing questions.

sync brings every derived view current at once. It is heavier than briefing pulse and lighter than running each skill by hand. Run it when you have been away, when you want to start fresh, or when something feels stale.

The steps

Sync runs fourteen numbered steps, 0 to 13, always in this order. Before the first, it saves the home as it stands when history is on.

Step 0 fast-forwards the default branches of the code repos you configured, so the agent reads current code. It never checks out, stashes, or commits: a dirty or diverged branch is reported, not fixed. Without repos or the GitHub pack, it is skipped.

What flywheel does

Flywheel is a cross-project work session framed by your north-star roadmap. Inside sync it does five things:

  • Catches up on the sessions since its last run. It reads every daily summary written since its previous report, adds one thread note to each task those sessions moved, and lists up to five work streams no task tracks, with an offer to file one.
  • Sets stalled tasks aside. A task that was already overdue at the last run and hasn't been touched since gets a decision instead of another "still unchanged" line. Sync asks it at the end.
  • Advances, updates and closes the rest, and flips a roadmap milestone's status only on evidence from this run.
  • Archives closed tasks into tasks/archive/, every run.
  • Saves a flywheel report in reports/briefings/, every run, so the next run knows where to start and the morning brief can pick up the trail.

What needs attention

After the flywheel, sync checks what is waiting and prints it in the status block. Outside sources are read as counts, names, and waiting times, never the text of a comment, a ticket, or a message.

It checks the board, the plugin, cadences, handed-off tasks and the brain, plus GitHub, support and Slack when their packs are on. Open the table for what each reports and offers.

The closing interview

Sync ends with questions only when it surfaced something to act on: an overdue item, a stalled task, a due cadence skill, a pending upgrade, a concrete next move. On a clean bill, the status block is the end.

  1. Self-review first, on its own, when the monthly review is due: run it now, tomorrow, or skip this month. Skips are counted. See Self-evolution.
  2. One question per stalled task: push it a week, park it (lower priority and no date, so it stops coming back), mark it blocked with a reason, or cancel it.
  3. What to tackle next. Pick one or several, then act on them now, in order, or queue each as a task.

While the home has no roadmap.html, building one is always the first option in the third question. It stands in for a due goals year when this year's goals aren't set, since the build runs that interview first. See Working sessions.

Chaining a briefing

sync morning or sync evening runs the matching briefing after the maintenance pass. With no argument, sync picks: a forgotten morning brief still runs in the afternoon instead of silently becoming an evening one.

The session radar runs before the briefing, so the briefing's first moves include the decisions your sessions are waiting on. The status block above it stays a full log of the run; the briefing is the part to read.

Saving a snapshot

When the home has history turned on, sync saves twice:

  • Before the run, the home as it stands, in one commit. It holds whatever changed since the last sync, and it is the point to go back to if the run goes wrong.
  • After the run, what the run changed, as a few ordered commits (knowledge, projects, reports, state), so the run reads as a clean diff of its own.

Sync only saves a history that stays on this computer. A home connected to a remote, not on its main line, or mid-merge is skipped with a one-line note, and so is a history whose setup has not finished its first snapshot.

Progress and reminders

In Claude Code, a band above the prompt shows the run as it goes: the step it is on, the elapsed time, and counters for what it is clearing. See Sync progress.

Between runs, the sync notice does the reminding. It starts in the session banner three days after the last sync and gets louder at five days and at eight. Sync stamps the time when it refreshes the dashboards, and that stamp resets the notice.

Why the order matters

Each step leaves what the next one reads. Out of order, you re-reconcile.

On this page