One agent decides. The next should not start over.
brain.klypix is an actively managed state layer beside your code. Corrections supersede stale decisions, sessions declare their scope, and drifted claims get flagged. Versioned in Git. Served over MCP.
Independent coding sessions read the same versioned project understanding.
One project. Many agents. One inspectable record.
Two sessions begin changing the same files, and nobody finds out until review.
Claude Code in one terminal, Cursor beside it, Codex in another - vendor-neutral over MCP. Supported sessions can retrieve the same versioned decisions, corrections, evidence, and open questions. When sessions declare files through KLYPIX, same-machine presence and exact-path warnings can surface overlap. Advisory only: KLYPIX does not compare agents’ conclusions, guarantee message delivery, block edits, or supervise agents.
Session presence and one-time messages are best-effort and same-machine. Durable decisions travel only after a session records them in brain.klypix.
KLYPIX surfaces overlapping work; it does not block edits or decide for you.
Available today
Same-machine session presence while connected
Declared intent and exact-path overlap warnings
Best-effort same-machine messages
Versioned project decisions
Cross-tool retrieval from brain.klypix
A team brain merged through git
Human inspection and correction
Next - the team plane, not shipping
Cross-machine presence
Guaranteed message delivery and read receipts
Automatic comparison of agent conclusions
Branch and worktree awareness
Cross-machine overlap warnings
Roles and permissions
Team audit
Organisation views
From the bug you can see
Capture the bug once. Give the next agent the whole story.
Every re-briefing is a tax, in your time and in tokens. Keep the screenshot with the decision it contradicts, the correction that followed, and what the last session already tried. The next session starts already knowing.
Capture the visible bug and keep the screenshot as evidence.
Connect its project context: the decision, correction, and prior attempt around it.
Hand it to an agent when you choose. You confirm the run; KLYPIX never starts one for you.
Snip the bug · keep it as evidence · two sessions read the same brain
Concept illustration: one captured bug travels with the decisions and prior work around it.
Give your agents one project understanding to work from.
Product walkthrough · 2:21
See the shared project brain in action.
Watch how current decisions, corrections, evidence, and active work carry forward into supported coding-agent sessions.
Human controlInspect and correct the project understanding yourself.
Session continuityThe next supported session starts from current project state.
Visible historyDecisions and corrections stay connected to their evidence.
0:00 / 2:21
Real KLYPIX product walkthrough · Watch with sound
Work beside your agents.
You type, organize, and point at the evidence while an agent adds decisions and links in the same shared canvas. Both actions stay visible, placed, and reviewable.
Rotated refresh keys in auth-service. Correction linked to the June audit note.
closes → Sessions: strategy
On Screen
Rate-limit table, clipped in one keystroke - source linked.
Two writers. One brain. - when the KLYPIX app saves a project brain it re-reads the copy on disk inside the capture lock and unions it, and the merge aborts rather than emit a file missing a card.
Project Map / available now
Watch the code and the project explain each other.
Click Project Map in the desktop app and choose a checkout. If the tested local generator is missing, review and set it up once inside the app, or import a compatible graph.json. KLYPIX places a bounded code map beside the project brain.
What changes for the user: the map shows what connects to what; the brain explains why, what changed, and what is true now. A teammate or agent can begin with structure and intent instead of reconstructing both.
OpenOne Project Map button starts from a folder or an existing artifact.
UnderstandSearch the graph, open mapped source, and jump to brain cards tied to that file.
CompareRefresh history and the MCP tool show structural change beside current project context.
CarryShared links show the safe snapshot on phones while every checkout keeps its own local full graph.
Local and bounded: parsing runs in an isolated worker, the full explorer cannot access the network, and the canvas stores a compact snapshot instead of uploading the complete code graph. KLYPIX can also build the map itself — your files and the import connections between them, scanned on this computer in seconds with nothing to install. KLYPIX works with Graphify artifacts. Graphify and Astral uv are separate third-party tools; KLYPIX does not bundle, own, endorse, or claim a partnership with them. Before a user-level setup, the desktop shows the pinned versions, exact commands, download/storage effects, licenses, and alternatives, then requires explicit confirmation. Setup does not scan the project. Local generation remains a separate click, and artifact import remains available.
Code graph shows the structureProject brain preserves the intentPeople and agents receive both
Old decisions should not outlive the reasons behind them.
This is what active means: Klypix tests new decisions against standing rules, supersedes what was reversed, and flags what has gone stale. Corrections, provenance, and receipts stay attached to the decisions your agents use next.
It challenges decisions with receipts.
Propose a decision and brain_challenge can surface the rule it disputes or the earlier approach the project tried and reversed.
brain_challenge1 conflict found
Proposed decision
Keep the raster radar above zoom 9.
Challenge with receipt
You reversed this after the zoom test. The current decision uses on-device vector radar.
correction · Jun 12source linked ↗
It warns when a decision may be stale.
A decision can cite the exact code it was decided against. When that file’s committed content moves on, the next Claude Code session’s brief flags the card as drifted and hands the agent the marker to re-verify or correct it.
It needs an evidence anchor on the card, and it runs in the Claude Code hook path. It detects that the cited code changed - never that the claim became false.
The anchored code changed 3 commits ago. Review this decision before using it.
A brain in every repo.
A single brain.klypix lives beside your code: the project’s active state. Supported coding sessions can read it, write back what they learn, and challenge new decisions against what the project already knows.
Same format, two content profiles: project.klypix carries the project’s files and folders inside it; brain.klypix carries only the understanding, beside code that stays in Git.
MCP hosts receive structured text from the same brain. The Windows app renders it as a visual board you can inspect and edit.
Klypix is built with its own project brain, written by multiple live agent sessions.
Session briefbrain.klypix
Focus
Ship the audience landing journeys and preserve the shared proof.
Correction
The Drive portal is already live; do not repeat the stale rollout note.
Open ?
Measure which journey turns understanding into the next action.
A task-relevant brief for the next supported coding session.
$ npx klypix-mcp install
# every supported tool you have installed - then it proves the connection
$ npx klypix-mcp link
# optional: re-project all 14 managed files, installed or not
100%15 of 15 coordination checks passed in a two-client conformance run
20 questionsfrozen retrieval evaluation against Klypix’s 2,380-card project brain
0 cloudthe published retrieval score was computed on-device; no cloud model graded it
Internal measurements, 14 August 2026, on a frozen 113-question evaluation set. Current retrieval result: 62% top-5, 67% top-10, 69% top-20. Not independently validated.
Start with one command. Link the project when you add more tools.
Files, evidence, decisions, conversations, people and agents should not become separate versions of the same project. Klypix keeps them connected through one portable workspace and a shared brain.
«لكل مشروع عقل.»
Free during beta. No card. No automatic charge.
Free while we earn your trust.
Everything is free during beta. After beta, the complete local app stays free; Cloud is planned at $7 monthly or $70 annually.
Free
After beta
$0
No subscription
10 GB Drive Local AI and your own keys Starter included Ask
KLYPIX Cloud
Recommended
$7 monthly
$70 annually, save $14
100 GB Drive 6x included AI allowance Included Agent runs
Cloud for Teams
Coming soon
Target $12 to $15
per member monthly
250 GB minimum pooled target, expanding with seats Planned seats, roles and billing Planned presence and audit history
Enterprise
Coming soon
Custom annual
For security and procurement needs
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.
Straight answers to the questions people actually ask us.
What can the brain do that plain notes can’t?
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.
What happens when two agents change the brain at the same time?
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.
Whose file is it? What if I stop using KLYPIX?
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.
Which AI tools can read it?
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.
Does Klypix replace Git?
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.
Is KLYPIX a project management tool? Where is the Gantt chart?
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.
What about Graphify - do I still need KLYPIX?
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.
Isn’t a CLAUDE.md or rules file enough?
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.
Is this just RAG or a memory plugin?
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.
I already have a working project. What does a fresh brain know on day one?
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.
Can my teammate and I use one brain from two computers?
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.
What is KLYPIX not?
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.
