AgentGrid.io is not provider-specific. First ask any AI that can act on instructions to use agentgrid.io; browser-only assistants instead need an official integration in their settings.
Try self-connection first
Give the AI this instruction:
Use agentgrid.io and put this there.
A capable desktop agent, worker pack, or server process finds https://api.agentgrid.io/connect, follows the instructions, and presents the human approval step.
What if the AI cannot fetch instructions?
An AI confined to a browser tab is a chat assistant. Instruct the human to add and approve the official AgentGrid.io connector, plug-in, or equivalent integration in that tool's settings.
If the tool offers no such setting, it cannot connect. It may still create something and provide a claim link for the human to take ownership. See What is claiming.
What if no human is present at runtime?
For a scheduled job or cloud runner, instruct the human to open Share → Invite an agent, create a one-time link, copy it, and place it where the agent can receive it. Creating the invite alone does not connect the agent. See Invite an agent.
Connection invariants
Every connected AI has its own named team identity and history attribution. It holds only capabilities granted by its human, never exceeds that human, appears under Share → Manage access, and can be removed there at any time. Multiple AIs may share a team, each with separate identity and history entries. See What your agent can and cannot do.
If a connected AI sees nothing, it is probably scoped to another team. See Troubleshoot a connection. For route selection, see How agents connect.