ComputerConnection/closing-statements

Closing Statements — Session Wrap-Up

You're closing out a work session on the CC Platform. Your job is to leave the project in a state where any agent on any workspace (Zach-Linux, Zach-Work, Zach-Server) can pick up exactly where this session left off — no guessing, no re-discovery, no wasted first 10 minutes.

What you're producing

1. Updated TELEMETRY.yaml — the cross-workspace state file at the repo root
2. A handoff summary — spoken to the user, concise, honest about what's done and what isn't

That's it. No reports, no documents, no extra files. Just update the state and summarize.

Step-by-step

1. Gather what happened this session

Run these to understand what changed:

# What workspace are we on?
hostname

# What repos have uncommitted changes?
cd <repo-root> && git status -s
cd <repo-root> && git submodule foreach --quiet 'echo "=== $name ===" && git status -s'

# What was committed this session? (last ~10 commits, check timestamps)
cd <repo-root> && git log --oneline --since="today" --all
cd <repo-root> && git submodule foreach --quiet 'echo "=== $name ===" && git log --oneline --since="today" --all 2>/dev/null'

# Any open PRs we touched?
cd <repo-root> && git submodule foreach --quiet 'echo "=== $name ===" && gh pr list --state open --limit 5 2>/dev/null'

Also review the conversation history — what was the user's focus? What problems were solved? What decisions were made? What got deferred?

2. Read current TELEMETRY.yaml

cat <repo-root>/TELEMETRY.yaml

Understand the current state so you can update it accurately.

3. Update TELEMETRY.yaml

Make these updates:

Header fields:

• last_updated: current UTC timestamp
• updated_by: the workspace hostname (Zach-Linux, Zach-Work, or Zach-Server)

workspaces section:

• Update last_active for the current workspace to today's date

submodules section:

• Update branch, last_commit_summary, status, and pending_prs for any submodule that changed this session
• If a PR was merged, remove it from pending_prs
• If a new PR was opened, add it

active_work section:

• Update status and completed/remaining phases for any work items touched
• Add new work items if new initiatives started
• Move completed items out (just delete them — the changelog is the record)

validation section:

• Update test counts, pass/fail, last_run date and workspace if tests were run

changelogs section:

• Add a new date entry under the current workspace
• Each entry should be one line, past tense, specific
• Good: "Fixed V3 build chain — added @cc/context to 6 apps, resolved 87 TS errors"
• Bad: "Worked on stuff" or "Made progress on the build"

next_actions section:

• Update based on what's actually next, per workspace
• Remove items that were completed this session
• Add new items that emerged from this session's work

4. Check for uncommitted work

If there are uncommitted changes in any submodule, flag them to the user:

"Heads up — there are uncommitted changes in [submodule]. Want me to commit those before closing out, or leave them staged?"

Don't silently commit. Don't silently ignore. Ask.

5. Commit TELEMETRY.yaml

cd <repo-root>
git add TELEMETRY.yaml
git commit -m "telemetry: close session from [Workspace] — [1-line summary]

Co-Authored-By: Claude <[email protected]>"
git push origin main

6. Deliver the handoff

Speak directly to the user — no markdown document, no file. Just a clear summary:

Format:

Session closed from [Workspace] — [date]

Focus: [What the session was about in one sentence]

Done:

• [Specific thing 1]
• [Specific thing 2]

Not done / deferred:

• [Thing that didn't get finished and why]

Next time on [most likely next workspace]:

• [The first thing the next session should pick up]

Hot start: Read TELEMETRY.yaml and CLAUDE.md, then [specific instruction]

The "hot start" line is the exact prompt the user can paste into their next session to get the agent up to speed immediately. Make it specific to what's actually next, not generic.

Tone

Keep it brief and direct. This isn't a report — it's a sticky note on the monitor for tomorrow-you. If something is broken, say it's broken. If something went well, a single line is enough. The changelog and git history have the details.

Edge cases

• Nothing meaningful happened (just research, reading, conversation): Still update last_active and last_updated. Skip the changelog if there's truly nothing to log. Don't manufacture entries.

• Session was on a workspace not in TELEMETRY.yaml: Add it to the workspaces section and ask the user to confirm the details.

• TELEMETRY.yaml doesn't exist: This shouldn't happen on the CC Platform, but if it does, tell the user and offer to create one from CLAUDE.md.

• Can't push (no network, auth issue): Commit locally and tell the user it needs a push. Don't silently fail.