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
Transactional mail is no longer discarded at ingest
- Fixed
Inbound mail carrying
Auto-Submitted: auto-generatedis 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. OnlyAuto-Submitted: auto-repliedis treated as a loop marker now. - Changed
Auto-generated mail is stored with
auto_generated: trueand never fans out tomailbox.inboundwebhook subscribers, so an agent still cannot reply to machine-generated mail and start an unbounded conversation.
- Fixed
Sandbox test-inbox API
- Added
A public sandbox test-inbox API mints a real
inbox.agentdraft.ioaddress 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}/waitlong-polls for the next message and returns the extractedotp_codeand firstlink, so a CI fixture can assert in one request instead of a polling loop.
- Added
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
90dfrom a single day.
- Fixed
Traffic recovery and two answer pages
- Fixed
/pressis indexable again and its press kit now carries company facts, boilerplate, and downloadable lockups. The oldnoindex, nofollowcontradicted the sitemap and made every footer link point at a noindex page. - Added
/for-agents/email-inboxis 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/approvalsis 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/agentmailnow 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.txtnow states the 5-minute bucket size the engine actually writes and separates the append-only audit log from the signed approval receipts. - Added
/contactand/pressnow carry visible FAQs mirrored intoFAQPage— security disclosure, pilot requests, status, the AgentDraft boilerplate, press contact, and lockup usage — and the press lockups load eagerly.
- Fixed
Siftfy verified-agent case study
- Added
A joint Siftfy × AgentDraft case study at
/customers/siftfycovers 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/agentdraftpage, which covers the site-owner side of the same run.
- Added
Tenant administration over MCP
- Added
Team-tier workspace owners can create an
avs_admin_…management key and drive tenant configuration throughhttps://api.agentdraft.io/mcp: agents and keys, rules, webhooks, calendars, team, profile, consent policy, audit, approvals, and usage. Anpx -y agentdraft-admin-mcpstdio 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_keyaudit 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.
- Added
Mail passport verification survives SES Message-ID rewriting
- Fixed
SES replaces the RFC
Message-IDon outbound mail, which made every inbound passport fail withmessage_id_mismatch. Outbound mail now preserves the signed id inX-AgentDraft-Message-ID; inbound verification checks that header and falls back to the receivedMessage-IDfor older messages.
- Fixed
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 aVerify this agentfooter linking to the page. - Added
GET /v1/agents/{agent_id}/verification.jsonis 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+jsonmedia type and response schema in OpenAPI. - Changed
The identity FAQ now names
api.agentdraft.iofor the operator-level index, themailbox.inboundtest-event sample includespassportandverified_agent_sender, and the Agents signing modal notes that the operator-level index requires a published A2A card.
- Added
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 anAgent-Cardheader. - 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 themailbox.inboundwebhook 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.
- Added
A strict-verifier index for Web Bot Auth keys
- Added
Verifiers that only accept an operator-level
.well-knownpath 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 withagent_id, is capped at 1000 keys, and is cached for 60 seconds. The per-agent directory named inSignature-Agentstays canonical. - Changed
The identity directory ADR,
SPEC.md, the docs endpoint list, and the/for-agents/identityFAQ now explain the compatibility index and its boundary.
- Added
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_idURL, set an exact redirect URI for authorization-code flows, or remove it to fall back to token exchange. - Added
A public
/for-agents/identityguide 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 matchinghash_evidence()helper. - Added
A2A 1.0 commits now honour the agent's mid-run consent policy:
SendMessagereturnsTASK_STATE_AUTH_REQUIREDwith the parked hold, consent id, expiry, and dashboard URL, and the agent retries after a human decision. Legacytasks/sendreturnsfailedwith the same consent data. - Added
Public docs now include a § 06 Agent identity endpoint group;
/spec/a2adocuments 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.
- Added
Related notes, a comparison matrix, and a hosted IndexNow key
- Added
GET /.well-known/jwks.jsonnow publishes the Ed25519 key that verifies every AgentDraft attestation, with/.well-known/oauth-authorization-serverdescribing the token-exchange endpoint. - Added
POST /v1/identity/exchangeexchanges 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.jsonnow publishes a JCS-canonicalized, Ed25519-signed A2A 1.0 AgentCard whosejkupoints at the public JWKS. - Added
POST /v1/a2a/rpcaccepts the A2A 1.0SendMessageandGetTaskmethods with the 1.0 task envelope andTASK_STATE_*states; the 0.2.0/.well-known/agent.jsoncard andtasks/send/tasks/getmethods are unchanged. - Added
Team+ agents now publish a Client ID Metadata Document at
/v1/agents/{id}/oauth-client.json, usable as an MCP OAuthclient_idwithprivate_key_jwtand no dynamic registration. - Added
PUT /v1/dashboard/agents/{id}/oauth-clientsets 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_requestfor 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
/alternativeshub 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
/alternativesnow render a realhref. 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
/pressis now pre-rendered and listed in the sitemap, so the footer link resolves instead of landing on the 404 document.
- Added
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.
- Fixed
- Added
agentdraft-mcp0.2.0 exposes nine tools: the six scheduling tools plusrequest_approval,get_approval, andwait_for_approval. The wait is clamped to 120 seconds, and a timeout returns statuspendingrather than a false approval. - Added
An interactive gate console on
/for-agents/mcpand every human-approval field note writes the exact MCP config for Claude Desktop, Claude Code, Cursor, or Cline, with uvx, pipx, pip, orpython -m. The optional API key stays in browser memory and is never stored or sent. - Added
agentdraft-benchmarkis now a standalone MIT package with a public mirror atryabinski-labs/agentdraft-benchmark, a committed baseline report, and--keys-file/AGENTDRAFT_AGENT_KEYSsupport 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.
- Added
Older releases
- Free-tier webhook signing in the capability contract
- Plan, key, and webhook facts in the capability contract
- A transitive advisory pinned out of the frontend build
- Page counts from our own CDN logs
- Opt-in visit analytics on the public site
- The paragraphs were always there — now the markup says so
- Every post now answers its own question
- What the page says when you take the tags off
- The pages nobody could reach
- Dead URLs stop pretending to be the home page
- A plan between Team and a sales call
- A direct path to production pilots
- Two priced limits start applying
- The homepage stops contradicting the pricing page
- One name on both registries
- Sixteen blog posts step out of the way of the homepage
- Analytics stops following you past the marketing site
- Blog ingest accepts updates and deletes, not just creates
- One redirect path for a stored paid-tier signup
- Free tier now representable in the billing client
- Free tier can now run multiple agents
- Retired marketing URLs now resolve cleanly
- Approvals — a human sign-off gate for any agent action
- Cookieless marketing analytics goes live
- Answer-engine polish and a shorter path to an API key
- The blog claim guard checks claims, not keywords
- No more dead citation links on the blog
- Every published blog post is back in the sitemap
- Answer-engine remediation pass
- DNSCove authoritative DNS cutover
- Blog ingest API returns the real post URL
- Free calendar collision audit, right from the comparison pages
- Try the API with no signup
- Instant API key, plus a code fallback for magic links
- A faster path from CTA to API key
- Alternatives guides, glossary expansion, and benchmark census
- Trust pages, SEO metadata, and production API tuning
- Billing correctness and an open-source collision benchmark
- A guided setup checklist and a clearer, more accessible dashboard
- Send feedback from the dashboard, plus blog & security SEO fixes
- Checkout now collects tax and accepts promo codes
- Calendar list no longer breaks after disconnecting a feed
- Webmail calendar connector is now Folio
- Calendar connect surfaces real errors; local dev boots again
- Billing webhook resolves the correct plan
- Private app routes are easier for crawlers to retire
- Google user data disclosures
- Launch-readiness proof is easier to audit
- Dashboard sessions last through the workday
- Publish and webhook setup feedback is clearer
- Mailbox webhooks can target one agent
- Email-flow monitoring with AgentDraft mailboxes
- Block out your vacations
- Counter-proposals documented, plus API reference fixes
- Webhooks are now documented
- Booking notes and the video link now land on the calendar event
- The timezone picker is now searchable
- Set your timezone — the one that actually gates bookings
- SDKs speak title, invitee, and timezone
- Scheduling rules are actually enforced
- Working hours read in your own timezone
- Pricing answers its own questions
- Bookings know who they're for
- One canonical URL per marketing page
- Connected calendars resync themselves
- The glossary doubles in size
- Integration pages for n8n and the OpenAI Agents SDK
- A sharper share card and a more legible masthead
- The free Developer tier reaches the homepage
- A free Developer tier, a mobile nav, and a clearer homepage
- Blog posts published via the ingestion API render cleanly
- Recurring ICS events with a non-UTC UNTIL now expand fully
- Permanently delete revoked agents
- Lowercase-safe agent mailbox routing
- Mid-run human consent for high-impact agent actions
- Marketing claim audit and pricing copy alignment
- Conferencing links, Calendar Audit, ChatGPT App, coordination-layer pillar
- Dashboard Webhooks page
- P1 differentiation moat — multi-agent negotiation + OSS engine reference
- P0 distribution oxygen — A2A protocol, two more /vs pages, Vercel AI + Mastra adapters, Claude skill
- Footer composition + Field notes in masthead nav
- Launch wave 1 — collision benchmark, vs/temporal-cortex, newsletter capture
- SEO landing pages + outbound mail fix
- Launch-week polish
- Passkeys
- A real changelog
- Launch readiness — SDKs, packages, and discovery
- Calendar connectors, agent key lifecycle, mailbox API
- Agent mailboxes, onboarding, dashboard hardening
- Production architecture and deploy pipeline
- 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.