hermes-agent: deploy private Nero agent on tau - #668
Open
mulatta wants to merge 3 commits into
Open
Conversation
Provide Hermes through the shared llm-agents input so host modules can consume a pinned, reproducible agent package.
Keep terminal-capable Slack automation isolated while preserving declarative control over credentials, tools, and skill seeding. Restrict container egress to DNS and HTTPS through tau's active interface and expose the dashboard only across the private bridge.
Keep app identity, scopes, events, and slash commands reviewable beside deployment policy so Slack-side authority cannot drift without an infrastructure change.
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.
Deploy Nero as a private single-user Hermes Slack agent on tau so terminal-capable automation stays isolated and its authority remains reviewable. This adds SOPS-managed credentials, restricted bridge networking with HTTPS/DNS-only egress, declarative tool and skill policy, a loopback-only dashboard, and a versioned Slack manifest for identity, scopes, events, and commands; the tau NixOS build, repository formatting, JSON validation, and Slack CLI local-manifest validation pass.