Daemon-mode background workers now try to claim a controlling terminal at startup.
tengu_bg_worker_ctty Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.251: off
Read once, for one account on one subscription tier, against v2.1.251. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
When the background backend is run as a daemon (CLAUDE_BG_BACKEND=daemon), startup now tries to acquire a controlling terminal for the worker, gated by tengu_bg_worker_ctty which defaults to on. Normal interactive sessions never reach this. If the gate is off it only checks whether a terminal was already acquired.
- Outcomes recorded are acquired, already, failed, ffi_unavailable, not_a_tty, unsupported and switched_off.
- Failures and the case where the native binding is unavailable are also sent through a separate error-reporting path, not just logged.
bg_worker_ctty
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Background daemon start failures are classified, and a sleeping machine gets one retry
Both mention daemon background
-
v2.1.248
Background daemon can retire a same-version instance
Both mention daemon background
-
v2.1.248
The background daemon defers restarts and idle exits while an upgrade is pending
Both mention daemon background