Repository navigation
Releases
Releases · nyssance/codex-acp
v0.7.63
v0.7.62
- Merge upstream: ACP SDK 2.5.0; checklist plans from
update_planareitemsplan_updates withplanIdcodex-structured-plan; fast mode sends thefastservice tier (Codex reports it back aspriority, which still reads as fast). - Follow upstream where the fork duplicated it. Session titles in the list and in history are normalized as upstream normalizes them (whitespace collapsed, 256 characters) instead of the first line cut at 120. A custom permission profile resolves to the mode upstream picks from the allowed list. Fork lineage pages through upstream's history paging, with its timeout.
_codex/skills_listomits the skills the adapter disables. - Removed:
capabilities._meta.codex.rename. The exported client reads rename support from the standardcapabilities.session.title;hasRenameandcodexExtensionCapabilities(agent).renamekeep their meaning. - Changing
systemPromptonsession/resumeworks again. Since 0.7.60 the app-server unloads a detached thread at once and refuses a resume while it closes; the adapter now waits for the unload before it resumes. - Source formatting follows upstream throughout. No behavior change.
v0.7.59
- Approval reviews on a gateway session run on a model the gateway serves. A gateway model's
auto_review_model_overridedefaults to itself instead of Codex's nativecodex-auto-review, which a third-party endpoint such as DeepSeek rejects; a reviewer named by the provider catalog resolves to that model's alias on the same gateway, and one the gateway does not list is a registration error.
v0.7.58
- Composer predictions are upstream's predicted follow-up prompt. A client that declares
clientCapabilities._meta.alwith.capabilities: ["promptSuggestions"]receives_meta.promptSuggestionsonsession_info_updateafter each completed turn, as AIR does; the exported client declares it and reads it withpromptSuggestion(session._meta). Removed:_codex/session_prediction_request, thecomposerPredictionscapability flag,requestPredictionandcomposerPredictionon the client, and the fork's ephemeral prediction thread. - Merge upstream codex-acp 2.6.0. The upstream prompt suggestion (AIR clients) samples the session thread with
thread/sampleinstead of forking it, and skips plan mode and turns that did not complete; approval prompts carry the command as their title so Zed labels them. Shell-wrapped commands are unwrapped for display only when the quoting is recognized.
v0.7.56
session/listis answered by the upstream session index for a client that declares_meta.alwith.capabilities: ["sessionIndex"], with standard rows: top-levelarchived,_meta.codex.{projectId,nativeSessionId,forkedFromId}, titles repaired where the native preview starts with a prompt envelope. The exported client declares it. Removed:_codex/session_list, the fork's own list and rollout fork index, andthreadSourceonsession/new,session/fork, lineage andSessionSummary. A v2 client that declares neither index gets upstream's legacy list and archive-on-delete.- A failed turn's
_meta.codex.errorcarries the adapter's own failure classification, the one its AIR session failures use:kind(CodexFailureKind),categoryandactions. The fork's second taxonomy (categorysuch asusage_limit,retryable,stopReason) is gone;codexTurnErrorreturnskind,category,actionsandretryablederived fromactions. Retrying a failed turn follows the same policy. - Reply envelopes are parsed by upstream's
parseAsyncQuestionReply; session titles are derived with upstream's attachment-envelope reader. The fork'ssessionConfig.tsis gone. - An external provider's HTTP 402 (DeepSeek's exhausted balance) reaches Codex as its usage-limit error instead of a retried connection failure. The turn error names the provider host, the 402 and the provider's message, and the thread keeps it; the proxy diagnostic records the upstream status.
v0.7.55
- Filter restricted subagent sessions from the ACP v2
session/listand overlay theiradditionalDirectories, as the other list paths do. - Send
useStateDbOnlywiththread/list, matching upstream. - ACP v1 session responses no longer carry
_meta.codexlineage, matching upstream; v2 keeps it. - Remove fork copies of upstream helpers and the unused
CodexImportClient.detectandreadHistorieswrappers. codexExtensionCapabilitiesalso reportsproviderCatalog,realtimeandsessionHistory;supportsCodexRealtimetakes the initialize response.- Document every fork-only method, its native counterpart and consumer in
docs/ALWITH-MIGRATION.md.
v0.7.54
Standard ACP set_title/archive/unarchive and archived list filter; session history rendered by the upstream replay path; gateway registrations, tool and session states reported as the protocol defines; unused extensions removed. See CHANGELOG.md.
v0.7.53
0.7.39
0.7.38
0.7.38 (2026-10-27)
- Ship
CodexClienton the./cliententry:@alwith/api/client's SessionClient plus every_codex/*extension (full session list, archive, history browsing and export, skills, plugin marketplaces, rate limits, file search, retries, predictions, fork lineage, realtime). ALwith U'scodex-extensions, history readers and activity preview move here with their tests. - The
./cliententry now depends on@alwith/api(peer,>=0.4.22) and keeps it external in the bundle.