feat(compass-agent): agents_tree native tool — indented agent tree with live presence (RIG-2678) - #1062
Open
rigel-mintaka wants to merge 1 commit into
Open
feat(compass-agent): agents_tree native tool — indented agent tree with live presence (RIG-2678)#1062rigel-mintaka wants to merge 1 commit into
rigel-mintaka wants to merge 1 commit into
Conversation
…th live presence (RIG-2678) New read-only `agents_tree` tool, sibling of `compass_roster`: one `GetRoster` call (scope `subtree`|`owner`, default `subtree`), assembled client-side into an indented parent→child tree with each agent's presence + activity. Pure agent-side — no proto, no RPC, no server work; the roster already carries `parent_agent_id` + `presence`. Handles and display names only, never account ids (ids are the internal tree keys); every peer-supplied string is `flat`-guarded exactly like the roster rows. An orphan (unknown parent) attaches at root rather than vanishing; a malformed parent cycle terminates via a `visited` set, each node rendered once. Matt-ruled pull-tool-over-prompt-bake (the tree is live state, so a prompt bake would rot). The when/how usage guidance rides compass-server's prompts workstream separately, not a second prompt edit here. Closes RIG-2678 Co-authored-by: Matt Wilkinson <matt@rigel.build>
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
|
Compass engineering docs preview: https://compass-agent-rig-2678-agent.compass-eng-docs.pages.dev Deployed from |
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.
New read-only
agents_treetool, sibling ofcompass_roster: oneGetRostercall (scopesubtree|owner, defaultsubtree), assembled client-side into an indented parent→child tree with each agent's presence + activity. Pure agent-side — no proto, no RPC, no server work; the roster already carriesparent_agent_id+presence.Handles and display names only, never account ids (ids are the internal tree keys); every peer-supplied string is
flat-guarded exactly like the roster rows. An orphan (unknown parent) attaches at root rather than vanishing; a malformed parent cycle terminates via avisitedset, each node rendered once.Matt-ruled pull-tool-over-prompt-bake (the tree is live state, so a prompt bake would rot). The when/how usage guidance rides compass-server's prompts workstream separately, not a second prompt edit here.
Closes RIG-2678
Co-authored-by: Matt Wilkinson matt@rigel.build