Hand off your AI coding session
in one command.

Vibe coding is great. Until two people share a feature.

Static rules files (CLAUDE.md, .cursor/rules/) describe how your team likes to work. They tell the AI nothing about what was tried in the last session. That gap shows up three ways.

Two commands. One in each terminal.

Dev A captures their session as plain markdown. Dev B picks it up — in whichever AI tool they prefer. The AI starts the next prompt already knowing what was tried.

Everything teams need for seamless AI handoffs

Built for the actual loop: code with an AI tool, snapshot, hand off, resume. No backend to host. No accounts to provision.

Snapshot in seconds

Captures git diff, the last AI messages from every detected tool, inferred open files, the active branch, and your one-line note. Writes plain markdown to .huddleup/threads/<name>.md.

Resume instantly

Your teammate runs one command and gets a "YOU ARE HERE" briefing, the relevant files reopened, and a context file the AI tool reads on its next prompt. Zero re-explanation.

VS Code + Cursor companion

Sidebar panel with Snapshot, Resume, Standup, and New Thread buttons. Every action is also in the command palette. Live on VS Code Marketplace and Open VSX.

Multi-tool capture

Claude Code, Cursor, Codex CLI, GitHub Copilot, and Windsurf are all auto-detected. detectAllAdapters() merges messages from every tool into a single snapshot — the thread's Tools field lists every contributor.

Token Exhaustion Protocol

The generated AI-tool config files (CLAUDE.md, .cursor/rules/huddleup.mdc, AGENTS.md, .windsurfrules) tell the AI to auto-run huddleup snapshot at ~10% tokens remaining. Even if a human forgets, the AI doesn't.

Plain markdown + git

The whole .huddleup/ folder is markdown plus JSONL history. Commit it, paste in Slack, attach to a Linear ticket. No backend, no MCP server, no accounts.

Auto-detected. Cross-platform. Easy to extend.

HuddleUp probes every supported tool on the machine. Multiple adapters can match — their open files and last messages merge into a single snapshot. The thread's Tools field lists every contributor.

How HuddleUp differs from static rules + memory banks

Static rules (CLAUDE.md, .cursor/rules) carry your conventions. Memory bank tools persist context for one tool. HuddleUp adds the missing live, cross-tool handoff layer.

Four commands. Under sixty seconds.

No sign-up, no account, no backend. Just Node.js, git, and a terminal.

1. 1

   Install

   $ npm install -g huddleup

   Requires Node.js 20+. Also installs the hup short alias.

2. 2

   Initialise

   $ cd your-project
   $ huddleup init

   Scaffolds .huddleup/ and generates CLAUDE.md, .cursor/rules/huddleup.mdc, AGENTS.md, .windsurfrules.

3. 3

   Snapshot before a break

   $ huddleup snapshot

   Auto-captures git diff + last AI messages from every detected tool. Asks one question: "where did you leave it?"

4. 4

   Resume (you or a teammate)

   $ huddleup resume streaming-chat-endpoint

   Prints a YOU ARE HERE briefing, opens the inferred files, and injects context into your AI tool.

Distributed via npm · VS Code extension via Marketplace and Open VSX · Open source on GitHub under AGPL-3.0

Questions teams ask before installing

If your answer isn't here, open an issue on GitHub — we'll add it.

• Does HuddleUp send my code anywhere?

  No. The CLI runs entirely on your machine. The .huddleup/ folder is plain markdown + JSONL that you commit to your own git repo. There is no backend, no telemetry, and no third-party uploads.
• Do I need to install all 5 AI tools?

  No. HuddleUp detects whichever tools you have. If you only use Claude Code, only the Claude Code adapter runs. The generic fallback always writes AGENTS.md so any AGENTS.md-respecting tool also picks up your charter.
• How is this different from a CLAUDE.md file?

  CLAUDE.md (and Cursor Rules, AGENTS.md, .windsurfrules) carry static project conventions. HuddleUp generates those files from a single charter — and adds the missing layer: live, per-session work-in-progress state. CLAUDE.md tells the AI HOW you work; a HuddleUp thread tells it WHAT was just tried and where it ended up.
• Does it work with Cursor specifically?

  Yes. HuddleUp reads ~/.cursor/{sessions,chats}/ and the Cursor workspaceStorage folders across macOS, Linux, and Windows, and writes .cursor/rules/huddleup.mdc. The VS Code extension also installs in Cursor via Open VSX.
• What if an AI tool changes its session file format?

  Each adapter is a small isolated file (~80 lines) with its own fuzz tests against captured fixtures. When a format changes you update one file, the tests catch the break, and a patch release ships. Other adapters keep working.
• Can I use it without git?

  You can run huddleup init and huddleup thread new without git, but the snapshot command embeds git diff and recent commit metadata — so without a git repo, snapshots will be lighter. Recommended: use it inside a git repo.
• Is it free for commercial use?

  Yes, with caveats. HuddleUp is AGPL-3.0. You can use it inside your company for any purpose. If you fork it and run a modified version as a hosted service, AGPL requires you to publish your changes under AGPL-3.0 as well.
• How do I install just the VS Code extension?

  Search "HuddleUp" in the VS Code Extensions panel, or visit the Marketplace listing directly. Cursor / VSCodium / Windsurf users can install it from Open VSX. You still need the CLI installed (npm install -g huddleup) for the buttons to do anything.
• What is the Token Exhaustion Protocol?

  When huddleup init generates the AI tool config files, it embeds an instruction that tells the AI to run huddleup snapshot when its session is near the token limit (default 10% remaining). The AI saves its own context before it gets dropped — so even if the human forgets, the snapshot still happens.
• Where do snapshots actually live?

  In .huddleup/threads/<thread-name>.md in your repo. Plain markdown with YAML frontmatter. Every snapshot appends a new ## Snapshot block. Archived threads move to .huddleup/threads/_archive/. History events log to .huddleup/history/<date>.jsonl.