Release v2026.8.2 · hex/claude-council

What's Changed

A large prompt reaches the Antigravity CLI on Windows. agy takes its prompt only as the value of -p, and Windows caps a command line at 32k, so a --file-sized prompt died in CreateProcess before agy ever started. Past COUNCIL_ARGV_LIMIT (24000 by default) the question is written to a file of its own and agy is pointed at it. Found and diagnosed by @DavidChin0.
COUNCIL_PROVIDERS pins a standing roster. Discovery enlists every agent on PATH, ollama included once installed. Precedence is --providers, then COUNCIL_PROVIDERS, then discovery, and both --list-default and --list-available report the pinned set.

The spill gets a directory of its own. --add-dir had been handed the whole temp root, 17,980 entries on the machine it was found on, and it is the only lever that widens --sandbox because agy has no allowed-tools flag.
The spilled file holds the question and nothing else. It had carried the answer guard, system prompt and verbosity directive into a file the argv prompt then disavowed, so a --verbosity brief run past the size limit lost its directive.
The spill prompt no longer forbids the one file it must read.
A malformed COUNCIL_ARGV_LIMIT such as 24k warns and falls back to 24000, instead of evaluating false and skipping the spill in silence.
A roster naming nothing usable says which roster emptied, rather than advising you to set an API key you already have.
--list-available and --list-default agree about what a default query runs.

Test inventory corrected in TESTING.md; COUNCIL_PROVIDERS and COUNCIL_ARGV_LIMIT added to the configuration table in docs/ARCHITECTURE.md.

Full Changelog: v2026.8.1...v2026.8.2