…ot everything Two data-contract defects, both measured, both of which read as model failures and were not. Written test-first; the tests fail against the old behaviour. 1. TRUNCATION WAS INVISIBLE. `bloqs list --json` returned 20 records as a FLAT ARRAY. The account has 137. No total, no truncated flag, no next — so a model reading it reasonably concluded it had everything, then answered "your family project is anomalyco#602" while anomalyco#200 Family Businesses, anomalyco#137 Family Health and Finance, anomalyco#544 and anomalyco#584 sat in the other 117. The API sends the total; the CLI dropped it on the floor. Now: {data, meta:{returned, total, truncated, limit, hint}}. Verified live — returned 20, total 137, truncated true. When the server sends no total, a FULL page is treated as truncated. Claiming "complete" on no evidence is exactly the failure being fixed: over-reporting costs one extra query, under-reporting produces a confident wrong answer. 2. `list` HAD NO FIELD CONTRACT. bloqs list = 20 records x 4 fields = 2,290 bytes agents list = 30 records x 72 fields = 145,395 bytes Same verb, 63x apart. The second overflowed the MCP every time, forcing a spill -> jq -> narrow round-trip to answer "what agents do I have". LIST_FIELDS caps a listing at 8 fields — identity plus discriminators — and a test enforces the ceiling plus the presence of an id and a human-readable label, because a row you cannot follow up with `get` is not lean, it is useless. `agents get <id>` still returns the full record. Measured: agents list 145,395 -> 7,828 bytes. 18.6x. It no longer overflows. WHY THIS RATHER THAN MORE PROMPTING. I previously diagnosed the missed-bloqs bug as a prompt problem and wrote tool-description guidance for it. That guidance still helps, but it was teaching models to compensate for a payload that misleads them. A tool returning 15% of the data while looking complete will defeat any model; one returning 145KB for a listing makes an easy question expensive. Fix the contract, not the reader. Shape change on --json for these two commands: consumers doing `jq '.[]'` now need `jq '.data[]'`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Uh oh!

Disable mouse scroll from input box? #544

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions