feat: Add profile-scoped gateway autonomy runtime#4711
Closed
ambrosecltr wants to merge 2 commits into
Closed
Conversation
Contributor
|
Thanks for the thorough work on this, @ambroseacoulter — the architecture spec and implementation are well thought out. We're not looking to add a proactive autonomy subsystem to the gateway at this time, so closing this PR. Appreciate the contribution! |
7 tasks
This was referenced Apr 29, 2026
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.
What does this PR do?
Adds a profile-scoped autonomy runtime to the messaging gateway so Hermes can track open-ended watch items, revisit them in the background, and surface useful updates naturally without relying on cron for everything.
This introduces a gateway-only autonomy system with durable state in SQLite, hot-path watch registration for explicit requests, hidden post-turn extraction for implied follow-ups, supervisor-driven findings/drafts, and proactive inbox/outbox delivery to a configured home chat. It also adds config controls for extraction mode, proactivity level, quiet hours, retention, and tool access, plus docs for setup and behaviour.
Type of Change
Changes Made
extract_behavior, home chat targeting, quiet hours, retention, and proactivity controls in gateway/config.py and hermes_cli/config.py/autonomycommand support and autonomy-aware session metadata in hermes_cli/commands.py and gateway/session.pyHow to Test
config.yaml, set a home chat, and start the gateway.Keep an eye on OpenAI for me. Let me know if anything interesting happensand verify it creates an autonomy watch instead of inventing a cron schedule./autonomy,/autonomy watch, and/autonomy runsto confirm watch registration, background supervisor activity, and clean run summaries.Checklist
Code
fix(scope):,feat(scope):, etc.)pytest tests/ -qand all tests pass (All tests associated with PR are green, failed tests are existing)Documentation & Housekeeping
docs/, docstrings) — or N/Acli-config.yaml.exampleif I added/changed config keys — or N/ACONTRIBUTING.mdorAGENTS.mdif I changed architecture or workflows — or N/AScreenshots / Logs
Focused verification after merging
main:Result:
251 passed