v0.30.1
What’s New in v0.30.1
Reliability & Security
- Scheduler gates can now distinguish a confirmed skip (
exit 1) from an indeterminate check (exit 75). Indeterminate results honor each schedule’s fail-open or fail-closed setting, so transient network, authentication, or parsing failures do not silently masquerade as an empty queue. - Gate subprocesses receive configured keychain-backed secrets only in their ephemeral environment. Secret names and values are not persisted in schedules and are redacted from diagnostics.
- Gate failures are sanitized, stripped of terminal control sequences, and safely bounded in run history, preserving useful troubleshooting context without leaking sensitive data.
Compatibility
- No migration or configuration changes are required.
- Existing gate commands continue to work unchanged. Remote or otherwise fallible gates can adopt
exit 75to signal an indeterminate result.
Documentation
- The scheduled-task documentation now covers gate exit semantics, fail-open behavior, secret handling, and diagnostic safety.
Implementation: #476
Documentation: claude-threads-site#57