Repository navigation
Discover and resume existing Claude Code sessions through ACP - #3
Merged
Merged
Conversation
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.
Existing local Claude Code conversations now appear in Alto's sidebar and History pane through ACP session listing. Opening a conversation replays its transcript and continues its original native session with Ask permissions. Stable IDs prevent duplicate history entries, and replay preserves recency and saved transcripts on failure. Claude history remains available if Codex cannot start.
Validation: typecheck and production build pass; 80 focused existing tests pass. Temporary verification exercised real Claude CLI history replay and continuation, pagination, concurrent requests, restart, failed loads, and unavailable Codex. No unit or integration test files were added to the repository.
The full test suite passed 967 tests with one existing Electron browser-test failure. That failure and the design-system audit failures reproduce on unchanged main. Local real-agent verification used the cached pinned adapter because the machine's npm package filter blocks the default npx launcher; direct installed-adapter configuration is documented.