[Feature Request] Add statusline customization setting for managed hook environments

Resolved 💬 3 comments Opened May 5, 2026 by doubleyou Closed Jun 3, 2026

Bug Description
When managed settings allow only managed hooks, it's impossible to set a custom statusline, because all script executions are blocked. Suggest there should be a separate statusline setting in settings.json, which either allows custom statuslines explicitly, or allows certain script paths.

allowManagedHooksOnly is a very useful setting for a proper security posture (albeit a bit clunky), so turning it off just for the sake of having statuslines seems unreasonable. But it also seems unreasonable that statusline is tied to hooks in the first place.

Environment Info

  • Platform: linux
  • Terminal: kitty
  • Version: 2.1.119
  • Feedback ID: 71b5ef71-899c-4cd9-883d-081957088bd6

Ways to reproduce

  1. Specify {"allowManagedHooksOnly": true} in managed settings.
  2. Attempt to specify a statusline in the local settings.json.
  3. Verify that the statusline script is never executed
  4. Set {"allowManagedHooksOnly": false} in managed settings.
  5. Observe the statusline working now.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗