How agent access works
An agent badge decides which team's memory an external agent can use. The Agent connections page turns that badge into setup instructions for each supported client.
Connect a client
Supported clients include Claude Code, Codex, Cursor, VS Code, Cline, Gemini CLI, and ChatGPT.
- Open Agent connections.
- Choose the client you want to connect.
- Create a new assistant key on the page, or use the badge key you saved during setup.
- Follow the exact steps shown on that client's card. Use the copy buttons to avoid transcription mistakes.
- Complete the client's own verification step when one is provided.
- Return to Agent connections and check Connected agents.
Confirm the agent is active
An agent is shown as active when its badge has been used recently. This is an honest last-activity signal, not a permanent online/offline connection.
If the agent has not used the key within the recent activity window, it will no longer appear active. Ask the agent to make a Halofy call, then refresh the page.
Manage access later
Use Scoped memory to inspect, rotate, or revoke badges. Revocation takes effect immediately.
Grant direct access to raw backend records only when the agent genuinely needs it. Ordinary agents should usually work from governed memory.