cozempic v1.8.24 — Agent-team safe-point hardening
This release makes the guard's safe-point reload gate agent-team aware: cozempic will not SIGKILL-and-reload a session while an Agent-spawned teammate is still working, and it fails toward block (defer) whenever it sees team coordination it can't fully resolve.
What's new
- Agent-spawned team visibility at the reload gate (PR #117, thanks @ynaamane): the safe-point gate now sees teammates created via the
Agenttool — not justTeamCreate— and defers a reload while any teammate is non-terminal. - Deny-by-default net: if the transcript shows team coordination the parser can't resolve to a roster (a drifted/unknown marker shape), the gate blocks instead of reloading through it.
- Robustness: camelCase
agentIdparsing, an anti-wedge for disbanded teams (TeamDelete), and a fail-safe that keeps blocking when a spawn result can't be parsed but didn't affirmatively fail.
Reliability hardening (found and fixed by our own adversarial QA fleet)
We ran the bundle through our standing QA fleet, which caught — and we fixed — over-block regressions in the new net before release:
- A spawn marker (
agent_id:) is credited only when it's paired with a real spawn tool — so reading code/YAML/logs that merely containagent_idno longer wedges the guard. - Teammate-message detection keys on the harness's structural delivery surface, so discussing or pasting protocol text no longer blocks reloads.
TeamDeleteis team-scoped, so disbanding one team can never SIGKILL another live team.
Both failure directions (reloading through live work and wedging a normal session inert) are now covered by the standing contract test tests/test_reload_gate_contract.py.
Full test suite: 1265 passed.
Install / upgrade
pip install -U cozempic # or: uv tool upgrade cozempic
npm install -g cozempic
brew upgrade cozempic # Ruya-AI/cozempic tap