Not switched on
Useful3 Signal4
The local-command tool refuses to run unless your sandbox is strict and fully confining.
Sandbox preconditions for the local command bridge are enforced, but the bridge itself is flag-gated.
What's wrong with this entry?
Anonymous. No account, no email.
What
Before running anything, the local-command tool checks the device's sandbox and refuses with a specific reason if sandboxing is off or unsupported on the platform, failed to start, is not in strict mode, allows all Unix sockets, or is set to inject real credentials into network requests. Each refusal returns an error saying what to change on that device.
Details
- successful runs emit
tengu_device_bash_servedwith whether the exit code was zero, duration, whether output was truncated, and whether the session matched - separate events cover timeouts, output limits, cancellation and failures
- refusals carry distinct reason codes, so a device that never runs commands can be told apart from one that ran and failed
Evidence
tengu_device_bash_served
Strings lifted out of the shipped bundle, so the claim above can be checked against them.