v0.6.22 — subject list --query title filter - #288
Merged
Conversation
Adds a case-insensitive substring filter on the subject TITLE to `subject list` (CLI flag + the animus.subject.list MCP tool). When --query is set the full set is fetched and filtered client-side, then the page limit is applied — so an agent or the portal can resolve a subject by name without paging, and without the agent-facing MCP result truncating a large unfiltered list. The daemon re-serializes the typed SubjectFilter (dropping unknown fields) and the backend has no title filter, so filtering in the CLI list handler is the clean, no-protocol-change path.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
Adds a case-insensitive substring filter on the subject title to
subject list— a new--queryCLI flag, surfaced on theanimus.subject.listMCP tool.Why
Agents (and the portal) had no way to look a subject up by name:
subject listsupports only kind/status/labels/limit/cursor, and the agent-facing MCP result truncates at a size budget — so on a large board (e.g. 180+ knowledge repos) a lookup by name was impossible (the agent only ever saw the first page).--querymakes name lookup a first-class operation.How
subject list --query <text>fetches the full set (the daemon re-serializes a typedSubjectFilter, dropping unknown fields, and the backend has no title filter), then filters by title client-side in the list handler and applies the pagelimitto the matches. Result carries an exacttotaland a nullnext_cursor. No protocol/plugin/version-line changes.Test
cargo fmt --check,clippy -p orchestrator-cli: clean--querydecision_gatetest failures exist onmain(v0.6.21) unrelated to this change.