Owner question: one 'Update automatically' switch for T3 and provider CLIs, or two? #149

Recommendation: one switch (upstream's).

Context: update design for the fork. Keep the fork's updater (fork #5) until upstream's own lands, then take upstream's whole and keep three small add-ons: default stays OFF (fork #41, pinned by a test), an "update only between these hours" setting, and the existing quiet command. 7 PRs (+1 conditional).

The question: after the sync, upstream's "Update automatically" also updates the provider CLIs in the background. One switch for both, or a second fork switch for the CLIs?

• One switch (recommended): less fork code to carry; with it off (our default), neither updates on its own.
• Two switches: T3 and the CLIs can be set apart; more fork code.

Reply "one" or "two".

🤖 Generated with Claude Code