Bypass permissions broken in VS Code extension; CLI non-functional in remote containers

OK Code wrote an abysmal issue report here. Basically it has run me around for about 10 resets of my VS Code session trying to get these two things working. The problem is this: I want to use the CLI version of Code because I can run in bypass permission mode but IDE integration is not working from my remote sessions (Docker). It probably has something to do with VS Code insisting on opening the terminal as root causing me to then have to su to the "developer" user in order to bypass permission because this isn't allowed in root. I'm trapped in a corner of Code not working for different reasons everywhere.

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/13488
2. https://github.com/anthropics/claude-code/issues/2933
3. https://github.com/anthropics/claude-code/issues/5859

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

Additional Context on Troubleshooting Attempts

Issue 1: Bypass Permissions

• Repeatedly advised to restart VS Code as the solution
• Restarted VS Code multiple times across multiple sessions
• Issue persists regardless of restarts
• Problem has existed for an extended period ("forever")
• Creates a frustrating loop where the same non-working solution is suggested repeatedly

Issue 2: CLI in Remote Containers

• Extension running as root user in container environment
• Root user execution causing additional problems
• No clear documentation on how to control which user the extension runs as
• Affects ability to use Claude Code in standard containerized development workflows

Impact

These are not edge cases - bypass permissions and remote container development are common professional development scenarios. The current state makes Claude Code unusable for these workflows, and the troubleshooting experience has been poor with solutions that don't address the root cause.

Resolved - kind of. VS Code was starting the container as root. Reconfigured VS Code to start it as "developer" and this is resolved. I spend a lot of time working around CC not being fully functional as root. I totally understand the security concerns but I develop in containers to give me the necessary protection. Please take off the training wheels.

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.