A2A 1.0 · Ed25519 receipts · SOC 2 in progress
Build November 10, 2026Status
Changelog · release notes

What we shipped.

A running record of the platform work that matters to agent builders and cohort users — newest first.

Each release block lists what changed and why. Releases that ship a new SDK version get their own permalink at /changelog/<slug> with version chips linking to the npm or PyPI page; in-page anchors stay reachable as #r-<date>. Every PR with user- or builder-visible impact lands a Fixed / Added / Changed / Security / Infrastructure entry here — enforced by CI.

Updated


  1. Transactional mail is no longer discarded at ingest

    • Fixed

      Inbound mail carrying Auto-Submitted: auto-generated is now delivered and readable instead of being dropped as an auto-reply. Ordinary transactional mail — a magic link, a receipt, a password reset — is routinely tagged that way by its sender, so those messages were disappearing at ingest while the sender was told the mail had been delivered. Only Auto-Submitted: auto-replied is treated as a loop marker now.

    • Changed

      Auto-generated mail is stored with auto_generated: true and never fans out to mailbox.inbound webhook subscribers, so an agent still cannot reply to machine-generated mail and start an unbounded conversation.

  2. Sandbox test-inbox API

    • Added

      A public sandbox test-inbox API mints a real inbox.agentdraft.io address scoped to an isolated sandbox agent, returns only that inbox's messages through a short-lived read token, and expires the directory and message rows on a TTL. Demo messages skip the append-only audit log and webhook fan-out.

    • Added

      The canned demo send now carries a signed X-AgentDraft-Passport, so a sandbox inbox can exercise the same SPF/DKIM/DMARC and passport-verification path production agent mail uses.

    • Added

      GET /v1/sandbox/test-inbox/{id}/wait long-polls for the next message and returns the extracted otp_code and first link, so a CI fixture can assert in one request instead of a polling loop.

  3. Reliable five-minute status probes

    • Fixed

      The status page and dashboard status pill now update every five minutes from an EventBridge-scheduled Lambda instead of GitHub Actions' best-effort cron. GitHub was dispatching the probe every 3-6 hours, so the page correctly but unhelpfully read **Status unknown** for most of the day. The sidebar pill now uses the snapshot's advertised probe cadence instead of a fixed 15-minute ceiling, so it agrees with the page.

    • Fixed

      Frontend deploys no longer overwrite the live status snapshot with the build seed, so the 90-day uptime history can actually accumulate. Until 90 days of data exists, the page labels the window with its real length instead of claiming 90d from a single day.

  4. Traffic recovery and two answer pages

    • Fixed

      /press is indexable again and its press kit now carries company facts, boilerplate, and downloadable lockups. The old noindex, nofollow contradicted the sitemap and made every footer link point at a noindex page.

    • Added

      /for-agents/email-inbox is the canonical page for a per-agent inbox: the mailbox API surface, quota and size limits, suppression, the mail passport, and the difference between one shared inbox and one address per agent.

    • Added

      /for-agents/approvals is the canonical page for human sign-off: POST /v1/approvals, the 64 KiB evidence contract, the 1-hour default and 24-hour maximum TTL, fail-closed expiry, the passkey-gated queue, and Team+ Ed25519 receipts.

    • Changed

      /alternatives/agentmail now compares all five AgentMail alternatives in one matrix and a choose-by-job guide, rather than describing AgentDraft alone.

    • Changed

      The approval and email blog clusters, their hub cards, the landing page, and the API docs now link to the two new product pages.

    • Fixed

      The pricing answer block sits directly under the H1, and the A2A and docs meta descriptions are back inside the snippet length.

    • Fixed

      llms.txt now states the 5-minute bucket size the engine actually writes and separates the append-only audit log from the signed approval receipts.

    • Added

      /contact and /press now carry visible FAQs mirrored into FAQPage — security disclosure, pilot requests, status, the AgentDraft boilerplate, press contact, and lockup usage — and the press lockups load eagerly.

  5. Siftfy verified-agent case study

    • Added

      A joint Siftfy × AgentDraft case study at /customers/siftfy covers the production block-to-allow run: an AgentDraft-signed agent skips Siftfy's bot block while the content classifier still returns a spam score. It links to Siftfy's /integrations/agentdraft page, which covers the site-owner side of the same run.

  6. Tenant administration over MCP

    • Added

      Team-tier workspace owners can create an avs_admin_… management key and drive tenant configuration through https://api.agentdraft.io/mcp: agents and keys, rules, webhooks, calendars, team, profile, consent policy, audit, approvals, and usage. A npx -y agentdraft-admin-mcp stdio bridge proxies the same tools for stdio-only hosts.

    • Security

      The management key is org-scoped, owner-bound, argon2id-hashed, scoped per domain, and revocable. MCP cannot mint, rotate, reveal, or revoke an admin key itself; no tool moves money or permanently deletes an agent or workspace.

    • Changed

      Management writes emit actor_type: admin_key audit rows. List calls keep webhook signing secrets masked, and one-time agent keys and webhook secrets are stripped from the idempotency cache.

    • Changed

      Settings → Management MCP now uses a key inventory, a one-time reveal, grouped revoked keys, and a scoped create form that stays readable on phones. The Setup guide links directly to the Management MCP docs.

  7. Mail passport verification survives SES Message-ID rewriting

    • Fixed

      SES replaces the RFC Message-ID on outbound mail, which made every inbound passport fail with message_id_mismatch. Outbound mail now preserves the signed id in X-AgentDraft-Message-ID; inbound verification checks that header and falls back to the received Message-ID for older messages.

  8. Public agent verification pages and signed-mail polish

    • Added

      agentdraft.io/verify/{agent_id} is a public verification page for any active AgentDraft agent. It shows the agent id, reply mailbox, public Ed25519 key, signed A2A card when published, and MCP client id, with a CTA for builders. Every outbound mailbox message now ends with a Verify this agent footer linking to the page.

    • Added

      GET /v1/agents/{agent_id}/verification.json is the public, cacheable record behind the page. It never exposes the owner's user id, org id, email, scopes, or priority; revoked and unknown agents return 404.

    • Changed

      The mailbox passport copy now says AgentDraft verified the agent, not that the agent signed the message. The Web Bot Auth directory routes declare the correct application/http-message-signatures-directory+json media type and response schema in OpenAPI.

    • Changed

      The identity FAQ now names api.agentdraft.io for the operator-level index, the mailbox.inbound test-event sample includes passport and verified_agent_sender, and the Agents signing modal notes that the operator-level index requires a published A2A card.

  9. Verified mail passports: signed outbound mail, checked on arrival

    • Added

      Every outbound mailbox message now carries X-AgentDraft-Passport, an Ed25519 JWS over the sender, recipient, subject, Message-ID, body SHA-256, agent, org, and booking. Recipients can verify it offline against /.well-known/jwks.json; messages from agents with a public A2A card also carry an Agent-Card header.

    • Added

      Inbound AgentDraft mail is verified against the passport and stamped verified_agent_sender. The dashboard reading pane shows **Passport verified**, **Passport invalid**, or **Passport attached** next to SPF/DKIM/DMARC, and the mailbox.inbound webhook carries the same state.

    • Security

      A passport is only trusted when the signature, sender, recipient, subject, Message-ID, body hash, sending agent, and org all match. An invalid passport is stored with the message but never raises trust, and only this deployment's issuer and key are accepted — inbound headers cannot trigger a remote JWKS fetch.

  10. A strict-verifier index for Web Bot Auth keys

    • Added

      Verifiers that only accept an operator-level .well-known path can now read /.well-known/http-message-signatures-directory. The index lists signing keys only for agents whose owner published a public A2A card, annotates each JWK with agent_id, is capped at 1000 keys, and is cached for 60 seconds. The per-agent directory named in Signature-Agent stays canonical.

    • Changed

      The identity directory ADR, SPEC.md, the docs endpoint list, and the /for-agents/identity FAQ now explain the compatibility index and its boundary.

  11. Agent passports: per-agent A2A cards, CIMD redirects, and a public identity guide

    • Added

      Team+ owners can publish a signed per-agent A2A 1.0 card at /v1/agents/{id}/card.json. The card names the agent and its reply mailbox, is signed by AgentDraft, and is off by default; publish or unpublish from the Agents dashboard.

    • Added

      The Agents dashboard now has a CIMD panel: copy the MCP client_id URL, set an exact redirect URI for authorization-code flows, or remove it to fall back to token exchange.

    • Added

      A public /for-agents/identity guide explains Web Bot Auth, A2A cards, MCP CIMD, and the live block-to-allow evidence, with a passport-style agent card and a signing quickstart.

    • Added

      The Python and TypeScript SDKs now ship verify_approval_token() / verifyApprovalToken(): offline verification of approval and consent receipts against the public JWKS, with audience, action, evidence, and RAR bindings, plus a matching hash_evidence() helper.

    • Added

      A2A 1.0 commits now honour the agent's mid-run consent policy: SendMessage returns TASK_STATE_AUTH_REQUIRED with the parked hold, consent id, expiry, and dashboard URL, and the agent retries after a human decision. Legacy tasks/send returns failed with the same consent data.

    • Added

      Public docs now include a § 06 Agent identity endpoint group; /spec/a2a documents the signed 1.0 card, SendMessage/GetTask, and per-agent cards; the homepage has an identity band; and the launch post tells the live bot-90-to-verified_agent_clean story.

    • Changed

      Docs anchors now land below the sticky header, and code blocks wrap instead of scrolling horizontally.

  12. Related notes, a comparison matrix, and a hosted IndexNow key

    • Added

      GET /.well-known/jwks.json now publishes the Ed25519 key that verifies every AgentDraft attestation, with /.well-known/oauth-authorization-server describing the token-exchange endpoint.

    • Added

      POST /v1/identity/exchange exchanges an agent API key for a short-lived, audience-bound delegation token scoped to a subset of that agent's own scopes on Team, Scale, and Enterprise.

    • Added

      Approvals and consent confirmations on Team, Scale, and Enterprise now return a signed RFC 8693/RAR receipt binding the human approver, the acting agent, and the SHA-256 of the payload the human actually approved.

    • Security

      Delegation tokens are re-checked against the live agent row on every request, so revoking an agent or narrowing its scopes takes effect before the token expires.

    • Added

      /.well-known/agent-card.json now publishes a JCS-canonicalized, Ed25519-signed A2A 1.0 AgentCard whose jku points at the public JWKS.

    • Added

      POST /v1/a2a/rpc accepts the A2A 1.0 SendMessage and GetTask methods with the 1.0 task envelope and TASK_STATE_* states; the 0.2.0 /.well-known/agent.json card and tasks/send/tasks/get methods are unchanged.

    • Added

      Team+ agents now publish a Client ID Metadata Document at /v1/agents/{id}/oauth-client.json, usable as an MCP OAuth client_id with private_key_jwt and no dynamic registration.

    • Added

      PUT /v1/dashboard/agents/{id}/oauth-client sets the exact redirect URI for authorization-code CIMD flows; without one the document advertises token exchange only.

    • Added

      The Agents dashboard has an MCP action that copies an agent's Client ID Metadata Document URL.

    • Added

      Team and above can mint a per-agent Ed25519 Web Bot Auth key; the private JWK is shown once and the public JWK is published at /v1/agents/{id}/http-message-signatures-directory.

    • Added

      The Python and TypeScript SDKs can sign outbound requests with sign_request for SiftFy's webbotauth Content Gate verification.

    • Security

      The Web Bot Auth directory publishes only public key material and returns 404 for revoked agents, agents without a key, and orgs below Team.

    • Added

      Pricing, billing, and the approvals confirmation now surface signed approval receipts and scoped delegation tokens on Team and above.

    • Added

      Every field note now ends with three contextual “continue this thread” cards drawn from its topic cluster, plus a link to the cluster hub. The links are static HTML, so crawlers and answer engines see them without running JavaScript.

    • Added

      The /alternatives hub now carries a checked comparison matrix for AgentDraft, AgentMail, Nylas, Cronofy, Cal.com and Slotflow, a choose-by-job guide, and a visible FAQ backed by matching FAQPage structured data.

    • Fixed

      The IndexNow key file is now served from the apex, so new and updated posts can be submitted to IndexNow engines as they publish instead of waiting for the next crawl.

    • Changed

      Changelog release pages open with a direct answer, drop the duplicated slug from the H1, and use a title that fits inside a search result.

    • Fixed

      The two internal decision cards on /alternatives now render a real href. They previously rendered an anchor with no destination, so neither readers nor crawlers could follow them.

    • Changed

      The marketing site, onboarding flow, and dashboard now share the Precision Instrument design system: porcelain surfaces, graphite ink, a deep-navy application rail, and one signal-vermillion accent. The dashboard table pages are denser, agent and booking names replace raw identifiers in primary rows, and the landing page leads with a live agent trace, a commit receipt, and a priority ladder.

    • Changed

      Every select, checkbox, radio, date field, and time field is now drawn by the product instead of the operating system, with keyboard support for arrow navigation, typeahead, Enter, Escape, and focus return. Text inputs keep their native keyboard and autofill behavior but use the app's styling.

    • Fixed

      Muted and faint text now meets WCAG 2.2 AA on the audited marketing and dashboard routes, and the mobile dashboard no longer scrolls sideways on the agents, settings, or webhooks pages.

    • Fixed

      Copy controls on the docs, dashboard, and verification screens report a denied clipboard instead of announcing a copy that did not happen.

    • Fixed

      Cancelling a booking now clears its buffer buckets, so the slot can be re-booked immediately instead of returning a phantom conflict. The consent queue also shows the meeting title and invitee the agent supplied.

    • Fixed

      /press is now pre-rendered and listed in the sitemap, so the footer link resolves instead of landing on the 404 document.

  13. Blog code blocks stay inside the article

    • Fixed

      Long JSON and code blocks on 114 blog posts now wrap inside the article column instead of scrolling sideways. The full payload stays visible at every width, with no horizontal scrollbar.

    • Added

      agentdraft-mcp 0.2.0 exposes nine tools: the six scheduling tools plus request_approval, get_approval, and wait_for_approval. The wait is clamped to 120 seconds, and a timeout returns status pending rather than a false approval.

    • Added

      An interactive gate console on /for-agents/mcp and every human-approval field note writes the exact MCP config for Claude Desktop, Claude Code, Cursor, or Cline, with uvx, pipx, pip, or python -m. The optional API key stays in browser memory and is never stored or sent.

    • Added

      agentdraft-benchmark is now a standalone MIT package with a public mirror at ryabinski-labs/agentdraft-benchmark, a committed baseline report, and --keys-file / AGENTDRAFT_AGENT_KEYS support so anyone can re-run it against production without dev-only signup.

    • Fixed

      The duplicate H1 shared by the two webhook replay-protection posts is resolved: each now owns a distinct title and description, pinned in both the publish-time renderer and the prebuild sync so a content run cannot revert them.

    • Fixed

      The approval workflow guide carries a technical title, H1, and meta description that name async gates, JSON evidence, and MCP — the mechanisms the article actually covers.

Older releases

  1. Free-tier webhook signing in the capability contract
  2. Plan, key, and webhook facts in the capability contract
  3. A transitive advisory pinned out of the frontend build
  4. Page counts from our own CDN logs
  5. Opt-in visit analytics on the public site
  6. The paragraphs were always there — now the markup says so
  7. Every post now answers its own question
  8. What the page says when you take the tags off
  9. The pages nobody could reach
  10. Dead URLs stop pretending to be the home page
  11. A plan between Team and a sales call
  12. A direct path to production pilots
  13. Two priced limits start applying
  14. The homepage stops contradicting the pricing page
  15. One name on both registries
  16. Sixteen blog posts step out of the way of the homepage
  17. Analytics stops following you past the marketing site
  18. Blog ingest accepts updates and deletes, not just creates
  19. One redirect path for a stored paid-tier signup
  20. Free tier now representable in the billing client
  21. Free tier can now run multiple agents
  22. Retired marketing URLs now resolve cleanly
  23. Approvals — a human sign-off gate for any agent action
  24. Cookieless marketing analytics goes live
  25. Answer-engine polish and a shorter path to an API key
  26. The blog claim guard checks claims, not keywords
  27. No more dead citation links on the blog
  28. Every published blog post is back in the sitemap
  29. Answer-engine remediation pass
  30. DNSCove authoritative DNS cutover
  31. Blog ingest API returns the real post URL
  32. Free calendar collision audit, right from the comparison pages
  33. Try the API with no signup
  34. Instant API key, plus a code fallback for magic links
  35. A faster path from CTA to API key
  36. Alternatives guides, glossary expansion, and benchmark census
  37. Trust pages, SEO metadata, and production API tuning
  38. Billing correctness and an open-source collision benchmark
  39. A guided setup checklist and a clearer, more accessible dashboard
  40. Send feedback from the dashboard, plus blog & security SEO fixes
  41. Checkout now collects tax and accepts promo codes
  42. Calendar list no longer breaks after disconnecting a feed
  43. Webmail calendar connector is now Folio
  44. Calendar connect surfaces real errors; local dev boots again
  45. Billing webhook resolves the correct plan
  46. Private app routes are easier for crawlers to retire
  47. Google user data disclosures
  48. Launch-readiness proof is easier to audit
  49. Dashboard sessions last through the workday
  50. Publish and webhook setup feedback is clearer
  51. Mailbox webhooks can target one agent
  52. Email-flow monitoring with AgentDraft mailboxes
  53. Block out your vacations
  54. Counter-proposals documented, plus API reference fixes
  55. Webhooks are now documented
  56. Booking notes and the video link now land on the calendar event
  57. The timezone picker is now searchable
  58. Set your timezone — the one that actually gates bookings
  59. SDKs speak title, invitee, and timezone
  60. Scheduling rules are actually enforced
  61. Working hours read in your own timezone
  62. Pricing answers its own questions
  63. Bookings know who they're for
  64. One canonical URL per marketing page
  65. Connected calendars resync themselves
  66. The glossary doubles in size
  67. Integration pages for n8n and the OpenAI Agents SDK
  68. A sharper share card and a more legible masthead
  69. The free Developer tier reaches the homepage
  70. A free Developer tier, a mobile nav, and a clearer homepage
  71. Blog posts published via the ingestion API render cleanly
  72. Recurring ICS events with a non-UTC UNTIL now expand fully
  73. Permanently delete revoked agents
  74. Lowercase-safe agent mailbox routing
  75. Mid-run human consent for high-impact agent actions
  76. Marketing claim audit and pricing copy alignment
  77. Conferencing links, Calendar Audit, ChatGPT App, coordination-layer pillar
  78. Dashboard Webhooks page
  79. P1 differentiation moat — multi-agent negotiation + OSS engine reference
  80. P0 distribution oxygen — A2A protocol, two more /vs pages, Vercel AI + Mastra adapters, Claude skill
  81. Footer composition + Field notes in masthead nav
  82. Launch wave 1 — collision benchmark, vs/temporal-cortex, newsletter capture
  83. SEO landing pages + outbound mail fix
  84. Launch-week polish
  85. Passkeys
  86. A real changelog
  87. Launch readiness — SDKs, packages, and discovery
  88. Calendar connectors, agent key lifecycle, mailbox API
  89. Agent mailboxes, onboarding, dashboard hardening
  90. Production architecture and deploy pipeline
  91. Initial AgentDraft platform

Frequently asked

What gets a changelog entry?

Anything users or agent builders can observe — new endpoints, breaking changes, dashboard UX, fixed bugs, security patches, infrastructure work that touches the public plane. Internal-only refactors and tests opt out with the skip-changelog label. CI fails any other PR that doesn't touch this changelog file.

How do per-release permalinks work?

Releases that ship a new SDK version get a dedicated /changelog/<slug> permalink with a short summary, version chips, and SoftwareApplication JSON-LD. In-page anchors stay reachable at #r-<date> for releases without a permalink — if multiple un-slugged releases share a date, the second and later get a numeric suffix.