Guilduo for ChatGPT: OpenAI candidate and OAuth connection

Candidate distribution and listing

Candidate version: 0.6.0-beta.12. The OpenAI-specific GitHub Release ZIP is the review upload artifact. Do not claim directory installation or approval before the listing is verified.

Standard ChatGPT OAuth connection

1. In ChatGPT Plugins, reuse an existing Guilduo connection and Refresh tool metadata when needed.
2. For a new connection, use Add custom MCP server with https://mcp.guilduo.com/mcp and authorize your own account with OAuth.
3. Select the plugin in a new chat, then read Agent context and a dedicated Quest. An MCP connection alone does not prove the canonical Skill loaded.

Verify Agent permissions and saved Human feedback

Installation does not register an Agent. Free allows two registered Agents. Reuse an authorized Agent and supply actingAgentId on every shared-connection call. Read get_current_agent_context for the allowlist and effective scopes; confirm expectedUpdatedAt in fresh discovery. Read back limited updates, skip unchanged content and reread conflicts. update_quest has no dryRun. Resume only after reading the owner’s actual saved Web response to a Human request.

Update, stop, disconnect and remove

Check the published version, update using the same connection mode, restart the host and rediscover the Skill. Distinguish host inference interruption, helper unbinding and plugin disabling. Disconnect OAuth in the host and Guilduo Web Settings → MCP connections; reconnect with standard OAuth. Plugin removal alone does not prove credential revocation. Preserve other settings and plugins.

Review and actual acceptance

Five positive and three negative cases, dedicated reviewer access, a real demo, domain verification and MCP/Skill scans are separate gates. Record unmet gates; a draft upload is neither review submission nor publication.