# I got a new computer. How do I move my setup?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Sign in, install Claude Code and [Node.js](http://support.gilb.com/help/how-do-i-install-nodejs-and-check-which-version-i-have), connect with "▸ CONNECT AI", make an AI vault, press "Bind AI", and give it access.

## Deeper

Also asked:

I got a new phone or computer. Does my passkey come with it? Only if your device's maker moves it: Apple says passkeys "sync across a user's devices using iCloud Keychain". If not, sign in with the e-mail code, which works on any device, and add a passkey there; [the answer on signing in with a passkey](http://support.gilb.com/help/how-do-i-sign-in-with-a-passkey) shows how.

Your vaults, the stores for your records, are kept on GilbPlatform, not on your computer, so there is nothing of them to move. You set up the new computer the way you set up the first one, and the old one keeps working until you cut it off. Only a project that Kai-Zen keeps in a folder on your computer, rather than in a vault, is on the old computer; copy that folder yourself.

On the new computer, in this order:
1\. Sign in to GilbApp at gilb.com/app with the e-mail code; another computer needs its own sign-in. [The answer on signing in to GilbApp](http://support.gilb.com/help/how-do-i-sign-in-to-gilbapp) shows how. To sign in there with Touch ID, add a passkey on it, as the answer on signing in with a passkey shows.
2\. Install Claude Code and [Node.js 18 or newer](http://support.gilb.com/help/how-do-i-install-nodejs-and-check-which-version-i-have), and sign in to Claude Code with your Claude account. [The answer on installing Claude Code](http://support.gilb.com/help/how-do-i-install-claude-code) shows how.
3\. Connect the computer with "▸ CONNECT AI": type a short name and do its steps 1 to 3, as [the answer on connecting your computer to your vault](http://support.gilb.com/help/how-do-i-connect-my-computer-to-my-vault) shows. The new computer gets its own Client ID, the name GilbPlatform gives this AI.
4\. Make a new AI vault for it, bind the new Client ID with "Bind AI", and give that AI vault access to the vaults it should work in. The answers on [making an AI vault](http://support.gilb.com/help/how-do-i-make-an-ai-vault-and-connect-claude-code-to-it) and on [giving your AI access](http://support.gilb.com/help/how-do-i-give-my-ai-access-to-a-vault) show how.
5\. To use Claude Code in GilbApp's chat, set up the bridge and pair it again; for Grok, press "Connect" again in the new browser. [The answer on connecting your AI to GilbApp chat](http://support.gilb.com/help/how-do-i-connect-my-ai-to-gilbapp-chat) shows both.

Step 4 needs a new AI vault because an AI is bound once, to one AI vault, and an AI vault takes one AI: GilbPlatform does not bind the new Client ID to the AI vault your old computer uses.

When you stop using the old computer, cut it off. In each vault you gave its AI, press "×" on the old AI vault's line, as [the answer on taking access away](http://support.gilb.com/help/how-do-i-take-access-away) shows. Sign out of GilbApp in its browser. If Claude Code was paired with the chat there, press "Disconnect" in that browser; with "Option Always On", remove the bridge by pasting this line in Terminal and pressing Return:
node \~/.gilb-claude-code-bridge.mjs --uninstall
If the old computer is lost or stolen, the answer on the "Download key" and [losing a key](http://support.gilb.com/help/what-is-the-download-key-and-what-if-i-lose-it) says what else to do.

This answer connects the new computer as a new AI. It does not cover copying the folder .gilb-connector, which holds the old AI's private key, from the old computer.

This answer is for a Mac and Claude Code. Under "▸ CONNECT AI", "Linux" says "These Linux steps need further testing." On "Windows", "Codex" is chosen for you, and with "Claude Code" chosen it says "Claude Code on Windows is not available yet. Choose Codex." With Codex, OpenAI's AI for writing code, steps 2 to 4 are Codex's own steps in "▸ CONNECT AI": [the answer on making an AI vault and connecting Codex to it](http://support.gilb.com/help/how-do-i-make-an-ai-vault-and-connect-codex-to-it) shows them.

Source: GilbPlatform 670005cc \(live at https://id.gilb.com/version, read 12 November 2026\): src/auth/bind-agent-vault.ts:135-160 \(a second client is a different anchor, so a vault that is already seated is refused; "this client already acts as … an acting identity is adopted once"\). GilbApp 96968de7 \(live at https://gilb.com/app/version.json, read 12 November 2026\): src/components/VaultAccessManager.tsx:71-80, :97 and :909-934 \("▸ CONNECT AI" steps, "Bind AI"\); src/lib/base/gilbConnector.ts:66-80 \(each short name its own AI and Client ID\). Live help pages, sentences shared: How do I sign in to GilbApp?; How do I sign in with a passkey?; How do I install Claude Code?; How do I connect my computer to my vault?; How do I make an AI vault and connect Claude Code to it?; How do I give my AI access to a vault?; How do I connect my AI to GilbApp chat?; How do I take access away?; How do I disconnect my AI?; How do I continue a project with Kai-Zen? New page in the same set: What is the "Download key", and what if I lose it?. Codex \(added 13 November 2026\): GilbApp 4557cf80 \(https://gilb.com/app/version.json, read 13 November 2026\), src/components/VaultAccessManager.tsx:105 \("Claude Code on Windows is not available yet. Choose Codex."\), :109 \("Choose Sign in with ChatGPT. Hand-offs run only on your ChatGPT sign-in, never on an API key."\), :180-183 and :1014-1015 \("Claude Code" and "Codex" under the computer tabs\), :581-657 \(the Codex steps\); src/lib/base/gilbConnector.ts:44-79. OpenAI, read 13 November 2026: https://learn.chatgpt.com/docs/pricing \("ChatGPT Work and Codex are included in your ChatGPT Free, Go, Plus, Pro, Business, Edu, or Enterprise plan"\), https://github.com/openai/codex \(npm install -g @openai/codex; "Sign in with ChatGPT"\). Live answer: How do I make an AI vault and connect Codex to it? Apple, https://support.apple.com/en-us/102195 \("sync across a user's devices using iCloud Keychain"\), read 14 November 2026.
