Changelog

User-visible changes to the hosted Pro Edition and this site, dated by production deploy — newest first. Internal refactors and dependency housekeeping are omitted. The Free Edition’s npm packages keep their own release notes: elicitly and @elicitly/tools.

2026-09-13

• A proper hello (and a check-in) when you join. New organization admins now get a short welcome email at signup with the fastest path to a first approval, and a personal check-in about two business days later asking how it’s going. Both are plain text from a real person — replies go straight to a monitored inbox. The privacy policy now lists Resend, the service that delivers them.
• The dashboard’s “Connect your agent” section works for every MCP host. Your MCP endpoint URL is now front and center with a copy button, the Claude Code one-liner is labeled as the example it is, and a link leads to the install guide for everything else.
• Install guide: ChatGPT and Codex instructions. A new section points at OpenAI’s MCP connector guide (ChatGPT desktop, Codex CLI, and IDE — one shared configuration), notes the Developer-mode requirement, and links our troubleshooting page for the known Codex OAuth-refresh issue.

2026-09-09

• The site reads better on phones. The header and footer now stack cleanly in portrait, link tap targets got breathing room, and pages use more of the screen width on small displays.
• llms.txt is now linked from the site footer. The machine-readable docs index has always been served (and advertised to crawlers); now it’s one click away for humans too.

2026-09-08

• Clearer Contact us page. Sales and support are now two distinct paths: talk to sales about the Enterprise Edition (self-hosting, SSO/SAML, compliance), or get support with direct links to the documentation and live service status.

2026-09-07

• elicit_doctor no longer fails on hosts that don’t support elicitation. Running elicit_doctor with probeElicitation: true against a host that doesn’t advertise elicitation now returns a clean “not attempted” result (and still records/shares the report) instead of erroring the call — so the capability report always comes back.
• The selection review page matches Elicitly’s design. The hosted elicit_selection grid now uses branded controls, clearer rows, and a primary Submit / quiet Decline layout, in both light and dark themes.
• Clearer elicit_doctor description for better agent tool selection — mirrors the same tightening in @elicitly/tools.
• New Troubleshooting page. Fixes for common connection problems, starting with ChatGPT/Codex connectors that stop working after a failed OAuth token refresh (codex mcp logout + reconnect).
• Elicitation Support Matrix refreshed. Current-build fingerprints for Claude Desktop 1.46388.4 (local and remote connector — elicitation not advertised on either) and ChatGPT Desktop 26.901.51231 (stdio and remote HTTP, both form and URL modes verified working), plus a new attachment-path dimension distinguishing config-file from desktop-extension installs.

2026-09-04

• Richer MCP tool contracts across all 12 hosted tools. Every input parameter now carries its own description (elicit_selection’s Liquid templates and selection limits included), and each tool declares a human-readable title, behavior annotations (read-only / destructive / idempotent hints), and — except the plain-text elicit_ping — an output schema, with results returning structuredContent alongside the JSON text. Agents get better tool selection and typed results; both transport lanes serve the identical contract. elicit_confirm / elicit_form / elicit_doctor mirror the same contract shipped in @elicitly/tools 0.6.0, so hosted and Free stay in lockstep.
• New concepts page: The Narrated Gate. Why a prose confirmation gate can be satisfied by narration — the agent describing asking instead of asking — and how a tool-call gate like elicit_confirm closes that gap.
• Landing page: the hero’s elicitation dialog now carries a slow aura ring spotlighting the human-checkpoint moment (respects reduced-motion).
• Connector icon fix for dark-mode hosts: the site now serves a full-bleed apple-touch-icon.png, so hosts that scavenge favicons for connector chips get maskable artwork instead of the rounded browser-tab favicon whose transparent corners rendered white on dark themes.

2026-08-23

• Claude.ai (Cowork, web) joins the Support Matrix. Like Claude Desktop, it advertises elicitation.form but never renders the dialog (probe advertised_but_unanswered, embedded client claude-code 2.1.241) — the same #88901 hang. This corrects the earlier note that claude.ai lacked elicitation entirely: it advertises it, it just doesn’t work yet.
• Claude Code stdio row refreshed to 2.1.231. A community fingerprint (elicitly 0.5.0, form probe accepted in 7.8s) confirms the row holds on the newer release; the 2.1.228 evidence moves to superseded. Contributed via the free edition’s contribute-fingerprint prompt.
• Claude Desktop joins the Support Matrix — its thesis row. Custom connectors advertise elicitation.form, but the live probe never renders a dialog: verdict advertised_but_unanswered, archived verbatim from an owner-run capture on Claude for Mac 1.34493.1. The embedded client identifies as claude-code 2.1.241 — the same client library that renders forms correctly in Claude Code — so the gap is the Desktop connector UI, not the protocol client. This is the case the Pro Edition’s hosted review page exists for.

2026-08-22

• The connector icon renders cleanly in MCP hosts. Hosts mask connector icons with their own corner radius; the site favicon’s baked rounded-rect showed white corners in Claude Desktop’s connectors list. The MCP endpoint now serves a full-bleed square mark (/favicon.svg, /icon.svg) and declares it via the spec’s serverInfo.icons, so both icon-aware hosts and favicon scavengers get maskable artwork. Browser tabs keep the rounded favicon.
• contribute-fingerprint survives hosts that never answer the probe. Field-testing in Claude for Mac showed two failure shapes the prompt didn’t handle: the prompt text arrives as an attachment (which a cautious model reads as injected instructions), and the live probe can hit the host’s tool-call timeout before the report returns. The prompt now states its user-initiated provenance up front and, on a probe timeout or repeated error, contributes a passive report with the failure recorded in notes — the timeout is the finding (advertised_but_unanswered), not a reason to give up. The prompt’s docs gain a Claude Desktop tip: invoke it from the + menu (Connectors → Add from your connector), and use Cowork mode — Chat mode’s tool calls errored out in testing. And the root cause is fixed on the hosted server: the doctor’s live probe now gives up after 40 seconds — below common host tool-call limits — so a host that never delivers the dialog gets the finished report back in one round, timeout verdict included.
• Pro install docs cover Claude Desktop and claude.ai. The Install page’s register step was written for Claude Code and config-file hosts; it now also walks the Add custom connector form (name + URL, keep the detected defaults, no request headers) and the Connect sign-in step.

2026-08-19

• Contribute a fingerprint in one step. elicit_doctor gains an opt-in share: true (plus productName / productVersion / notes): the hosted server stores the finished report in the Support Matrix’s evidence queue — no copy-paste, no email. The new contribute-fingerprint prompt (the server’s first MCP prompt; hosts that support prompts list it — in Claude Code it’s a slash command) walks the whole flow: host details, consent, probe, share. Reports remain payload-free (handshake echo, capability booleans, probe verdicts); nothing is stored without share: true; the matrix stays curated — contributions are evidence for review, not automatic edits.
• The free edition contributes too — elicitly 0.5.0 ships its own contribute-fingerprint prompt: same flow, but ending in a pre-filled GitHub issue (nothing sent automatically). Its first community contribution landed within hours and gave the Claude Code stdio row its first verbatim archive — every matrix row now links archived evidence.
• Docs: a Prompts section, sibling to Tools, starting with contribute-fingerprint — flow, consent scope, and the planned Free-edition variant. The Support Matrix also now sorts freshest capture first and separates each row’s current evidence from superseded fingerprints (earlier versions of the same host), both on the page and in the CSV.
• Claude Code remote-HTTP form elicitation: working as of 2.1.228. The very first prompt-driven contribution flipped the matrix’s most-watched cell: the auto-cancel bug (anthropics/claude-code#85442) is fixed in practice — live probe, dialog rendered, answer round-tripped. History preserved in the row; before/after fingerprints archived.

2026-08-16

• Listed on the Official MCP Registry and Smithery. Both editions are published on registry.modelcontextprotocol.io under the DNS-verified ai.elicitly namespace — ai.elicitly/elicitly (the free stdio server on npm) and ai.elicitly/pro (the hosted remote). Elicitly Pro is also live on Smithery as elicitly/pro, domain-verified, and the install guide notes the Smithery gateway as an alternate connection route.
• Agent discovery, end to end. An agent can now find, understand, and authenticate to Elicitly starting from nothing but the domain name, by standards at every hop: a DNS-AID record (_mcp._agents.elicitly.ai, DNSSEC-signed — the whole zone now validates) points at the MCP host; an API catalog (RFC 9727) and homepage Link headers (RFC 8288) advertise the machine-readable surfaces; an MCP Server Card (SEP-1649) at /.well-known/mcp/server-cards.json — on this site and on the MCP host itself — describes the server, its endpoint, and how to authorize.
• Content Signals in robots.txt. Explicit search=yes, ai-input=yes, ai-train=yes: for an agent-native product, being searchable, quotable in AI answers, and present in training data is distribution, not leakage.

2026-08-15

• Fixed: form-mode elicitation answers through the hosted server. A runtime restriction in our hosting environment broke validation of every form answer a host delivered over the legacy protocol — the dialog worked, but submitting it returned an error. Found via a ChatGPT Desktop fingerprint, fixed the same day, and re-verified live. (The failure was ours, not the host’s — the correction is on record.)
• elicit_doctor failures now say why. Error probes include the underlying rejection in probes.elicitationForm.reason — the field that cracked the bug above.
• Support Matrix: evidence layer. Rows now link the verbatim elicit_doctor fingerprints they were derived from, split by transport (stdio vs. remote HTTP), track the negotiated MCP protocol revision and capture date, and export as CSV. ChatGPT Desktop is the first host verified working over remote HTTP in both elicitation modes — form and URL.