Guilduo Agents: registration, linking and Handoff

Register a role and permissions

1. Sign in at https://app.guilduo.com/ and open Agent registration in Party.
2. Set the display name, provider, role and instructions. For example: name Implementation helper; instruction Read the target before editing and return verification results for review.
3. Choose the required allowedScopes. Use quests:read for Quest access and consider quests:write for delegated updates.
4. After saving, verify the registered Agent ID and active status. Do not register model API keys or execution URLs.

Link an MCP connection to the registered Agent

Public tools also include get_agent_link, link_agent and unlink_agent. link_agent requires the OAuth agents:write scope; it does not register an Agent or expand its policy.

1. Complete MCP OAuth using the same account and the connection guide.
2. Link the intended client to the Agent in Connections.
3. Use get_current_agent_context to check the Agent ID and effectiveExecutionScopes. Execution permissions are the intersection of OAuth and Agent policies.

Preview and save a Quest assignment

Read the actual Agent ID with list_registered_agents and the assignee and updatedAt with get_quest. The JSON below previews assign_quest_to_agent. Replace placeholders with values you read.

1. Check the Quest, Agent and resulting Handoff in the preview. Use ready only when the work is ready for the Agent.
2. Within authorized scope, add the current expectedUpdatedAt to the same input and set dryRun to false to save.
3. Reread with get_quest to verify the saved assignee and Handoff.

{
  "questId": "REPLACE_WITH_QUEST_ID",
  "agentId": "replace-with-agent-id",
  "handoffState": "ready",
  "note": "Improve one help message and return a review summary.",
  "dryRun": true
}

Move through Handoff and return results

Preview transitions with transition_quest_handoff and pass the current state as expectedState when saving. Do not overwrite using stale state.

ready does not prove delivery or Agent startup. Actual work happens in the connected Codex, Claude or other environment.

Diagnose Agent issues

• Agent missing from the list: check the account, registration and active status. A legacy free-form assignee is not a registered Agent.
• Assignment conflict: reread the Quest, refresh updatedAt and preview again.
• Reads work but writes fail: check that both OAuth and the Agent include the required write scope.
• Wrong linked identity: verify the intended Agent ID, relink within authorization and reread context.