Feature request: Stealth mode (no committed Entire config)

Problem or use case

I would love to use entire, but I am not sure i am willing to go thro the corporate machinery required to get it not only approved but like incorporated into every devs flow. I would like to be able to use Entire without needing to commit any file to the repo, because the configs live elsewhere or are gitignored (which I can do for now myself), and without having commits autopushed nor autolabeled

Desired behavior

Something like https://deepwiki.com/search/find-info-related-to-the-so-ca_0bcddd4e-bd30-4dc6-afb6-2745dcfc790c?mode=fast (Bead's stealth mode)

Proposed solution

Something like https://deepwiki.com/search/find-info-related-to-the-so-ca_0bcddd4e-bd30-4dc6-afb6-2745dcfc790c?mode=fast (Bead's stealth mode)

Alternatives or workarounds

From codex:

Closest unsupported workaround

You could approximate stealth like this:

entire enable --local --skip-push-sessions
Never commit .entire/settings.json
Never commit agent hook/plugin files
Manually remove Entire-Checkpoint trailers from every commit
That may work for personal local use, but it is brittle and easy to leak accidentally. I would not call that a real supported stealth mode.

Start with the existing entire enable --local --skip-push-sessions behavior and the .entire/settings.json workaround described in the issue. Define the supported stealth-mode boundaries, including config storage, agent hook/plugin files, commit trailers, pushes, and labels, then verify that local use does not require repository changes or leak Entire metadata.