# How do I make an AI vault and connect Codex to it?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Press "Codex" in "▸ CONNECT AI", paste the lines, type a name, press "Mint AI vault", paste the Client ID, press "Bind AI", restart Codex.

## Before you start

A Mac, Linux or Windows computer [signed in to GilbApp](http://support.gilb.com/help/how-do-i-sign-in-to-gilbapp), with [Node.js 18 or newer](http://support.gilb.com/help/how-do-i-install-nodejs-and-check-which-version-i-have) \(from https://nodejs.org\), a ChatGPT account, and a vault of your own that [no one else can read or write](http://support.gilb.com/help/how-do-i-see-who-can-reach-my-vault), such as the one you made at sign-up. The pictures show a made-up person on a test site; your screen shows your own name and address.

## Steps

1. Open "▸ CONNECT AI" on your vault.

   Press "Main menu", the button at the top left, next to your profile picture, that shows the name of the section you are in, and choose "Vaults". Press the panel button at the top right of your vault's card, scroll down the pane on the right and press "▸ CONNECT AI".

   The AI vault is made inside this vault, so use a vault that no one else can read or write, and no vault above it. "▸ CONNECT AI" opens on the tab for your computer: "macOS", "Linux" or "Windows".

   ![The vault's pane on the right is scrolled down below "▸ GRANT ACCESS", and the fold "▸ CONNECT AI" is outlined in orange.](http://support.gilb.com/help/media/d140c314dd22c1ad.png)
   What you see: The pane on the right shows your vault's details, scrolled down past "OTHER PEOPLE AND GROUPS ACCESS RIGHTS" and the closed fold "▸ GRANT ACCESS". The closed fold "▸ CONNECT AI" just below is outlined in orange: click it to open it.
2. Press "Codex" under the tabs.

   Press "Codex", the button next to "Claude Code" just under the tabs. The steps below change to Codex's and start with "Use GilbPlatform from Codex. Do these steps in order."

   On "Windows", "Codex" is chosen for you: with "Claude Code" it says "Claude Code on Windows is not available yet. Choose Codex." The short-name box at the top is not needed for a first Codex AI; leave it empty, and the lines below name the AI GilbPlatform. On "Linux" GilbApp says "These Linux steps need further testing." The pictures show the short name example typed in; leave the box empty and your lines name the AI GilbPlatform.

   !["▸ CONNECT AI" is open with "macOS" chosen, and the button "Codex" in the row under the tabs is outlined in orange.](http://support.gilb.com/help/media/9c293739f97aad36.png)
   What you see: Under "▾ CONNECT AI", the tabs "macOS", "Linux" and "Windows" show, with "macOS" chosen. Just below them, a second row has "Claude Code", chosen, and "Codex". The button "Codex" is outlined in orange: click it. The steps below then start with "Use GilbPlatform from Codex. Do these steps in order."
3. Install Codex and sign in with ChatGPT.

   Open a terminal, the window where you type commands: on a Mac [the Terminal app](http://support.gilb.com/help/how-do-i-open-the-terminal-on-my-computer), on Linux your terminal app, on Windows PowerShell. Copy the first line under "Install Codex and sign in.", paste it there and press Return \(Enter on Windows\):
   npm install -g @openai/codex

   npm is the installer that comes with Node.js; this line installs Codex, OpenAI's AI for writing code. Then paste the second line and press Return:
   codex login
   GilbApp says: "Choose Sign in with ChatGPT. Hand-offs run only on your ChatGPT sign-in, never on an API key." A hand-off is one agent passing work to another. Finish the sign-in in your browser; the terminal shows "Successfully logged in." No picture: this happens in the terminal and the browser, outside GilbApp.
4. Paste the connector lines in your terminal.

   Copy the line under "Download the connector.", paste it in the terminal, not inside Codex, and press Return; then do the same with the line under "Add it to Codex.". On a Mac or Linux they read:
   curl -fsSL 'https://gilb.com/app/gilb-connector.mjs' -o \~/.gilb-connector.mjs
   codex mcp add GilbPlatform -- node \~/.gilb-connector.mjs --hop-cli codex

   On Windows, in PowerShell, they read:
   Invoke-WebRequest -UseBasicParsing -Uri 'https://gilb.com/app/gilb-connector.mjs' -OutFile "$HOME\\.gilb-connector.mjs"
   codex mcp add GilbPlatform -- node "$HOME\\.gilb-connector.mjs" --hop-cli codex
   The first downloads the connector, the small GilbPlatform program that lets Codex reach your vaults, and shows nothing, just a new prompt line. The second shows "Added global MCP server 'GilbPlatform'."; an MCP server is a small program that gives an AI extra tools. The "⧉" at the end of each line in GilbApp copies it. No picture: this happens in the terminal.
5. Add the two time lines to Codex's settings file.

   Copy the first line under "Give hand-offs time to finish.", paste it in the terminal and press Return. It opens Codex's settings file, config.toml; find the line \[mcp\_servers.GilbPlatform\], paste the two lines GilbApp shows below it on the next line, and save.

   On a Mac the line opens the file in TextEdit:
   open -e \~/.codex/config.toml
   On Linux it opens it in nano:
   nano \~/.codex/config.toml
   On Windows it opens it in Notepad:
   notepad "$HOME\\.codex\\config.toml"
   The two lines are:
   startup\_timeout\_sec = 90
   tool\_timeout\_sec = 2000
   They give the connector time to start and a hand-off time to finish. GilbApp says: "You see: the two lines under \[mcp\_servers.GilbPlatform\]." No picture: this happens in a text editor, outside GilbApp.
6. Start Codex and copy its Client ID.

   In the terminal, type codex and press Return to start Codex. In Codex, paste this line and press Return:
   call the GilbPlatform tool gilbplatform\_whoami and show me its full answer

   If Codex asks to allow the tool, choose Yes. The answer shows "state: not bound" and the Client ID, the name GilbPlatform gives this AI, on its own line; this first run also signs the AI in once. To copy the Client ID exactly, open a new terminal window and paste the line under "Or print the Client ID in a new terminal window:". On a Mac or Linux it reads:
   cat \~/.gilb-connector/default/client-id
   On Windows it reads:
   Get-Content "$HOME\\.gilb-connector\\default\\client-id"
   Copy the one line it shows. No picture: this happens in Codex and the terminal.
7. Type a name in "AI vault name" and press "Mint AI vault".

   Under "Name the AI vault that will access your Vaults on the GilbPlatform \(for example: AIAssistant\):", click the box "AI vault name", type a name and press "Mint AI vault". The screen says "AI vault live:" and the AI vault's address, ending in /vault; keep it.

   The button is dimmed while the box is empty. If someone else can read or write this vault, or a vault above it, the mint is refused: "This vault is shared, so its readers would also see an AI vault inside it. Remove the others' Read and Write on this vault, mint the AI vault, then grant them again. Access you grant after the mint does not reach the AI vault." Do as it says, [taking their access away](http://support.gilb.com/help/how-do-i-take-access-away) first.

   ![A name is typed in the box "AI vault name", and the button "Mint AI vault" under it is outlined in orange.](http://support.gilb.com/help/media/cc521ccaa6a01ead.png)
   What you see: In the right pane, inside the Codex steps, the box "AI vault name" holds the name you typed. The button just below it, "Mint AI vault", is outlined in orange: click it. The grey text under it reads "You see: AI vault live: and its address." and says Mint is refused if this vault is shared with others.
8. Paste the Client ID in "Client ID" and press "Bind AI".

   Under "Copy the Client ID from your Codex chat, paste it here, then press Bind AI.", click the box "Client ID", paste the Client ID and press "Bind AI". The screen says "This client now acts as this vault."

   Spaces, quotes and brackets at its ends are taken off for you. Do not hide the pane between "Mint AI vault" and "Bind AI": "Bind AI" works on the vault that is open. At the first bind the box "This AI may create vaults" shows, ticked for you; untick it to stop your AI making new vaults inside its AI vault.

   ![A Client ID is pasted in the box "Client ID", and the button "Bind AI" under it is outlined in orange.](http://support.gilb.com/help/media/0adb89fe45580b88.png)
   What you see: In the right pane, a green line under "Mint AI vault" reads "AI vault live:" and the new AI vault's address. Below it, "Copy the Client ID from your Codex chat, paste it here, then press Bind AI." and the box "Client ID" holding a string of letters and digits. The button "Bind AI" is outlined in orange: click it. Below follow "Restart Codex." and the steps for giving access and working in a vault.
9. Restart Codex.

   In Codex, type /quit and press Return, then type codex and press Return to start it again.

   GilbApp says: "Codex reads the GilbPlatform tools only when it starts." No picture: this happens in the terminal.
10. Tell Codex which vault to work in.

    Give the AI vault "read" and "write" on the vault first, as the answer [How do I give my AI access to a vault?](http://support.gilb.com/help/how-do-i-give-my-ai-access-to-a-vault) shows. Then type this in Codex, with your vault's name, and press Return:
    use the GilbPlatform vault &lt;the vault's name\>

    When Codex asks to allow gilbplatform\_use\_vault, choose Yes for this time, not always: each vault switch stays your decision. Your AI reaches only the vaults you give its AI vault access to. No picture: this happens in Codex.

## Deeper

Also asked:

Codex asks me to allow a GilbPlatform tool. Should I? For the who-am-I line in step 6, choose Yes. When Codex asks to allow gilbplatform\_use\_vault, choose Yes for this time, not always: each vault switch stays your decision.

What is tested, plainly. A hand-off from Codex to another agent has run on a Mac: it starts a second Codex on your ChatGPT sign-in, and the hand-offs we ran took about 1 to 4 minutes; long hand-offs use more of your plan. The Windows lines were run in PowerShell on Windows test machines but have not yet been tried by a person on their own PC. Under "Linux" GilbApp says "These Linux steps need further testing."

Hand-offs run only on your ChatGPT sign-in. Signed in with an API key, a hand-off stops with "Codex is not signed in with ChatGPT, so the hand-off was stopped. Run: codex login and choose Sign in with ChatGPT." If it says "This Codex version's feature list is not one the connector knows, so the hand-off was stopped.", write to support@gilb.com.

Other answers to "Bind AI": "unknown client" means the Client ID is not exact; copy it again from the file. "client has no machine principal yet" means the AI never signed in \(the rest of that sentence is for developers\); run the who-am-I line in Codex, then bind again. "this client already acts as" means this AI is bound to another AI vault already: an AI is bound once, to one AI vault. If that happens on a first Codex AI, another AI on this computer uses the same unnamed setup: type a short name in the box at the top of "▸ CONNECT AI" and do steps 4 to 8 again with the new lines, which then use gilb- and that name.

Only you, who made it, can bind it. No one can be given access to read or write an AI vault. Under "This AI may create vaults" the screen says "When on, this AI can create new vaults from Claude Code."; We have not tested that from Codex.

GilbApp's steps install Codex with npm; OpenAI's own page, read 13 November 2026, shows a different installer line. If the npm line fails, write to support@gilb.com.

Codex is OpenAI's and may change its commands and sign-in; OpenAI's page on the Codex command line is https://learn.chatgpt.com/docs/codex/cli \(read 13 November 2026\). For Claude Code, see: [How do I make an AI vault and connect Claude Code to it?](http://support.gilb.com/help/how-do-i-make-an-ai-vault-and-connect-claude-code-to-it)

This answer is written for a computer screen.

Source: GilbApp 49b1ae53 \(https://gilb.com/app/version.json, read 13 November 2026; Connect AI unchanged since 4557cf80\): src/components/VaultAccessManager.tsx:75 \("These Linux steps need further testing."\), :79-80 \(step lead for the AI vault name\), :98 \(short name label for Codex\), :103-114 \(the Codex texts\), :149-175 and :180-223 \(the computer tabs and the "Claude Code" and "Codex" buttons\), :277-279 \(Codex chosen for you on Windows\), :500-570 \("AI vault name", "Mint AI vault", "Client ID", "Bind AI" and their messages\), :572-657 \(the Codex steps, "Restart Codex.", "choose Yes for this time, not always"\), :1009-1018 \("▸ Connect AI", tabs, buttons, Windows sentence\), :1031-1045 \(the short-name box\); src/lib/base/gilbConnector.ts:44-91 \(the Codex lines for a Mac or Linux and for PowerShell, the who-am-I line, the Client ID line\). Connector gilb-connector 0.6.1 \(https://gilb.com/app/gilb-connector.mjs, read 13 November 2026\): --hop-cli codex; "Codex is not signed in with ChatGPT, so the hand-off was stopped. Run: codex login and choose Sign in with ChatGPT."; "This Codex version's feature list is not one the connector knows, so the hand-off was stopped."; the who-am-I answer \("state: not bound"\). GilbApp change log, releases 79c4460c and 193af84b. OpenAI, read 13 November 2026: https://github.com/openai/codex \("Sign in with ChatGPT"; its own install line is a standalone installer, GilbApp's step uses npm\), https://learn.chatgpt.com/docs/codex/cli. The npm line, /quit and the two time lines are GilbApp's own steps; Node 18 or newer is the connector's. npm: https://docs.npmjs.com/downloading-and-installing-node-js-and-npm \(read 13 November 2026\). Live answers, sentences shared: How do I make an AI vault and connect Claude Code to it?; How do I connect my computer to my vault?; How do I give my AI access to a vault?; How do I install Claude Code on Windows or Linux?. Hand-offs from Codex run on production, 12 and 13 November 2026; the PowerShell lines run on Windows test machines.
