One project.
One shared brain.

1. The missing layer
   1. Every new agent session starts from zero. Your project’s decisions live in chats, files and people’s heads.
   2. KLYPIX adds the missing layer. One shared, inspectable brain between your agents and your project.
   3. Agents read it. Agents add to it. You correct it.
   4. It’s one file in your project. Portable, inspectable, yours.

   Voice-over: Starting a new coding session often means explaining your project all over again: the stack, the conventions, the thing you ruled out. Nobody wrote those decisions down in one place. KLYPIX gives you and your agents one shared place to record them, and to correct them when things change. Come back a month later and you can read what was decided, and the thinking that led there. So the next session can start from what you settled, instead of from zero.

2. What Klypix is
   1. A desktop app for your whole project. For Windows.
   2. Drop in anything. Files, folders, links, video and voice notes.
   3. Real files, not shortcuts. Copied into one .klypix file, so they keep working if the originals move.
   4. Group it. Connect it. Decisions stay next to their evidence.
   5. Zoom from one note to the whole project.
   6. Your agents can read it. Cards, file names, folder paths, links and decisions.

   Voice-over: No project lives in one place. Part of it is in folders, part in a browser tab, part in a conversation nobody will find again. KLYPIX holds the whole project in one portable workspace on Windows. Drop in whatever the project is made of; the real files are copied inside, so they keep working even if you move the originals. Group what belongs together, and connect every decision to the evidence underneath it. Then step back and see the shape of it. Your coding agents can read that same workspace: the cards, the links, the decisions, and the names and paths of your files, but not inside a video. So you stop briefing them from scratch every time.

3. iPhone and Drive
   1. Share from your iPhone. From any app. It’s encrypted before it leaves the phone.
   2. Your PC can be off. It waits safely in the cloud.
   3. Open it in Drive meanwhile. At drive.klypix.com: preview it or download it.
   4. It lands in the space when your PC is back.
   5. One tap puts a space on your iPhone. Then send straight to it.

   Voice-over: You find something your project needs on your iPhone, and it lands in the camera roll with everything else you meant to come back to. KLYPIX lets you send it straight to the project, from whatever app you are in. It is encrypted on your iPhone before it leaves. Your PC does not have to be awake: it waits in the cloud, and meanwhile Drive lets you view or download it. When KLYPIX is running on your PC and connected again, the item lands in your space. And one tap adds the space as a destination on your iPhone, ready for your next share.

4. Reels to text
   1. Share an AI reel to KLYPIX.
   2. Pick a space.
   3. It goes to your PC. PC off? It waits in the cloud until it’s back.
   4. Turn the reel into text. Right-click, Read contents. Works on public reels.

   Voice-over: The reel you saved to watch later is forgotten by the time you reach your desk. Share a public one to KLYPIX, then right-click on your PC and choose Read contents. A cloud model turns its speech into timestamped text, beside your project's files.

5. Connect your agents
   1. One command in your project. It creates brain.klypix if there is none, and connects the AI tools it finds.
   2. Already have a brain? A teammate committed brain.klypix? Install keeps it as it is and connects your tools.
   3. Several AI tools, one brain. Claude Code reads and saves by itself. In tools with MCP, the agent calls the brain.
   4. Two sessions on one PC? Sessions can list the files they will touch. Same file? Both get a heads-up.
   5. A teammate on another PC? Commit brain.klypix with your code. Once each teammate runs install, a pull merges both sides’ cards.
   6. Check it any time. npx klypix-mcp doctor

   Voice-over: You brief one tool, then the next, then the one your teammate prefers: the same project explained three times. One command changes that. Run it inside your project: KLYPIX creates the shared brain if there is none, then connects the supported tools it finds on this machine. Claude Code reads it and writes to it by itself; in other tools, your agent calls it. Two sessions on the same PC can each declare the files they are about to touch; name the same one and each gets a heads-up, advisory, nothing blocked. Commit it with the code; after each teammate has run install, a pull brings both copies together. Different tools, one current understanding.

6. Parallel sessions
   1. Two sessions. One brain. Claude Code and Codex on one PC, reading brain.klypix in your repo.
   2. Same file? Each gets a heads-up. Advisory. Nothing is blocked.
   3. Leave a note for a closed session. KLYPIX keeps it for up to 7 days. You relay nothing.
   4. It arrives when that session next acts. Reopen it when you like. Nothing starts or wakes a session.
   5. All on your machine. One brain file in your repo, not one tool’s private notes.

   Voice-over: Two agent sessions on one PC, Claude Code and Codex, read one brain file in your repo. Both declare the same file? Each gets a heads-up. Nothing is blocked. Codex closed for the day? Claude leaves it a note, and KLYPIX keeps it for up to seven days. You don't copy anything across. Reopen Codex, and the note reaches it the moment it next acts. Nothing starts or wakes a session for you. All on your machine.

7. Your whole team
   1. Your team works on more than one PC. Each PC keeps its own copy of the project brain.
   2. Share the brain once. An encrypted copy goes to the KLYPIX cloud. Invite the teammates who edit it.
   3. It syncs by itself. When you open the brain, when an agent writes to it, and when you come back to it.
   4. Your teammate’s agents start with it.
   5. Cards from both PCs are merged. The dot on each PC shows whether its copy is in sync.

   Voice-over: When a team shares a project, the files get shared and the reasoning stays on one machine. Your teammate's agent starts cold on what you settled last week. KLYPIX shares the brain: every machine holds the whole brain, not a link to it. Share it once, invite the teammates who will edit it, and each copy syncs by itself while that brain is open in KLYPIX. Their agents can pick up the current decision, cards added on both PCs are merged, and a dot on the sync button tells you if your copy is current. One project. One shared understanding.

One project. One shared understanding.

1. Map your repo. KLYPIX’s own scan maps your files, and the imports between JS/TS files, on this PC. Nothing to install.
2. Code beside the decisions. Pick a file to see what it connects to, and which brain cards name it.
3. Your agent gets both. One read-only call returns the matching code and the current decisions, side by side.
4. When the code changes. The card says when the code or the map has changed. Rescan and refresh to see the difference.
5. Check the brain against the code. A read-only check lists brain cards that point at files now gone or moved. You fix them.
6. See the whole brain. Lenses show freshness, who wrote what, and open questions. Views only; nothing changes.

One project. One shared understanding.

Voice-over: A folder tree tells you where a file sits. It doesn't tell you why. KLYPIX maps your repository on this PC, with its own scan and nothing to install, so the code sits beside the decisions. Choose a file and you see everything it connects to, and the brain cards that mention it. Your agent can request both in one read-only call. When the code moves on, the card says so, and a separate read-only check lists the cards whose files have gone or moved, for you to correct. The lenses are views of the whole brain: how recently a card changed, who wrote it, what is still unanswered. Nothing is altered.

1. Every new agent session starts from zero. Your project’s decisions live in chats, files and people’s heads.
2. KLYPIX adds the missing layer. One shared, inspectable brain between your agents and your project.
3. Agents read it. Agents add to it. You correct it.
4. It’s one file in your project. Portable, inspectable, yours.

One project. One shared understanding.

Voice-over: Starting a new coding session often means explaining your project all over again: the stack, the conventions, the thing you ruled out. Nobody wrote those decisions down in one place. KLYPIX gives you and your agents one shared place to record them, and to correct them when things change. Come back a month later and you can read what was decided, and the thinking that led there. So the next session can start from what you settled, instead of from zero.

1. Your team works on more than one PC. Each PC keeps its own copy of the project brain.
2. Share the brain once. An encrypted copy goes to the KLYPIX cloud. Invite the teammates who edit it.
3. It syncs by itself. When you open the brain, when an agent writes to it, and when you come back to it.
4. Your teammate’s agents start with it.
5. Cards from both PCs are merged. The dot on each PC shows whether its copy is in sync.

One project. One shared understanding.

Voice-over: When a team shares a project, the files get shared and the reasoning stays on one machine. Your teammate's agent starts cold on what you settled last week. KLYPIX shares the brain: every machine holds the whole brain, not a link to it. Share it once, invite the teammates who will edit it, and each copy syncs by itself while that brain is open in KLYPIX. Their agents can pick up the current decision, cards added on both PCs are merged, and a dot on the sync button tells you if your copy is current. One project. One shared understanding.