claude-code - 💡(How to fix) Fix FleetView: support Shift+Tab to cycle permission modes (plan / accept-edits) in the new-task input

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

In the claude agents (FleetView) background-task input ("start a task in the background"), make Shift+Tab cycle the permission mode for the about-to-be-dispatched chat — the same keybind that already cycles modes inside an active chat session.

Display the currently-selected mode somewhere near the input (a chip / hint, e.g. ▸▸ mode: plan (shift+tab to cycle)), so submitting with Enter dispatches the new chat in that mode.

Root Cause

In the claude agents (FleetView) background-task input ("start a task in the background"), make Shift+Tab cycle the permission mode for the about-to-be-dispatched chat — the same keybind that already cycles modes inside an active chat session.

Display the currently-selected mode somewhere near the input (a chip / hint, e.g. ▸▸ mode: plan (shift+tab to cycle)), so submitting with Enter dispatches the new chat in that mode.

Fix Action

Fix / Workaround

In the claude agents (FleetView) background-task input ("start a task in the background"), make Shift+Tab cycle the permission mode for the about-to-be-dispatched chat — the same keybind that already cycles modes inside an active chat session.

Display the currently-selected mode somewhere near the input (a chip / hint, e.g. ▸▸ mode: plan (shift+tab to cycle)), so submitting with Enter dispatches the new chat in that mode.

  • Relaunch claude agents --permission-mode plan (heavy, loses FleetView state).
  • Prefix every first message with /plan (one-shot, easy to forget).
  • Set permissions.defaultMode: "plan" in .claude/settings.json — currently not honored by the FleetView dispatcher (#59112).
RAW_BUFFERClick to expand / collapse

Summary

In the claude agents (FleetView) background-task input ("start a task in the background"), make Shift+Tab cycle the permission mode for the about-to-be-dispatched chat — the same keybind that already cycles modes inside an active chat session.

Display the currently-selected mode somewhere near the input (a chip / hint, e.g. ▸▸ mode: plan (shift+tab to cycle)), so submitting with Enter dispatches the new chat in that mode.

Motivation

Shift+Tab is already the muscle-memory keybind for switching between default, plan mode, and accept-edits inside a chat. But when spawning a new chat from FleetView, there's no equivalent — you have to:

  • Relaunch claude agents --permission-mode plan (heavy, loses FleetView state).
  • Prefix every first message with /plan (one-shot, easy to forget).
  • Set permissions.defaultMode: "plan" in .claude/settings.json — currently not honored by the FleetView dispatcher (#59112).

For workflows where I want to think-before-acting on a fresh chat in a specific directory, none of those match the ergonomics I already have inside a chat. Extending Shift+Tab to the dispatch input makes "spawn a new task in plan mode" a one-keystroke move.

Proposed UX

  • In the FleetView input box, Shift+Tab cycles permission mode the same way it does in-session: defaultplanaccept-edits → ...
  • The current mode is shown in the bottom hint bar near the input (e.g. ▸▸ mode: plan · shift+tab to cycle · enter to dispatch).
  • Mode is sticky for the FleetView session — if I set it to plan, the next dispatch also defaults to plan until I cycle again, so I can spawn several plan-mode chats in a row without re-toggling.
  • The dispatched chat starts in the selected mode (equivalent to passing --permission-mode plan to claude agents).

Related

  • #59112 — permissions.defaultMode not honored by FleetView dispatch.
  • #55368 — auto-enter plan mode for slash commands / sub-agents.
  • #39889 — dispatch-spawned sessions ignore user's permission-mode.
  • #46517 — auto-accept plan (unattended).

Workaround today

Relaunch FleetView with claude agents --permission-mode plan, or prefix the first message with /plan.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix FleetView: support Shift+Tab to cycle permission modes (plan / accept-edits) in the new-task input