feat(cli): add operator message-post and agent-status nouns (RIG-2662, RIG-2663) - #585
Open
rigel-mintaka wants to merge 1 commit into
Conversation
|
Compass engineering docs preview: https://compass-rig-2662-2663-cli-me.compass-eng-docs.pages.dev Deployed from |
…, RIG-2663) The operator `compass` CLI had no way to post a channel message or inspect agent-session state — both were dogfood gaps (an operator could not message the Manager or see whether a session was live from the CLI). Adds two nouns following the existing secret/agent-config Cobra pattern: `compass message post --channel <id> --topic <name> [--mention <handle>]` (body read from stdin, never argv, so it cannot leak into the process table; over CommsService/PostMessage) and `compass agent status [--session <id>]` (over CompassService/GetAgentStatus, rendering session id + state). Both dial the authenticated network door / unix socket via the shared connection flags. Note on RIG-2663 Fix 3b (GetAgentStatus permission_denied on the dev-http door): that was a misdiagnosis, not a server bug. The dev-http browser door deliberately mounts no bearer interceptor, so AdminGate fail-closes adminOnly RPCs there to prevent the 'Dev Door Can Mint Admin Tokens' hole. GetAgentStatus is adminOnly and operators read it over the network door (TLS + admin bearer) or the socket — exactly the door this CLI dials. No server change. Refs RIG-2662, RIG-2663 Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
force-pushed
the
compass/rig-2662-2663-cli-message-agent-status
branch
from
August 24, 2026 14:57
86fb894 to
588ac36
Compare
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.
This PR is part of a stack containing 3 PRs:
mainThe operator
compassCLI had no way to post a channel message or inspect agent-session state — both were dogfood gaps (an operator could not message the Manager or see whether a session was live from the CLI).Adds two nouns following the existing secret/agent-config Cobra pattern:
compass message post --channel <id> --topic <name> [--mention <handle>](body read from stdin, never argv, so it cannot leak into the process table; over CommsService/PostMessage) andcompass agent status [--session <id>](over CompassService/GetAgentStatus, rendering session id + state). Both dial the authenticated network door / unix socket via the shared connection flags.Note on RIG-2663 Fix 3b (GetAgentStatus permission_denied on the dev-http door): that was a misdiagnosis, not a server bug. The dev-http browser door deliberately mounts no bearer interceptor, so AdminGate fail-closes adminOnly RPCs there to prevent the 'Dev Door Can Mint Admin Tokens' hole. GetAgentStatus is adminOnly and operators read it over the network door (TLS + admin bearer) or the socket — exactly the door this CLI dials. No server change.
Refs RIG-2662, RIG-2663
Co-authored-by: Matt Wilkinson matt@rigel.build