Tab Watchdog
Per-tab self-healing is not a stable Chau7 feature.
Availability
The advertised workflow is not available as a connected feature in stable v0.5.1. Source components or future work do not make it a shipped capability.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- Stale UI or a hung command can interrupt work.
- Recovery copy should distinguish app-level monitoring from per-tab repair.
What ships with it
- No per-tab stale-state watchdog or automatic refresh was found in stable source.
- The app has separate main-thread hang and restore-pipeline recovery.
- Those components do not establish continuous per-tab self-healing.
Questions this answers
- Does stable Chau7 automatically repair stale tabs?
- Is per-tab self-healing available in stable?
How it works
The audited stable source does not show a per-tab watchdog that compares expected and rendered tab state and refreshes a stale tab. Claims of continuous per-tab health checks and automatic retries are unsupported.
The app contains other recovery and monitoring components, including main-thread hang recovery and restore-pipeline timeout handling. Those are app-level or startup recovery paths, not evidence that every terminal tab can heal itself.
Do not rely on stable Chau7 to detect and restart a frozen shell, repair arbitrary terminal desynchronization, or retry a failed tab refresh. Those behaviors need a user-facing implementation and verification.
Why it matters
Feature copy must distinguish app-level recovery tools from per-tab monitoring. The stable release does not substantiate the feature as currently described.
Frequently asked questions
Does stable Chau7 refresh a frozen tab automatically?
No per-tab auto-refresh implementation was found in the stable source audit.
Is there any watchdog code in the app?
There are app-level hang and restore recovery components, but they do not establish the claimed per-tab stale-state watchdog.