[BUG] Running /bg for Agents view looses plan mode scope

Status Fixed / completed
Reported on v2.1.139
Maintainer reply ✓ Yes — bogini
Activity 4 comments · opened May 12, 2026 · closed May 13, 2026
💡 Likely answer: A maintainer (bogini, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When there's an active agents view and from another active CC instance we run /bg , the session gets pushed there. But if that session was in plan mode it looses that mode.

What Should Happen?

When running /bg it should respect the current mode of CC (plan mode)

Error Messages/Logs

Steps to Reproduce

  1. In terminal 1 run: claude agents
  2. In terminal 2 start claude and setup plan mode
  3. Run /bg in terminal 2
  4. agents view regarding terminal 2 looses plan mode.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.139

Platform

Other

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] · 5 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/58259

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

bogini collaborator · 5 months ago

Thanks for the clear repro — confirmed and fixed. /bg (and the ←← detach gesture) now propagate the active permission mode to the background worker, so plan/acceptEdits/auto carry over instead of resetting to default.

Ships in v2.1.141 (tomorrow). Appreciate the report!

claude[bot] contributor · 5 months ago

This issue was fixed as of version 2.1.141.

github-actions[bot] · 3 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.