Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,12 @@

## Unreleased

- Add the bounded `compass.query.agent-view/1` projection for coding agents.
Typed CLI and MCP query text now lead with result state, answer, and caveats;
`--format agent-json` and MCP `agentView` expose the same deterministic
source-linked view while raw query JSON remains unchanged. Discovery text
keeps its v2 cursor ledger and adds only an answer-first fixed header.

## 0.3.26 - 2026-09-15

- Make query failures and paths more trustworthy: exact-looking missing symbols
Expand Down
16 changes: 16 additions & 0 deletions COMPATIBILITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,22 @@ history profiles, and cache identities.

## Evolving contracts

### Agent Query View

Compass adds the additive strict projection `compass.query.agent-view/1` for
typed CLI and MCP consumers. It is derived from, and digest-bound to, the raw
`compass.query/1` or `compass.query.discovery/1` response. The raw CLI `json`
shape, MCP `structuredContent.result`, graph schemas, and discovery
`compass.query.discovery-text-page/2` cursor meaning are unchanged.

The typed commands accept `--format agent-json`; default text is an
answer-first presentation. MCP keeps `compass.mcp.tool-result/1` and adds the
optional `agentView` sibling plus a code-query `semanticResultDigest`. Existing
consumers may ignore the optional projection. Consumers that consume Agent
View must reject unknown major versions, enforce the documented bounds, and
distinguish `no_match`, `needs_resolution`, `no_path`, source truncation, and
projection truncation from a positive complete answer.

Immutable history now accepts up to 5 GiB of aggregate authoritative key and
value bytes per realization, raised from 512 MiB. The history schema and
canonical encoding are unchanged, as are the per-key, per-value, per-tree,
Expand Down
Loading
Loading