Conversation
| response = web.json_response({"ok": True, "ignored": event_type}) | ||
| except CompanionClosedError as exc: | ||
| self._dedup_rollback(request_id) | ||
| return web.Response(status=503, text=str(exc)) |
| return web.Response(status=503, text=str(exc)) | ||
| except CompanionError as exc: | ||
| self._dedup_rollback(request_id) | ||
| return web.Response(status=422, text=str(exc)) |
This was referenced Sep 20, 2026
alex-w-99
marked this pull request as ready for review
September 20, 2026 08:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Executive Summary
Add durable Companion mode conversation initialization to Codex bridge 0.2.14.
Description
The Companion inbox feeds the native session queue, records logical input and acknowledged thread/turn identifiers, and retains each turn's group reply target.
inkbox-codex companion-statusexposes checkpoints;companion-resolvesupports reviewed recovery. History never enters local command or approval parsing. Current main's activity callbacks, context-only queue messages, group reply behavior, A2A progress and audio support are preserved.All PR unit and contract jobs fetch and verify public SDK commit
449966c885208d41f995d09c54072e012df9eb1a, build the Python wheel fromsdk/python, and install it alongside the bridge. Runtime requirements and installed-version checks remain>=0.7.3,<1.0.0; no checks are disabled.Reason
Group conversations need complete available context and a durable boundary between initialization, subsequent messages and uncertain host execution. Exact-source SDK builds enable honest prerelease validation without depending on registry publication.
Decisions
Testing
companion-status,companion-resolve, group replies and uncertain restart recovery: expect fixed group targeting and no blind replay.86ca19e: Python 3.11/3.12/3.13 unit jobs and native host contracts. CodeQL also passed. Published-registry installation and live channel/model acceptance remain unverified.Readiness-triggered CI snapshot (2026-09-20 08:48 UTC)
Readiness-triggered Full stack e2e 35500001349 failed during dependency setup. The reusable canary and live installers still request registry
inkbox==0.7.3, which is unavailable. These paths need the same exact-source dependency handling as unit CI before tests can run; no live acceptance is established.Companion PR stack
These peer PRs each target their own
main; the coordinated set is now ready for review.Review and release status
Ready for review. SDK/CLI 0.7.3 remains unreleased; SDK PR 190 and public source commit
449966c885208d41f995d09c54072e012df9eb1aare the dependency reference. Current-head unit/contract CI passed; any readiness-triggered live checks require their own completed results. Package publication and full live channel/model acceptance are not claimed.