$ t3 triage --agent codex Starting Codex. It will ask what went wrong. WARNING: proceeding, even though we could not create PATH aliases: CODEX_HOME points to "/evidence/run/codex-state", but that path is not a directory Error finding codex home: CODEX_HOME points to "/evidence/run/codex-state", but that path is not a directory Codex exited with code 1. Codex keeps its state in /evidence/run/codex-state. If that drive is out of space, free some up or set CODEX_HOME to a folder on another drive. The triage prompt and machine context were written to: /evidence/run/t3-home/userdata/triage/2026-11-11T09-31-50-055Z/triage-playbook.md /evidence/run/t3-home/userdata/triage/2026-11-11T09-31-50-055Z/context.md To retry, start `codex` yourself with any flags it suggested, or use any coding agent, and give it this prompt: Read the file "/evidence/run/t3-home/userdata/triage/2026-11-11T09-31-50-055Z/triage-playbook.md" and follow its instructions exactly: it is your T3 Code triage playbook, and it starts with asking the user what went wrong. CLI exit status: 1 $ t3 triage --no-daemon DESCRIPTION Investigate a T3 Code problem on this machine with claude or codex, and help file a good issue. USAGE t3 triage [flags] FLAGS --base-dir string Explicit T3 Code data directory; runtime state is stored under userdata (equivalent to T3CODE_HOME). --agent choice Agent CLI to use. Default: ask when both are installed. (choices: claude, codex) --model string Model passed through to the agent CLI. Default: the agent's default. GLOBAL FLAGS --help, -h Show help information --version, -v Show version information --wizard Start wizard mode for a command --completions Print shell completion script (choices: bash, zsh, fish, powershell, sh, pwsh) --log-level Sets the minimum log level (choices: all, trace, debug, info, warn, warning, error, fatal, none) ERROR Unrecognized flag: --no-daemon in command t3 triage CLI exit status: 1