mirror of
https://github.com/usestrix/strix.git
synced 2026-10-01 02:03:55 +00:00
1d05637b68
Three issues raised in review on #1217, all real: - The STRIX_MAX_AGENTS check read agent_count() and then spawned, so two parents racing for the last slot both passed before either child registered and the graph overshot the cap. The coordinator now hands out slots atomically (try_reserve_agent_slot / release_agent_slot), counting outstanding reservations alongside live agents under the same lock. The slot is released once the spawner has registered the child or failed. Depth stays a plain check — a parent's depth cannot change mid-spawn. - _trim_parent_history kept the newest item whole when that item alone exceeded the budget ("and kept"), so the cap bounded nothing on the child's first request and could overflow the provider context window. An oversized newest item is now rendered as a truncated text message. No tool-call pairing can break: nothing else survives that trim. - --reasoning-effort exported STRIX_REASONING_EFFORT, which persist_current() then wrote into cli-config.json, turning a documented per-run flag into the default for every later run. Env vars can now be marked run-scoped and are skipped when persisting. Tests cover the concurrent reservation, slot release, the oversized-item trim, and the persist exemption. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| cli.mdx | ||
| instructions.mdx | ||
| scan-modes.mdx | ||
| viewer.mdx | ||