fix(session): recognize Gemini CLI 'Invalid session identifier' as session-not-found#35
Merged
osolmaz merged 1 commit intoopenclaw:mainfrom Mar 1, 2026
Conversation
…ssion-not-found Gemini CLI returns 'Invalid session identifier' with JSON-RPC code -32603 when session/load is called with an acpx-owned UUID. This text was not matched by isSessionNotFoundText, preventing the reconnect fallback to session/new and causing RUNTIME: Internal error. Add 'invalid session identifier' to the pattern list.
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
2 participants
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.
Problem
When acpx reconnects a Gemini session, it sends
session/loadwith acpx'sown session UUID. Gemini CLI does not know this UUID and returns:
with JSON-RPC error code -32603.
isSessionNotFoundText()did not matchthis text, so
shouldFallbackToNewSession()returned false and the errorwas thrown instead of falling back to
session/new.This caused every
acpx gemini prompt --sessionto fail with[error] RUNTIME: Internal error, whileacpx gemini execworked fine.Fix
Add
"invalid session identifier"to the pattern list inisSessionNotFoundText().Test
acpx gemini sessions newecho "Say hello" | acpx --verbose gemini prompt --file -
Before: [error] RUNTIME: Internal error
After: [acpx] loadSession failed, started fresh session → prompt succeeds