Free
After beta$0
10 GB Drive
Local AI and your own keys
Starter included Ask
Klypix is a local-first active context engine: it keeps a project’s files, decisions, and evidence current, so people and AI continue without starting over.
When a project changes hands, the files arrive. The decisions, evidence, and history behind them usually do not.
That is why every handoff creates another round of questions.
Klypix keeps files, evidence, decisions, and current context in one portable workspace you can inspect, organize, and send.
Mark screenshots and files beside the evidence, then review one connected brief.
Twelve issues. One project. One complete brief.
The recipient sees where to begin, what is final, why it changed, and what remains open.
The recipient gets the files and the project around them.
One actively managed state: supported coding sessions retrieve and update recorded decisions, corrections, evidence, handoffs, and active work, and a confirmed correction supersedes the stale answer.
One project. Many agents. One inspectable record.
Explore multi-agent continuity
What this is not: KLYPIX does not launch, supervise, route, or run agents. Presence, one-time messages, and exact-path overlap warnings are best-effort and same-machine; KLYPIX does not compare agents’ conclusions or guarantee they consumed a correction.
Snip the screen, open a file, or send from your phone. The useful part lands beside the project context it belongs to.
One shortcut searches recent clipboard items, your KLYPIX projects and the cards written inside them (a card is any note, screenshot, file, or decision on a project’s canvas), the folders you indexed, and files, apps and saved chats. Clipboard history is stored on your own machine; only items you pin can be synced across your devices, and only if you turn that on. How KLYPIX handles your data
See how one project keeps its current decisions, corrections, evidence, and active work visible to people and available to supported coding-agent sessions.
General projects can live inside Klypix. Software projects can keep their code in Git and carry their understanding beside it.
Same underlying format; different content profile.
The shared brain is inspectable. You can read the current decisions, correct one that has gone out of date, change what the project is focused on, and keep evidence beside the reasoning it supports. The canvas is the human control surface for the project: the place a person looks at what the project holds and fixes it.
Your real files, still connected
The actual bytes travel inside the project file, so what you send is not a set of links to a disk the other person does not have.
Decisions you can change
A decision that no longer holds is superseded, not silently overwritten. The old card is archived with a date, and later answers surface the correction.
Evidence beside the reasoning
Screenshots, files and marks stay attached to the decision they support, so a claim can be checked rather than taken on trust.
Answers that name their source
When KLYPIX answers from your own indexed documents it names the file, and the page where a document has pages.
Read on your machine
Asking your own folders runs on your computer. With no local model available it returns the matching passages rather than sending them anywhere.
Yours to take out
Export to Markdown and JSON Canvas whenever you want. The project brain is a versioned file you keep, not a record held somewhere you cannot reach.
Same workspace, same file, same project brain. Start where your work is today.
Free during beta. No card. No automatic charge.
Everything is free during beta. After beta, the complete local app stays free; Cloud is planned at $7 monthly or $70 annually.
$0
10 GB Drive
Local AI and your own keys
Starter included Ask
$7 monthly
100 GB Drive
6x included AI allowance
Included Agent runs
Target $12 to $15
250 GB minimum pooled target, expanding with seats
Planned seats, roles and billing
Planned presence and audit history
Custom annual
1 TB included target, with custom expansion
Planned SSO, SCIM and policy
Planned audit, DPA review and SLA
You will get at least 30 days notice before paid plans begin. Use it, then tell me what’s broken.
Questions before getting started? Email us at hello@klypix.com
Straight answers to the questions people actually ask us.
It argues back. Propose a decision and Klypix can surface the earlier decision it contradicts, the standing rule that disputes it, or the approach the project tried and reversed. Notes store what you wrote. A project brain can answer with the receipt.
Concurrent captures share a local write lock. At git time, the optional merge driver unions both sides after each machine registers it. If both sides changed one card, Klypix keeps both versions linked. Live overlap warnings are separate and currently same-machine.
Yours. The brain is a documented ZIP on your disk, with an Apache-2.0 parser. You can export to Markdown and JSON Canvas, extract the files, or open Obsidian canvas files directly.
Claude Code gets the deepest automatic integration. Codex gets MCP tools and the brain_sync gateway. Cursor, Cline, VS Code / Copilot, Gemini CLI and Antigravity get project MCP config plus rules. Windsurf uses global MCP plus a rule, while Aider uses the CLI path. Integration depth varies by host.
No. Git versions the code. Klypix keeps the decisions, rejected paths, corrections, and evidence the code cannot explain. brain.klypix lives beside the repository, so the understanding can travel with the branch.
No. Trackers assign work and dates. Klypix keeps the current decisions, corrections, evidence, and open questions that people and agents need while doing the work.
Your repo shows what exists. It rarely explains why another path was rejected, which constraint came from a customer, or which decision replaced an older one. The brain keeps that reasoning current and available to the next supported session.
For one tool and one stable project, often yes. The pain begins when decisions change or a second agent starts. A Klypix brain retrieves task-relevant context, records explicit corrections, stamps provenance, and surfaces declared exact-file overlaps on the same machine.
No. Passive memory appends and retrieves. Klypix manages state: a confirmed correction supersedes the stale answer, brain_challenge tests proposed decisions against standing rules and reversed approaches, and a decision anchored to code that has since changed is flagged before an agent relies on it.
On day one, only what you or your agent capture. Klypix does not invent project history. Its value compounds as decisions, corrections, evidence, and open questions are written back.
Yes, through the repository. Commit brain.klypix and each teammate can pull the same durable understanding. Live session presence and overlap warnings are currently machine-local, so two laptops do not see each other’s sessions.
Klypix does not create, launch, route, supervise, or run agents. It is a portable project workspace with a shared brain that the tools you choose can read and update.