MyJackfruit

Help
Browse topics · Connecting my AI

Connecting my AI

← Back to I connected the wrong AI or the wrong vault. What now?

What is an AI vault?

Checked against GilbApp d529620.

An AI vault is a small vault that stands for your AI; your AI reaches only the vaults you grant it.

It holds none of your records: the only record in it is one card for the AI itself, which GilbPlatform makes when you bind it. It lets you give your AI access by a grant, the same way you give anyone access. You make it in GilbApp: open one of your vaults, open ▸ CONNECT AI and press Mint AI vault. Then paste your AI's Client ID, the fixed name GilbPlatform gives your AI when it is first registered, and press Bind AI, so that your AI, such as Claude Code or Codex, acts as that vault. Last, on each vault the AI should work in, open ▸ GRANT ACCESS, choose Vault under SHARE WITH, not Person, paste the AI vault's address, and grant it read, then write.

Example: an AI vault named AIAssistant is given read and write on a garden club's vault. Asked to list the vaults it can reach, the AI lists that vault and no others. An app's server can have an AI vault in the same way.

Deeper

Also asked:

What is an AI vault, and why does my AI need one? It is the vault your AI acts as. Your AI needs one so that you can give it access by a grant, the same way you give anyone access; it reaches only the vaults you grant it.

What does AI vault mean? A small vault that stands for your AI, such as Claude Code or Codex. It is the vault your AI acts as.

What is a Connected AI? Your own AI, such as Claude Code or Codex, connected with ▸ CONNECT AI and bound to its AI vault. It acts for you, and reaches only the vaults you give that AI vault access to.

What is the difference between my own vault and an AI vault? Your own vault holds your records, and you sign in to it. An AI vault stands for your AI: it holds only a card for the AI, and the AI reaches only the vaults you grant it.

An AI vault is made inside the vault you opened. It is refused while someone other than you can read or write that vault or a vault above it, because they could then read the AI vault too. The screen says: "If this vault is shared with others, Mint is refused: remove their Read and Write here first, mint, then grant them again."

Only you, who made it, can bind it. Once bound, your AI cannot be bound to another AI vault. No one can be given access to read or write an AI vault. Typing the AI vault's name under SHARE WITH does not find it: paste its address.

A vault cannot be turned into an AI vault later, or back: make a new one.

The box This AI may create vaults is ticked for you at the first bind: the AI can then make new vaults from Claude Code. Each one sits inside the AI vault, and you get Read, Write and Control on it. Untick it and the AI makes no new ones, but vaults it already made stay.

When you take a grant away, the AI loses that vault from its next request.

Source: GilbVeda t:Vault a:does ("A bounded store, owned by one principal, that holds that principal's records and keeps them retrievable") and t:AiAgent a:does ("a Software System THAT perceives a task assigned by a principal, decides how to carry it out, and acts on it"); the platform's definition: a vault whose a:podRepresents is t:AiAgent (GilbPlatform 988605c5 src/auth/account-vocab.ts:351, AI_AGENT_REPRESENTS_URI = https://veda.gilb.com/base/t/AiAgent); Dev.Guide.AppAccess.AiVault, .Bind, .Grant (A 06gqw6jdn9sgbc9rfbfrwc7rec); GilbApp 0c933e55 src/components/VaultAccessManager.tsx:77, :589 and records/AccessPanel.tsx:33-34 (fold headings drawn uppercase: ▸ CONNECT AI, ▸ GRANT ACCESS), :609-634 (Share with drawn uppercase, chips Person, Vault; Vault-to-vault reach. Not a person grant), :660-679 (vault grant: read or write, one at a time; Write + Read is the Person list only, :702), :384-396 (box ticked on a new bind); registry-lookup-visible.ts:244-261 (name search offers person vaults only), :918 (Client ID placeholder), :925 (Bind AI), :593, :780, :894, :906, :909-934, :940-955, :965-966, :983-996 (incl. vaults it already made stay); GilbPlatform 988605c5 src/authz/vault-nesting.ts:330-345, src/authz/vault-access-edge.ts:1026-1044, src/authz/ai-agent-vault-guard.ts:77-86, src/auth/vault-represents-decider.ts:140-153, src/auth/bind-agent-vault.ts:112-148, :142 and :158 (giveAiItsOwnCard), src/baseconnect/ai-own-card.ts:1 (A vault that represents an AI agent … holds ONE AiAgent card of its own) 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?