**Bug: Web UI permission settings ineffective + workspace path conflict (/root vs ~)**

[w1739902251]

Description

Issue 1: Web UI permission settings have no effect, preventing normal session use

• Observed behavior: Configuring Claude permissions (e.g., enabling tools) via the Web UI does nothing. The only workaround is to launch Claude from the command line using --dangerously-skip-permissions. When trying to use a session via the Web UI (e.g., after re-login), the terminal shows:

  Starting terminal in: /workspace/claude
  --dangerously-skip-permissions cannot be used with root/sudo privileges for security reasons
  Process exited with code 1
  

• Expected behavior: Permission settings in the Web UI (Tools settings) should take effect, allowing sessions to start normally without command-line flags.
• Actual behavior: Permission configuration is ignored, and the Web UI cannot start sessions due to the security restriction.

Issue 2: Using Claude from CLI causes workspace path corruption (/root vs ~)

• Observed behavior: Forced to use Claude from the command line (due to issue 1). Claude then creates projects and sessions under /root. After that, the “Select Folder” function in the Web UI fails to create a workspace, showing:

  Cannot use system-critical directories as workspace locations
  No subfolders found
  

  All workspace creation paths become locked to ~ (home directory) and cannot be changed.
• Impact: Severely breaks workspace management; the state is difficult to revert.
• Expected behavior: Claude should create projects under the user-specified workspace directory, not /root. The Web UI should allow selecting normal paths (outside system-critical directories) as workspaces.

Environment

• Deployment: Self-hosted via npx @cloudcli-ai/cloudcli or global install
• Permissions: Likely running with root/sudo privileges (as suggested by the error message)
• Version: Latest (v1.28.1 as of now)

Additional notes

• Issue 2 is likely a side effect of issue 1, but both critically affect core workflows.
• According to the documentation, Claude Code tools are disabled by default and must be enabled in settings – but the Web UI settings do not persist/take effect (issue 1).

Please let me know if you need more details or logs.

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• [BUG] Cannot create workspace in subdirectories of /root on VPS/dedicated servers #495

🔗 Related PRs

#208 - feat: Multiple features, improvements, and bug fixes [merged]
#289 - Add inline permission grant for Claude tool errors [merged]
#353 - fix: enforce WORKSPACES_ROOT in folder browser and folder creation [merged]
#451 - fix(claude): correct project encoded path [merged]
#462 - fix: preserve pending permission requests across WebSocket reconnections [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!