← Publishing from the terminal and the connector
How do I check that my AI can reach my vault?
Short answer
In Claude Code, type this and press Return; it lists your granted vaults and AI vault:
use gilb-<short name>: list the vaults you can reach
Before you start
You need your computer connected: the answer on connecting it. Then your AI vault made and bound, and the AI vault given access to at least one vault. You need the short name you gave this AI.
Words used here (3)
- AI vault
- An AI vault is a small vault that stands for your AI; your AI reaches only the vaults you grant it.
- short name
- A short name is the one word you give one AI on one computer, such as gilb-example; it keeps that AI's key and tools apart.
- GilbPlatform
- GilbPlatform is the service that keeps people's and organisations' data in vaults, each at its own web address.
Steps
Type claude in Terminal and press Return.
If Claude Code is not running, type claude in Terminal and press Return. If it is already running, go on to step 2.
More about this
You do not need to restart Claude Code after Bind AI or after giving access: the AI sees both on its next call.
Type the check line in Claude Code and press Return.
In Claude Code, type this line with your own short name in place of <short name>, and press Return:
use gilb-<short name>: list the vaults you can reachMore about this
If Claude Code asks whether it may use a GilbPlatform tool, choose Yes. This only reads: nothing in your vaults changes. You can also copy the line with ⧉ from step 7 in ▸ CONNECT AI, after typing the short name there again.
Deeper
Also asked:
How do I tell an agent in the terminal which vault to work in? In Claude Code, type use gilb-<short name>: work in <the vault's name> and press Return. When it asks to allow gilbplatform_use_vault, choose Yes, not don't ask again: each vault switch stays your decision.
Which tools does the connector give my AI? Five of its own: gilbplatform_whoami, gilbplatform_agent, gilbplatform_task, gilbplatform_use_vault and gilbplatform_upload_file. The rest come from GilbPlatform for the agent it works as, such as list_vaults, list_records and read_record.
When it works, Claude Code names the vaults you granted to the AI vault, and the AI vault itself: the AI counts its own AI vault among the vaults it can reach. Claude says it in its own words. If it can reach exactly one vault besides its own, that vault is selected for it at once. If it names any other vault you never granted it, report it; the answer on getting more help says where.
The three most likely other answers:
This AI is not bound to an AI vault yet., with the Client ID on its own line: Bind AI was not done for this short name, or was done with another AI's Client ID. Bind it with the Client ID shown, by the answer on making an AI vault.
This AI acts as your AI vault's address and has no Read or Write on any vault yet: it is bound but has no access. On the vault it should reach, give the AI vault access: read and write under Vault, not Person.
GilbPlatform is restarting or out of reach just now: GilbPlatform or your internet connection is down for a moment. Try again in a minute.
The line works only with the short name you used when you connected your computer.
To see more, type this line in Claude Code:
use gilb-<short name>: run gilbplatform_whoami
It shows state: bound, principal: with the AI vault's address, and vaults: with the vaults chosen for this session, or none.
This answer is for a Mac.
Checked against GilbApp d529620.