docs(hermes): add xAI OAuth auth guide for K8s and ECS#828
Merged
Conversation
github-actions
Bot
added
closing-soon
|
All PRs must reference a prior Discord discussion to ensure community alignment before implementation. Please edit the PR description to include a link like: This PR will be automatically closed in 3 days if the link is not added. |
- Option A: K8s port-forward flow - Option B: ECS curl-the-callback flow (step-by-step) - File ownership fix after exec-based auth (chown) - SuperGrok subscription requirement warning
pahud
force-pushed
the
docs/hermes-auth-guide
branch
from
a857ca1 to
06c3d42
Compare
thepagent
approved these changes
May 16, 2026
6 tasks
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.
Summary
Add detailed xAI OAuth authentication instructions for Hermes Agent, covering both Kubernetes (port-forward) and ECS Fargate (curl-the-callback) workflows.
Changes
chown -R agent:agentafter exec-based auth/config commands (exec runs as root, hermes-acp runs as agent)Context
Discovered during testing on ECS Fargate Spot — the OAuth flow is tricky because:
stateparameter must match the current session