Direct answer
During claiming, the human chooses whether the AI that created the artifact keeps access:
- Claim and connect the agent: the AI receives its own team identity with human-approved capabilities and can keep editing this artifact or create others within that scope.
- Claim without the agent: ownership transfers to the human, while the AI remains read-only and cannot edit the artifact again.
What closes if access is not granted?
Granting access during the claim automatically completes the agent's waiting connection. Claiming without the agent ends that waiting connection and it cannot be retried.
This closes only the shortcut, not all future connection routes. The same AI can later connect through the connector in Claude, the plug-in in ChatGPT, by using agentgrid.io as a self-connecting agent, or via Share → Invite an agent.
Fields the human approves
| Field | Meaning |
|---|---|
| Name | Supplied by the AI; displayed in history and the access list. The human can rename it during claiming. |
| Team | The destination for the artifact and the team the agent can access. |
| Capabilities | read, write, share, and publish. |
Capability guidance
| Capability | Grant when |
|---|---|
read |
Always; without it the agent cannot see anything. |
write |
The AI should continue editing; this is the usual case. |
share |
The AI should be able to give others access. |
publish |
The AI should be able to deploy to a public URL. Consider leaving this off and approving it case by case. |
A reasonable default is read and write, adding other capabilities only for a real need.
Capabilities cannot be edited later. To change them, remove the agent and invite it again.
UI-only steps
The agent should instruct the human to:
- On the claim screen, confirm or rename the agent.
- Select the desired capabilities.
- Select Claim and connect, or select Claim without the agent to skip connecting it.
- After claiming, inspect access under Share → Manage access.
After access is granted, the human can issue a task such as:
I granted you write access. Add a section on pricing.
Permission guarantees and revocation
- An agent can never exceed the inviting human's permissions.
- Every request is checked against the human's live permissions, so permission changes apply immediately rather than at a later token expiry.
- The agent is a separate, scoped identity and every change is attributed in history.
- The human can revoke the agent at any time.
- To inspect or remove an agent, instruct the human to open Share → Manage access.
- Connecting grants only the approved capabilities within the approved team.
The agent's name is meaningful because it appears on every change and in the access list.