brain_folder
Idempotent
Configure where your personal AI memory is stored and which PCs share it: point it to a synced folder or local store, share access with another PC, or export/import the memory file.
Instructions
Where the user's own personal memory lives, and which of their own PCs share it.
Not for teams: project brains shared with teammates are brain_checkpoint.
Anything that changes where the memory goes (`path`, `share_existing`, `export_to`,
`import_from`) is not done from here: the tool returns `command`, and the user runs it in
a terminal. A web page or file you read can then never move their memory somewhere else.
Show the user the command, say what it does, and call this again without arguments after
they ran it to confirm. Codes and passwords appear only in that terminal.
Call it with `path` when the user names a folder for their memory, e.g. "use my Google
Drive's Turnbook folder as my brain". A folder that OneDrive, Google Drive or Dropbox
syncs makes the same memory available on every PC where the user chooses it too; nothing
else is needed. Without `path` it reports the current folder and the devices writing to it.
`path="local"` keeps the brain in this PC's own Postgres instead, shared the instant it is
written (no sync delay).
Other PCs: when the user asks to let their other PCs use this brain ("다른 PC도 붙게 해줘"),
call it with `path="share"`. It opens this PC's Postgres to the local network and Tailscale
(Windows may ask the user to approve a firewall rule once) and returns a
`connection_code` in the terminal. On the other PC the user runs
`turnbook folder <that code>`; it contains the password, so say not to post it anywhere
public.
Codes: when the user pastes any Turnbook code ("gm1." for their own other PC, "gmt1."
for a team invite), call this with `path=<the code>`; it does the right thing for either
(a team invite is joined at once), so never ask the user which kind it is.
`share_existing=true` sends what this PC remembers and the shared memory lacks (only that:
it also repairs turns that missed a hub that was down). It uploads
it to wherever the folder syncs. Set it only when the user has explicitly agreed to that.
`reindex=true` brings the search index up to date (links new memories, embeds unembedded
ones). Saving already does this; it is for a large imported backlog.
Moving a whole memory as one file ("내 기억 파일로 내보내줘", "이 기억 파일 가져와"):
`export_to=<file path>` writes every memory and conversation turn into that file;
`import_from=<file path>` adds such a file's contents to this memory, skipping what is
already here. Only when the user asks. Tell them the file holds their entire memory
(secrets were masked when saved), so keep it private like a diary.
With `project=<folder>`, `export_to` writes only the conversations held in that folder
(or below it) and the memories drawn from them ("이 프로젝트 대화만 넘겨줘"): every word
of those conversations goes in the file, so say so. Facts saved on request carry no
folder and are not included.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | ||
| project | No | ||
| reindex | No | ||
| export_to | No | ||
| import_from | No | ||
| share_existing | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||