Repository navigation
v1.5.0
Added
- The scheduled ACP ecosystem drift check now pins and monitors the newly
publishedzai-org/ZCoderepository alongside the Claude, Codex, and Pi
adapter references. The pin and the check are repo-only; no library code or
behavior changes. - Pi adapter golden-transcript characterization suite:
ExMCP.Test.PiGolden(test/support/acp/pi_golden.ex) and seven golden
areas undertest/ex_mcp/acp/adapters/pi/characterization/with fixtures
undertest/fixtures/acp/pi/, pinning the adapter's RPC envelopes,
control-group ordering, stream-event conversion, prompt scheduling,
configuration updates, slash commands and session-store safety rules
before thePi.*boundary extractions. Repo-only; nothing ships to Hex. ExMCP.Client.subscribe_notifications/3and
ExMCP.Client.unsubscribe_notifications/2, a public delivery path for
legacy-era (MCP 2024-11-05 through 2025-11-25) list-change and
resource-update notifications. A listener registers a filter using the same
keys aslisten/3, minustaskIds, and receives matching notifications as
{:ex_mcp_notification, listener, method, params}. Listened resource URIs
are subscribed on the server once and shared across listeners, released
when the last listener naming them goes away or its subscriber exits, and
re-subscribed after an automatic reconnect with a
{:ex_mcp_notification_reconnected, listener, result}report. On a modern
peer the call returns{:error, :use_listen}. Previously the client parsed
these notifications and dropped them with a warning about an unknown
subscription; that warning is now a debug-level message when no listener
matches. Modern subscription routing andsubscribe_resource/3are
unchanged (#44).
Changed
-
Internal:
.dialyzer_ignore.exsdrops fifteen filters that no longer match
a warning, and documents that entries must be verified in bothMIX_ENV=dev
andMIX_ENV=testbecause the files undertest/are only analyzed in the
test environment. No analysis result changes. -
ACP reference-adapter parity, from the 2026-09-20 drift review of
claude-agent-acp and codex-acp (both still on ACP SDK 1.4.0):- Claude SDK adapter: a host may opt a session out of
bypassPermissions
with_meta.claudeCode.options.allowDangerouslySkipPermissions: false
onsession/new,session/load, orsession/resume. The mode leaves
the catalog,session/set_moderefuses it, and an active bypass mode is
clamped todefaultthrough aset_permission_modecontrol.true
cannot override the adapter's own option. (claude-agent-acp#1129) - Claude SDK adapter: an AskUserQuestion custom answer no longer replaces
a selection. It joins a multi-select in the CLI's own quoted form, and
for a single-select it rides beside the pick as the tool's per-question
annotations[question].notes, so a client that presents the box as a
notes field cannot make the selection disappear. (#1031, #1131) - Codex adapter:
item/tool/requestUserInputforms follow codex-acp#299.
The elicitation message is always "Codex needs your input to continue.",
the question text is the field title and the header its description,
every question is required, anisOtherquestion with options gains a
"None of the above" choice and a separate<id>_notefield tagged
_meta.codex.role: "user_note", and note text returns to Codex as
user_note: <text>beside the selection instead of replacing it. A
whitespace-only answer is dropped. Wire-visible for clients that read
the previous<id>__otherfield or_meta.codex.isOtherAnswer. - Codex adapter:
session/loadpages a thread's older turns through
thread/turns/listwhen the resume result carries a backwards cursor,
replaying the full history in order instead of only the newest hundred
turns; the initial page is now requested newest-first and reversed. A
server without the method, or a failed page, still loads with the
initial page. (codex-acp#481) ExMCP.ACP.Adaptertranslations may return
{:messages_and_reply_and_write, messages, result, iodata, state}, and
session/loadandsession/resumeaccept{:reply_and_write, ...}.- Deferred with recorded decisions (pre-standard
_metaextensions, not
in ACP SDK 1.4.0):authStatus,recommendedValue,asyncTasks,
tool-callname, and both compaction mechanisms. Not applicable:
codex-acp#471, since ExMCP forwards MCP elicitations without a
synthetic tool call. Seedocs/POST_1_0_MAINTENANCE_PLAN.md.
- Claude SDK adapter: a host may opt a session out of
-
Internal: the three Mint-based pinned HTTP clients
(ExMCP.Internal.PinnedHTTPClient,ExMCP.Authorization.PinnedHTTPClient,
andExMCP.Transport.HTTP.BoundedClient) now share one pure response
reducer,ExMCP.Internal.HTTPResponseReducer, for Mint event accumulation
and bounded-body decisions. Each client keeps its own DNS pinning, TLS,
compression and framing policy, error atoms, and return shapes. No public
API or behavior change. -
mint moves to 1.10.1, which fixes
EEF-CVE-2026-82672(unvalidated
chunk-size line tail in the HTTP/1 client).mix hex.auditfails on 1.10.0
since the advisory was published on 2026-09-19. -
Internal dependency-cycle reductions with no public API change. Seven of
the ninemix xref graph --format cyclescomponents reported on Elixir
1.19.5 / OTP 28.3.1 are gone (MessageProcessor/MethodHandlers,
Content.Validation/Rules,SchemaPolicy/SchemaRemoteResolver,
ExMCP/ClientConfig,Server.Subscriptions/Tasks, the
Internal.SessionStorebehaviour and its ETS/DETS backends, and the
VersionRegistry/Protocol.Methods/ErrorCodes/Typesversion cycle),
each through a narrow dependency inversion or a small@moduledoc false
lower-level module (ExMCP.Tasks.StoreCall,
ExMCP.Internal.SessionStore.Factory,ExMCP.Internal.RevisionCatalog).
The two large client and transport cycles remain; see
docs/POST_1_0_MAINTENANCE_PLAN.md. -
The Codex ACP adapter is split into
ExMCP.ACP.Adapters.Codex.Permissions,
Codex.Content, andCodex.MCP(internal modules) with no wire-visible
change: the golden transcript fixtures are byte-identical, and the public
ExMCP.ACP.Adapters.CodexAPI and state struct are unchanged. See the
Codex status indocs/POST_1_0_MAINTENANCE_PLAN.md.
Fixed
-
Pi adapter: three agent-controlled payloads no longer crash the adapter.
A streamed tool call carried underpartial.content[contentIndex]is now
selected withEnum.at/2(Accesscannot index a list, so the clause
written to support that shape always raised), and aget_available_models
payload whosemodelsis not a list, or whose entries are not maps, drops
the unusable data instead of raising. Found by the new Pi characterization
gate and pinned by three golden scenarios. -
Codex adapter:
session/loadhistory replay now handles app-server v2's camelCaseagentMessageitems. Previously a replayedagentMessagereached the streaming completion path with no session state and crashed the load; only the legacyagent_messagespelling replayed. -
ExMCP.SessionManagerno longer logs atinfowhen it starts or when it
sweeps expired sessions; both aredebug. The:ex_mcpapplication boots
before a stdio server can suppress logging, and the default Elixir logger
writes to stdout, so in a release that did not configure:stdio_mode
ahead of boot the startup line landed in the protocol stream before the
first frame. A subprocess test now boots the application's supervision tree
under the default logger and asserts stdout stays empty. The configuration
guide documentsconfig :ex_mcp, stdio_mode: truetogether with
config :logger, :default_handler, config: [type: :standard_error]as the
stdio deployment setting that closes the window for every application in
the VM. -
The stdio transports no longer let the process locale translate protocol
frames.ExMCP.Server.StdioServerandExMCP.ACP.Agent.Transport.Stdio
now detect, on every read and write, whether each device is a character
or a byte device and use the matching calls, through one shared framing
owner, which is byte-exact for UTF-8 on every supported OTP and survives
the VM flipping a device to latin1 after undecodable input (on OTP 27 that
flip still ends the session under a UTF-8 locale; see the transport
guide). Previously,
under a C locale or no locale (launchd, systemd, minimal MCP host
environments) the MCP stdio server double-encoded non-ASCII input and
emitted\x{...}escapes for non-ASCII output, producing invalid JSON,
while under a UTF-8 locale the ACP agent transport corrupted non-ASCII
input. An echo tool masked the MCP case because the write reversed the
read's damage. A byte-order mark before the first frame is now stripped
instead of hanging the session atinitialize. Diagnosed by deepfates in
#41. A shared non-ASCII payload corpus now runs byte-exact through every
transport, with a locale matrix on the stdio subprocess test (#52).