Skip to content

Ship the agentmail-agentid skill and release 0.4.0 - #15

Merged
sidharth0612 merged 7 commits into
mainfrom
sid/agentid-provider-accounts
Sep 29, 2026
Merged

sidharth0612 merged 7 commits into
mainfrom
sid/agentid-provider-accounts

Conversation

@sidharth0612

@sidharth0612 sidharth0612 commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Summary

This makes AgentID (provider connect and accounts) available in the Cursor, Claude Code, and Codex plugins.

  • Skills: exported from Add the agentmail-agentid skill for providers and accounts agentmail-skills#17 with skills.py build --target .:
    • new skills/agentid/ (canonical agentmail-agentid, exported under the short ID agentid like send-email, so it's /agentmail:agentid and $agentid), with an MCP dependency in agents/openai.yaml
    • agentmail-mcp now covers Claude.ai / ChatGPT connector setup and the tool groups
    • check-email now uses get_message
    • the threat model gains a "Connect inbox to provider" row
  • README: a new "AgentID: create accounts for your agent" section. It leads with what people ask for ("Create an account at Firecrawl for my agent", "My agent needs a web search API", "Log my agent back in to Turso"), explains what the skill carries through to (usually an API key in a secret store), and then gives the tool table and per-client invocation. It notes that unlisted providers work by ID (agentmail-to/agentmail-api#1408) and adds a safety-model bullet for provider sign-ins.
  • Manifests: all four go to 0.4.0. Every manifest and the marketplace entry now use one description: "Email inboxes for agents. Create inboxes, send and receive emails, automate email workflows, and create accounts with AgentID." Keywords include agentid, the Codex longDescription explains AgentID, and one Codex defaultPrompt is now "Create an account at Firecrawl for my agent with AgentID."
  • validate_repo.py: agentid is added to the skills that must declare the hosted MCP dependency.
  • CHANGELOG: new 0.4.0 entry, which absorbs the Unreleased notes. I dropped the "blocked on publish" sentence, since the pins already moved to toolkit 0.5.1.

Not changed: the compatibility.json pins. check_compatibility.py reports drift that was already there before this PR: TS SDK 0.5.31, Python SDK 2.0.5, CLI 1.7.0, toolkit TS 0.9.0. Moving those pins means re-verifying the SDK signature tests, which belongs in its own PR.

Test plan

  • python3 scripts/validate_repo.py: passed (4 manifests, 9 skills)
  • claude plugin validate . --strict and .claude-plugin/plugin.json --strict: passed
  • skills.py build --check --target . against the skills branch: clean
  • After merge, reinstall in Codex, Claude Code, and Cursor, and run list_providers as a read-only check

Merge order

  1. Frame provider tools around creating accounts; unlisted providers by ID; show the sign-up cap agentmail-toolkit#66, then publish agentmail-toolkit 0.9.1 to npm
  2. Send server instructions that introduce AgentID providers and accounts agentmail-mcp#62 after it gains the 0.9.1 pin bump and a regenerated mcp-manifest.json, then confirm the connector deploy
  3. Add the agentmail-agentid skill for providers and accounts agentmail-skills#17, re-synced with skills.py sync --backend against the regenerated manifest
  4. Ship the agentmail-agentid skill and release 0.4.0 #15, re-exported from Re-export the skills with app_connect and release 0.5.1 #17 if Re-export the skills with app_connect and release 0.5.1 #17 changed
  5. docs(agentid): use AgentID from Claude, ChatGPT, and Cursor agentmail-docs#279, then run Publish docs

Skills, plugins, and docs wait for the connector so they don't describe ownerSignupLimit and unlisted-by-ID behavior that the live 0.9.0 tool descriptions contradict.

🤖 Generated with Claude Code

sidharth0612 and others added 3 commits September 29, 2026 12:02
Export the new AgentID skill from agentmail-skills (#17) so Codex, Claude
Code, and Cursor agents know how to find providers, sign an inbox in with
connect_provider, and list provider accounts. The README gains an AgentID
section with example prompts and per-client invocation, and every
manifest now mentions AgentID so it shows up in marketplace listings.

The version bump is what makes installed Claude Code and Codex plugins
pick up the new skill.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sidharth0612 and others added 2 commits September 29, 2026 12:14
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Re-export agentmail-agentid, which is now organized around requests
like "create an account at Firecrawl". The README AgentID section,
the Codex long description and default prompt, and the changelog
describe the product the same way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@shalim786 shalim786 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The skill copies inherit the inline notes on agentmail-skills#17 (cap counting, 404 meaning); re-export after those land. Merge after the connector is on toolkit 0.9.1 (see #17).

Comment thread README.md Outdated
- "Log my agent back in to Turso."
- "Which services is support-bot@agentmail.to signed up for?"

The `agentmail-agentid` skill carries the whole job. It finds the provider, picks the inbox that will own the account (creating one if needed), and checks for an existing account and the provider's sign-up cap. Then it hands you a single-use sign-in link and confirms the account exists. Finally it helps you get what you came for, usually an API key stored in your secret store. Invoke it explicitly with `$agentmail-agentid` in Codex or `/agentmail:agentmail-agentid` in Claude Code; in Cursor, just ask.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Naming nit, and cheap only before 0.4.0 ships: this becomes /agentmail:agentmail-agentid. skills.json pluginExport.legacyIds already maps agentmail-* action skills to short IDs (send-email, …). Adding "agentmail-agentid": "agentid" would give /agentmail:agentid and $agentid, consistent with the others. Renaming after release breaks installs.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. skills.json in agentmail-skills#17 now maps "agentmail-agentid": "agentid" in legacyIds (863fa6f). This PR re-exports it as skills/agentid/, so it's /agentmail:agentid and $agentid (6b51153). The README, changelog, and validate_repo.py MCP-dependency set use agentid, and so does the docs guide in agentmail-docs#279. It stays agentmail-agentid on skills.sh.

Re-export from agentmail-skills#17: the skill now exports under the
short ID agentid (/agentmail:agentid, $agentid), matching send-email,
check-email, and manage-inboxes, and picks up the review fixes on the
sign-up cap, 404 meanings, and error codes. README, changelog, and the
MCP-dependency check use the new ID.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sidharth0612

Copy link
Copy Markdown
Contributor Author

@shalim786 Re-exported after the skills#17 fixes (6b51153), with the agentid short ID applied. The merge order is in the description: this goes after the connector is on 0.9.1 and after skills#17, and gets re-exported again if #17 changes.

@shalim786 shalim786 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rename to agentid and the re-exported fixes look good (6b51153). LGTM. Merge order still applies: publish agentmail-toolkit 0.9.1 from #66, bump the connector's pin to it, regenerate mcp-manifest.json and deploy; then merge skills#17, plugins#15 and docs#279.

@sidharth0612
sidharth0612 merged commit 8b346ec into main Sep 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants