feat(assist): sticky sessions and agent routing#10
Open
dalehamel wants to merge 2 commits intotechartdev:mainfrom
Open
feat(assist): sticky sessions and agent routing#10dalehamel wants to merge 2 commits intotechartdev:mainfrom
dalehamel wants to merge 2 commits intotechartdev:mainfrom
Conversation
Partial/incomplete debug logging references (CONF_DEBUG_LOGGING, broken options.get() calls) were accidentally included in this branch. The full debug logging feature lives in feature/debug-logging.
Author
|
Related to this i implemented '/new' handling dalehamel#2 so that we can get a new context window if we want one (but it has to be done through text chat) |
DarrenBenson
added a commit
to DarrenBenson/OpenClawHomeAssistantIntegration
that referenced
this pull request
Mar 29, 2026
Merges dalehamel's fix for agent ID routing (issue techartdev#8): - Agent ID sent as model field (openclaw:<agent_id>) for gateway routing - Sticky sessions persisted to disk, durable across HA restarts - Resolved agent ID used consistently (voice_agent_id || configured_agent_id) Merged on top of our room awareness feature (device area injection). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
DarrenBenson
added a commit
to DarrenBenson/OpenClawHomeAssistantIntegration
that referenced
this pull request
Mar 29, 2026
…ky sessions) The static session ID override is no longer needed now that PR techartdev#10 provides durable, agent-scoped sticky sessions persisted to disk. The old option caused confusion by routing all requests to whichever agent owned the named session, bypassing voice agent routing. Removed from: config_flow, conversation, strings, translations. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Previously as documented in #8, we were seeing that the agent ID was completely ignored, and every new chat created a new session with open claw.
It seems the headers we were setting are completely broken?
This fixes both issues by:
We now see that home assistant correctly routes the session and reuses it:
Previously this would route to 'main' and chew through tokens as it reloaded all the agent info for every conversation very wastefully.