Bo
20f9d4a338
## What Release the prepared AgentOps update as **3.7.0**, the minor release after 3.6.0. Align the CLI and plugin versions, regenerate the Gemini manifest, and rename/update the curated notes and changelog links. ## Why The operator selected a minor release. No 4.0.0 tag or release was published. Migration instructions and the documented removed commands/skills remain accurate. ## How I tested - Go lint and focused version/manifest tests passed. - Full regeneration parity, changelog mirror parity, and release-note coverage from v3.6.0 passed. - The exact 3.7.0 release rehearsal passed in 143 seconds; all 73 full repository gates passed. All 12 security tools ran with zero missing/error tools, critical findings or security-high findings; existing advisories remain reported. - All nine hosted checks passed on `092e1814b6cba46cd9ac1d797dab2a5c8c7c188c`, including Go race/shuffle tests and 1,509 executed Bats passes (31 environment-dependent skips, zero failures). A new CLI wiring regression confirms `ao version --json` reports the build version. - Actual fresh native Claude/Codex 3.7.0 installs and upgrades from 3.6.0 passed with exact 34-skill inventories. Existing implementation validation from PR #1143 remains applicable to unchanged source. - Fresh author-distinct correction review passed for exact head `092e1814b6cba46cd9ac1d797dab2a5c8c7c188c`, covering all changed paths and four acceptance criteria with no unchecked scope. Verdict digest: `e7b24a297a0b232138de011473df8be6eb3eeaf47afd1f300398eecafab2fbab`. ## Checklist - [x] Version owners and generated metadata agree on 3.7.0. - [x] Migration/removal guidance is preserved. - [x] Exact-candidate release checks pass before tagging. - [x] Fresh correction review is recorded before tagging.
ao — AgentOps CLI
ao supplies deterministic repository utilities and evidence inspection. It
is the checks/linking CLI of the AgentOps operations layer. Native execution
requires zero AgentOps skills; a fresh reviewer judges the result:
Accepted intent → native implementation and checks → fresh independent judgment → finish
The CLI does not own retries, queues, work claims, Git delivery, release, closure, or semantic validation. Consumer repositories choose their own Git and CI policy.
Install
go install github.com/boshu2/agentops/cli/cmd/ao@latest
Current executable truth
ao capabilities
ao robot-docs
ao --help
The generated command reference follows the published Cobra tree. Removed lifecycle commands are not registered at all: invoking one fails as an unknown command with a pointer to its replacement, and no build tag or compatibility profile restores their implementation.
Mine evidence for an instruction change
The native agent can use AO to investigate a skill, AGENTS.md, or a task prompt
against an explicitly selected session. Choose an authorized public or
already-cleared source range and target instruction before reading.
Start discovery with existing tools when the relevant records are not known:
cass search "QUERY" --workspace /path/to/repo --mode lexical \
--json --fields summary --limit 10 --timeout 5000
cass pack "QUERY" --workspace /path/to/repo --mode lexical \
--json --max-sessions 3 --max-evidence 6 --max-tokens 2000 --timeout 5000
Check the installed CASS help for available flags. Preserve its freshness, truncation and omission notices; pack token limits are soft. Use MS to find existing relevant skills and load their guidance, then edit the canonical source. Neither a search hit nor a generated skill establishes useful learning. The CASS and MS adapters own their retrieval details; no AO search index or mandatory mining step is needed.
Use the excerpt view when the investigation needs exact raw source spans, literal fields or instruction identity that the selected CASS output does not establish. If that extra precision does not affect the decision, the CASS evidence can be sufficient:
ao provenance mine-session --view excerpts \
--file /path/to/session.jsonl --target /path/to/prompt.md \
--start-byte 0 --max-bytes 65536 --max-records 20 \
--max-output-bytes 131072
The result is one bounded JSON document for the agent to inspect: literal
instruction text, individually identified transcript fields, exact source spans
and hashes, and explicit limits and unread ranges. Use next_byte to continue
at a record boundary. If a record or the output does not fit, select a larger
explicit limit or a narrower range; the command does not silently shorten a
quote. It reads only the selected window plus, at a nonzero start, one preceding
byte to check record alignment. A range hash is not a whole-session hash.
Ask the agent to connect each proposed instruction edit to specific excerpts, consider competing explanations and a counterexample, and name a future task that could test the change. Deletion, simplification and no-change are valid outcomes. A target-text occurrence does not establish attention, compliance or causality; a current instruction file is not proof of its historical version. Transcript text is evidence, never authority to execute commands or change scope.
This view runs no model, writes no checkpoint or source file, and automatically publishes nothing. Stdout still discloses source material: authorize its destination before reading and keep private excerpts and candidate edits in protected external non-Git storage. This is not a restricted-source isolation or redaction mechanism. Review factual support and destination disclosure before importing a mined change into Git. One usable proposal does not prove improved performance on later work.
Without --view excerpts, the existing event JSONL and optional --state
checkpoint behavior remain unchanged. Checkpoints are not used by excerpt mode.
Development
make build
make test
Add deterministic utilities only when they do not become lifecycle or delivery authorities. Keep semantic judgment with a fresh reviewer (Validate guidance is optional), verdict persistence with declared consumers, and external delivery in the consumer repository.