Your AI chat history belongs in your repo — so that's the only place we put it.

Session Control saves and resumes your GitHub Copilot, Cursor, Codex, and Claude Code chat sessions, linked to your git commits. Local-first. Cross-IDE. Free forever.

Install free on Open VSX See Pro →
Free — forever

Session Control

Everything the extension does today stays free. That's a commitment, not a trial.

Pro

Session Control Pro

Five features in the same extension — enter a license key and they unlock in place. Find past work, turn it into knowledge and guidance your AI tools load, and keep it in sync across assistants and machines.

Screen recording: Harvest This Session is run on a saved chat, the review lists two files to create, and the knowledge folder appears in the repository with a decision file open.
Knowledge Harvesting, start to finish: harvest one saved session, review what will be written, get the bundle in your repo.

What a harvest writes into your repo

This is the bundle from the recording above, unedited: one two-turn demo session about an authentication refactor, harvested with GPT-4o mini through Copilot. Plain markdown files, in a folder you commit like any other.

your-repo/
knowledge/
├── index.md
├── log.md
├── decisions/
│   ├── index.md
│   └── refactor-authentication-…-parsing.md
├── patterns/
│   └── index.md
├── pitfalls/
│   └── index.md
├── playbooks/
│   └── index.md
├── references/
│   └── index.md
└── sessions/
    ├── index.md
    └── screenshot-demo-auth.md
knowledge/decisions/refactor-authentication-middleware-for-token-parsing.md (excerpt)
---
type: Decision
title: Refactor authentication middleware for token parsing separation
tags: [authentication, middleware, refactor, decision]
source_sessions:
  - /sessions/screenshot-demo-auth.md
provider: copilot
confidence: 0.9
…
---
…
**Decision:** Refactor the middleware to keep `authenticate(request, next)` as the public entry point. Move token parsing into a new function called `parseBearerToken`.

**Consequences:**
- Token parsing will be handled separately, allowing for more focused testing of token validity (missing, malformed, and expired tokens).
…

# Citations
1. [Session screenshot-demo-auth](../sessions/screenshot-demo-auth.md)

Harvest runs on the AI model you configure. It sends the sessions you select to that model (Copilot, Cursor, Claude, or Codex) and shows who receives the content and how much before anything is sent. The bundle is written only to your repo. We run no servers. What leaves your machine

Search Saved Sessions (All Workspaces)

Search locally stored sessions across workspaces with ordinary text, then open the result you need.

  • Narrow results with provider:, branch:, workspace:, after:, and before: filters
  • Select a result to open that saved session
  • Runs locally over your stored session files
The Search Saved Sessions quick pick in VS Code with the query provider:copilot branch:demo/auth-middleware and one matching saved session listed.
Filtering saved sessions by provider and branch.

Knowledge Harvesting

Turn write-only chat logs into a durable knowledge base your team — and your AI tools — can actually use.

  • Analyze your saved sessions and extract reusable playbooks, decisions, code patterns, and pitfalls
  • Write a plain-markdown Open Knowledge Format bundle into your own repo
  • Every concept cites the session it came from
  • Dry-run preview before anything is written
  • Also harvests one session at a time, or an imported Word document
  • Analysis by the AI model you choose — results stay in your repo

Export Session to AI Control File

Right-click one saved session and turn what it worked out into guidance your assistant loads next time.

  • Write a Cursor rule, Claude Code skill, Copilot *.instructions.md file, or AGENTS.md section
  • See the generated file before anything is written
  • Generated by a VS Code language model or your installed Claude Code or Codex CLI

Sync AI Skills Across Assistants

Keep the same repository guidance matching across your Copilot, Cursor, Claude Code, and Codex copies.

  • Works in both directions: an edit to any copy flows back to Copilot and on to the others
  • Asks before overwriting; copies edited differently are shown to you to choose
  • Local file comparison only — nothing is sent anywhere

Push / Pull Saved Sessions to Git

Sync saved sessions with a private Git repository you own, so they follow you across machines.

  • Runs only when you choose Push or Pull, from the Saved Sessions title bar
  • A session changed on two machines is shown to you to resolve, never overwritten
  • Push never force-pushes; Git uses your own credentials, which Session Control never stores

Pricing

Five Pro features, one price. No seats math, no tiers.

Free

$0

Save, resume, browse, continue, analyze — across all four providers. No account required.

Install

Pro

$29/year

Everything in Free, plus Knowledge Harvesting, Search Saved Sessions (All Workspaces), Export Session to AI Control File, Sync AI Skills Across Assistants, and Git sync. License key delivered instantly via Polar.sh. Prefer monthly? $4/month.

Upgrade to Pro
Founders lifetime — $49, first 100 buyers. Pay once, keep every Pro feature in the Session Control extension — today's and any added later. Thanks for being early. Lifetime does not include separately sold products: the GitHub App companion, a hosted sync or team tier, a self-hosted enterprise license, or the Knowledge Pack marketplace. License terms.
Get lifetime access

Local-first, by design

Sessions are stored in your repository as plain files. Knowledge bundles and control files are written to your repo, in plain text you can read with cat. Saving, resuming, browsing, auto-save, and AI skills sync involve no network calls at all. Global Session Search runs locally over your stored session files.

These features send data to an AI provider, and only when you use them: Analyze Saved Chats (free), Knowledge Harvesting, and Export Session to AI Control File send the sessions or document you select to the AI model you choose (Copilot, Cursor, Claude, or Codex). Harvesting and export show who receives the content and how much before anything is sent. If you turn on the optional TypeSafe integration and accept its notice, plain-words @session-control routing sends your prompt plus the titles, providers, and dates of up to 20 saved sessions, and search reranking sends your query plus the title, provider, workspace, date, and snippet of its top 10 matches, to the TypeSafe AI provider.

Git sync pushes only to the private Git repository you configure, using your own Git credentials. Pro validates your license key. Nothing goes to us — we don't run servers. No telemetry, no cloud storage, no account.