Your code doesn’t
leave the building.

Node.js 20+ · macOS, Linux, Windows · no account, no sign-in

• Same engine as the extension. The agent, permissions, checkpoints, semantic search, and MCP support are shared code — not a reduced second implementation.
• /pr-review reviews your branch's PR file by file, then posts a real GitHub review with inline comments and one-click suggestions — only after you approve it. /pr-review deep adds a verification pass that drops false positives first.
• Headless mode. -p "task" runs the whole agent loop with no TTY — plain text or --json events, four permission modes for unattended runs, non-zero exit on failure. Built for CI.
• Every action gated. Same permission prompts as the editor, plus shadow-git checkpoints you can rewind step by step.
• Your models. Local Ollama or LM Studio, a box on your LAN, or any OpenAI-compatible endpoint — configured once, per role.

Runs on your machine · localhost by default · no account, no hosted service

• One command. heapcode web in any folder opens a browser tab pointed at that workspace — same agent, same permissions, same checkpoints as the CLI and the extension.
• A real workspace panel. Per-file diffs, one-click revert, a checkpoint timeline to rewind to, the file tree, streamed command output, and what the agent has actually indexed about your code.
• Things a terminal can’t do. Paste a screenshot straight into the message box. Get a desktop notification when a long run finishes in a background tab. Read rendered diagrams and HTML the agent built for you.
• Close the tab, keep the run. The server owns the work, not the browser — reopening reattaches to whatever is still going.
• Localhost by design. A fresh token per launch, never left in the address bar. --host opts in to reaching it from your phone, and says so loudly. Your API keys stay on the server and never reach the page.

Ships in the CLI · heapcode chat [folder] · or at /chat under heapcode web

• Your files, not your code. Point it at a folder of PDFs, Word documents, spreadsheets and photos. It reads them, searches them, and answers from them — a scanned receipt is findable by what it says.
• Every answer shows its source. It says which file an answer came from, and a figure can be traced back to the line it was read from.
• It never writes over your files. A summary, a table or a report lands beside the conversation as a draft. Saving it into your folder is your call.
• Same engine, its own product. Its own tools, prompt, history and memory — sharing only the engine, the models you configured, and the index with Heap Code.
• Connectors with sign-in. MCP servers work here too, including hosted ones that need you to log in — and it asks before running one.

• A Chrome side panel that works the page you are on. Ask about it, or have it search, filter, compare across pages and fill in forms — and hand back the steps only you should take.
• Nothing happens without you seeing it. Every click or form fill is checked against what the element really is, and asks first. Banking and password sites are refused outright.
• Your own models. Point it at Ollama on your machine or your LAN — no server setup needed — and the pages you read never leave home.

Chrome extension · side panel · sites granted one at a time. Not on the Chrome Web Store yet: download the heapbrowse .zip from the latest release, unzip it, and choose “Load unpacked” in chrome://extensions.