Docs

/ wrap-session

End a work session. Summarize progress, update issues, post a project health update.

The /wrap-session command ends your work session. It gathers what happened, composes a summary, determines project health, and posts an actual project update, not just a chat summary, but a real update to your issue tracker.

Usage

agent chat 
/wrap-session
agent chat 
that's it for today
agent chat 
let's wrap, good progress on the auth flow

What Happens

  1. Gather session data: Collects what was worked on, what changed, and what's still in progress
  2. Compose summary: Builds a structured summary covering what was completed, what's in progress, what's next, and any blockers
  3. Determine health status: Assesses whether the project is on track, at risk, or off track
  4. Post project update: Cloud tier publishes the summary to your issue tracker via the mechanism scripts. Local tier writes the summary to a file in your project's session history.
  5. Check for uncommitted changes: Warns if there are local changes that haven't been committed

Health Status

The wrap command determines one of three health states:

  • On Track: Work is progressing as expected
  • At Risk: There are concerns that could slow things down
  • Off Track: Significant blockers or delays exist

When to Use It

At the end of every work session. The project update gets posted to your issue tracker, so your team has visibility into what happened. This is especially useful when multiple people are working on the same project. The updates build a running record of progress.

Best Practices

  • Always wrap before ending a session. It preserves context for next time
  • Add notes about what's next or what's blocking you
  • Commit your changes before wrapping to keep things clean

Related Commands