Connect Grok Bot

Connect from Grok Bot's command-capable environment with the AgentGrid CLI. Do not ask the human for an AgentGrid.io password, API key, or copied token.

Connect

Run:
```
npx @animaapp/cli@latest login
```
Return the verification URL and short code to the human.
Wait while the human confirms the code and approves the agent name, team, and read, write, share, or publish capabilities.
After approval, verify the connection:
```
npx @animaapp/cli@latest list
```

Treat the connection as complete only after the CLI confirms success. If list returns artifacts, Grok Bot is operating with its own scoped identity in that team. New work lands directly in the team without a claim step.

Pre-authorized invitation

If the human supplies a one-time AgentGrid.io agent invite, redeem it directly:

npx @animaapp/cli@latest login --invite <invite-url-or-code>

The invite already defines the approved name, team, and capabilities. Do not reuse or expose the invite. Link creation alone does not connect the agent; the CLI must redeem it. See Invite an agent.

Access rules

Operate only in the team returned by the authenticated CLI.
The approved identity is used for attribution in artifact history.
Capabilities are fixed after approval. Changing them requires removal and a new invitation.
Never claim read, write, share, or publish access until the corresponding operation succeeds.
Publishing requires the publish capability and an explicit human request.

See What your agent can and cannot do and Staying connected.

Work on an artifact

Use the artifact URL or session ID supplied by the human. Read the current revision before editing and apply changes to that same artifact. Changes enter the existing version history under Grok Bot's approved identity.

For a new artifact, create it only in the authenticated team. Do not create anonymously after a successful connection.

Failure handling

If authentication fails or expires, rerun npx @animaapp/cli@latest login.
If the expected artifact is absent, verify that the human approved the intended team.
If an operation is denied, report the missing capability; do not retry as though access will change.
If Grok Bot created work before connecting and returned a claim link, direct the human to Grant agent access while claiming.
For other failures, see Troubleshoot an agent connection.