instibrain
Sign in
instibrain  /  sync client

The sync client keeps your folder and the brain in step.

It owns the files, the keys, and the sync. Pages land as plain markdown, and nothing is overwritten.

Request access → Connect Claude Code
this machinereal output
$ instibrain status device 9f3c1a84-62b7-4de0-9a15-7c4e2f08d331 root /home/you/instibrain/spaces/acme cursor 2026-09-13T09:41:22.174382Z tracked 7 live, 2 tombstones on disk 7
no key ever reaches our server
day one

Day one starts from your folder.

No import, no new editor. Your files stay where they are.

  1. step 1 Install

    One line, in a terminal.

    Mac, Linux, Windows
  2. step 2 Link your folder

    A code from Devices. Every file becomes a page.

    nothing moves
  3. step 3 Seal the rest

    A second folder. Its pages leave encrypted.

    your key only
  4. step 4 Your phone too

    The AI on your phone reads the open spaces.

    it holds no key
the first day~/acme-brain
$ curl -fsSL https://instibrain.ai/install.sh | bash $ instibrain link K7QM-2XPA ~/acme-brain pulled 0 pushed 214 adopted 214 linked ~/acme-brain to Acme; it syncs now and on every change $ instibrain link R4TN-8WJC ~/acme-finance pulled 0 pushed 31 adopted 31 laid out the sealed space from its template on this computer linked ~/acme-finance to Finance; it syncs now and on every change
one thing to know first

An AI reading a file sees plaintext, sealed pages included. Our server cannot; your AI can.

the cycle

Each burst of saves runs one cycle: survey, pull, adopt, push.

A clash stops the cycle, and nothing is overwritten. It refuses a path through a symbolic link, outside the folder, or naming another page in other letters. The brain tells an old client which version to install, and raises that floor only once every linked computer runs it.

  1. 1surveyRead the disk

    What changed since the last cycle.

  2. 2pullTake the brain's changes

    What others wrote lands as files.

  3. 3adoptNew files become pages

    Each gets its id.

  4. 4pushSend yours

    A clash comes back as 409 and stops here.

then wait for your next save, or the brain's next change
~/instibrain/spaces/acme  ·  two devices, one conflicting edit
$ tail -n 0 -f ~/Library/Logs/instibrain-computer.log # a save on this device pulled 0 pushed 1 adopted 0 # the other laptop had already pushed the same page pulled 0 pushed 0 adopted 0 conflicts 1 conflict: pricing/floors.md — server copy written beside it, then 'instibrain resolve pricing/floors.md' # merge the two files by hand, or let your AI do it, then $ instibrain resolve pricing/floors.md resolved pricing/floors.md

The server copy lands beside yours. No cycle pushes over an open conflict.

the commands

Most days you type none.

The watch syncs every burst of saves and takes the brain's changes as they come. The rest link, check, and keep your keys.

Runs by itself
  • watchA cycle per burst of saves
  • service installThe watch, from login on
  • updateThe newest client, daily once setup turns it on
most days, all that runs
Links
  • linkA code links a folder
  • link --allEvery space you read
  • link --spaceOne more space, no code
  • spacesWhat you read, and your role
  • setupStatus line, daily update, defaults, each asked first
Works
  • mcpYour AI on this computer, working as you
  • openClaude or Codex, from a menu
  • windowA session in its own window
  • specialistsThe specialists you read
  • specialist adoptA folder becomes a specialist
  • toolRuns the approved version
Checks
  • statusWhat it tracks
  • checkDead links, orphan pages
  • guard --scanWhat the guard would stop
  • resolvePushes a merged file
  • moveA page to another space, after a review
Keys
  • approveAdmits a new computer
  • key pendingComputers waiting for you
  • key publicSafe to paste anywhere
  • key membersEach fingerprint, beside its name
  • key pinTrust a chain once
  • key backupYour keys, under a passphrase
  • key restoreRebuilds an empty computer
why a chain, not a list

Each admission is a signed entry, verified from the first before a key is taken. The threat model has the detail.

a teammate's day one

Their AI arrives knowing the company.

Install, link, connect. Get started walks each step. Leaving is one step: the grant goes, and a sealed space gets a new key. Pulled copies stay.

One line

The installer links every space they read.

instibrain link --all
Every space, as files

A folder of plain markdown each.

~/instibrain/spaces/
Their AI

Knows the company before it writes a line.

Claude Code, Codex

Your pages stay plain files on every computer you link.

The protocol is on How it works; the keys are on the security page.

Request access → Connect Claude Code