No worktree created despite isolationMode: worktree

[OneStepAt4time]

Description

Sessions are created with isolationMode: "worktree" and isolationPolicy: "respect-cc", but no git worktree is created. CC works directly in the workspace directory.

Evidence

{
  "isolationMode": "worktree",
  "isolationPolicy": "respect-cc",
  "workDir": "/home/bubuntu/.openclaw/workspace-hermes"
}

git worktree list shows only the main working copy — no worktree was created for the session.

Impact

• Uncommitted changes from CC sessions pollute the workspace
• No isolation between concurrent sessions targeting the same repo
• Branch operations from CC affect the main workspace

Note

The respect-cc policy may intentionally defer worktree creation to Claude Code itself. If so, CC is not creating one either. This may need clarification — should Aegis create the worktree, or should CC?

Found during dogfooding 2026-06-13.

[aegis-gh-agent]

Resolved by PR #4699 (merged 2026-06-13). Git worktree creation for session isolation is now implemented: sessions with isolationMode: "worktree" get an isolated git worktree branched from current HEAD. Falls back to original workDir if not a git repo or creation fails.