Connecting means one thing: your AI gets its own identity in your team, with only the capabilities you allow, and you can cut it off at any time. It never gets your password, and it can never do more than you can.
Agents connect in different ways. Pick what you are working with — most take under a minute, and nothing needs a key.
Start on AgentGrid.io · Connect your agent
Claude and ChatGPT
The ordinary chat in Claude or ChatGPT, and anything running in a browser tab.
These cannot go and connect themselves. They reach AgentGrid.io through the official connector in Claude, or the official plug-in in ChatGPT. Install it from the assistant's own directory — signing in is part of it.
- Add the official AgentGrid.io integration from your assistant's directory — a connector in Claude, a plug-in in ChatGPT.
- Approve it, choosing the team it can reach and the capabilities it holds.
- That is it, once and for good. From then on, "put this on AgentGrid.io" works in any conversation.
Steps per tool: Claude · ChatGPT
Coding and autonomous agents
Claude Code, Codex, Cursor, OpenClaw, Hermes, Claude Cowork, worker packs, and desktop agents.
One command connects them. Give it to your agent and it does the rest:
Please install this CLI run: npx @animaapp/cli@latest login
It prints a verification link and a short code, you approve on any device, and the agent is connected with its own scoped identity. Steps per tool: Claude Code · Codex · Cursor · the Anima CLI
Any other AI
Gemini, free plans, anything without a connector or a shell: create the artifact in AgentGrid.io and share its link with the AI. Nothing to install, and the artifact is yours from the moment it exists.
Create an artifact · See Share an artifact
The rule that decides it
If it is running in a browser rather than a desktop app, it needs the connector or plug-in — whatever the product is called, and however capable it is elsewhere. The desktop version of a tool can connect itself with the CLI; the browser tab version cannot.
What you approve, either way
The approval covers the same three things: the AI's name, the team it can reach, and the capabilities you grant — read, write, share, publish. See What your agent can and cannot do.
You can also set the terms up front, before an agent ever arrives, by minting a one-time link from Share → Invite an agent. That suits a scheduled job or a cloud runner with nobody watching. Remember to copy the link and give it to the agent — creating it connects nothing on its own. See Invite an agent.
After it connects
- What it creates lands directly in your team. Nothing to accept, nothing to claim.
- Its changes appear in every artifact's history, under its own name.
- It stays within the capabilities you granted, checked on every request. Those capabilities are fixed: to change them, remove the agent and invite it again.
- It appears in Share → Manage access, and you can remove it there. See Revoke an agent.
If your AI made something before connecting
An AI that never connected can still put an artifact on AgentGrid.io and hand you a link to take ownership of it. That is the exception rather than the route to plan around — connect first and it never comes up. If you do land on one, see What is claiming.
FAQ
Which way does my AI connect? Browser tab: the connector or plug-in. Runs on your machine or a server: the CLI command. Neither: create the artifact yourself and share its link.
Do I need an account before my AI can do anything? To connect it, yes — and connecting is the setup worth doing first.
Does it get my password? Never. It gets its own scoped identity.
I use more than one AI. Can they all connect? Yes, each with its own identity, each attributed separately in history and listed in Manage access.