Evidence record / agent-flywheel
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-09-21-agent-flywheel-carry-forward-safe-mode-is-still-not-a-boundary-at-v0-9-0-dangerous-aliases-unchanged
Carry-forward: safe mode is still not a boundary at v0.9.0; dangerous aliases unchanged. Two things moved, the boundary did not. (a) Since v0.8.0,
~/.zshrc.local is sourced last (v0.8.0 line 746, v0.9.0 line 762; v0.7.0
line 238 sourced it before the aliases), so an operator override such as
alias cc='claude' now actually sticks; the in-file comment says the earlier
order “silently re-armed them on every new shell”. (b) cod now pins a model
and xhigh effort on the command line, overriding ~/.codex/config.toml.
Channel: tagged-release. Half: defect. Date: 2026-09-04 (tag read).
Operator consequence: The profile’s avoid_for stands at v0.9.0: switching
to safe mode does not revoke an earlier vibe run’s sudoers file, and the
dangerous shortcuts ship regardless of mode. New mitigation that works: put
un-dangerous alias overrides in ~/.zshrc.local on v0.8.0+. On v0.7.0 that did
not work. Note the cod model pin is a model-and-effort pin, not a CLI version
pin.
Receipt
Finding metadata
Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0
Finding ID: 2026-09-21-agent-flywheel-carry-forward-safe-mode-is-still-not-a-boundary-at-v0-9-0-dangerous-aliases-unchanged
Profile citations
- Agent Flywheel / claim / safe-mode-not-a-boundary-at-v0-9-0
Source links
Primary links, including exact changelog lines when available.
Versioned source: run artifact