Session Glue — Communication skill for Claude Code

Session Glue

[](https://github.com/realproject7/session-glue/actions/workflows/ci.yml) [](https://pypi.org/project/session-glue/) [](https://pypi.org/project/session-glue/) [](LICENSE)

**Reset the chat, not the work.**

Session Glue is a session-continuity protocol and CLI for coding agents (Claude Code, Codex, Cursor, and friends). When an agent session gets long, expensive, and forgetful, Session Glue freezes the useful context into a compact, repo-local briefing — and a fresh session picks up exactly where the old one left off, without dragging the whole chat history along.

No daemon. No server. No database. No network by default. Just markdown files in your repo — plus an opt-in [Personal Vault](#personal-vault--the-same-work-on-your-other-machine) when you explicitly ask to carry them to another machine.

The problem

Long coding-agent sessions degrade in a predictable way:

• Context bloat — old logs, diffs, and dead ends stay in context; every new turn re-reads material that no longer matters.
• Rising cost and latency — you pay for that bloat on every single turn.
• Memory drift — the agent starts forgetting earlier constraints and re-litigating decisions you already made.
• Bad restarts — clearing the session loses the work state, so the next session burns thousands of tokens re-scanning the repo to figure out where things stand.

The usual escape hatch is "paste a messy summary into a new chat and hope." Session Glue replaces that with a disciplined, validated engineering handoff.

How it works

Session Glue cuts one long conversation into two clean ones — and carries the **work** across the gap while letting the **chat** die.

┌─────────────────────────────────