jpmschweitzer/settled-reach
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(briefings): log worktree-sandbox dead-end + image.show win (clide)

Browse Source 
T2: background agent / lead writes are confined to the session root, so an
out-of-root sibling worktree (.worktrees/<branch>) is unwritable — the
agent could design but not write, and there's no permission to grant. Fix
options for clide noted. Plus a positive: clide image show works first-try.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
jpmschweitzer
2026-06-07 12:57:10 +02:00
co-authored by Claude Opus 4.8
parent 1cb53b3654
commit 5dfea07bff
3 changed files with 91 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/briefings/clide-team-mode-friction.md
+26
View File
@@ -83,3 +83,29 @@ earlier is unrelated background sessions, not this teammate.) This sharpens the
**Workaround taken this session.** Kept Tyre's delivered round-1; ran the rest of the Q-101 workshop
as **background Agent subagents** (the Si/reviewer pattern), which DO surface in clide's normal Claude
activity flow — i.e. avoid `teammateMode` teammates until the team-chat view is wired to the mailbox.
### FINDING T2 — background agent + out-of-root worktree is a sandbox dead-end — 2026-06-07
**What.** Spawned a background Agent (not a `teammateMode` teammate) to implement a server ticket in
an isolated git worktree at `/var/mnt/data/projects/settled-reach/.worktrees/<branch>` — a *sibling*
of the session root `/var/mnt/data/projects/settled-reach/main`. The agent could Read/Grep/cargo fine
and produced a complete design, but **every `Edit`/`Write` was denied**: sandboxed file writes are
confined to the session's project root, so the sibling `.worktrees/` path is unwritable — by the
agent *and* by the lead. It is not a clide permission toggle; there is nothing to "grant."
**Impact.** The whole background-agent-in-worktree isolation pattern is unusable under the current
sandbox: the agent burns a full run designing, then blocks at the first write. The user (reasonably)
looked for a permission to grant and found none. Fallback was to drop the worktree and implement in
the main checkout on the branch.
**Suggested fixes (for the clide team).**
1. Create agent/teammate worktrees *inside* the writable root (e.g. `main/.worktrees/<branch>`), or
2. Extend the sandbox's writable root to cover the repo's sibling worktrees, or
3. At minimum, fail fast with one clear up-front error ("worktree path is outside the writable root")
instead of per-`Edit` denials that read as a grantable permission.
### Positive — `clide image show` works well — 2026-06-07
`clide image show <path> --caption "..."` rendered and displayed a generated diagram first try, with a
clean `{shown:true}` return. A solid parity data point alongside the team-mode gaps — the observe/drive
surface (D-6) is sound where it's wired; the gap is specifically team-mode rendering, not the CLI model.