[BUG] Zoo is attempting to be refactored, but a permission issue occurs when accessing the `mkdir /plans` directory.

[juneleung]

Describe the bug
For unknown reasons, there are often numerous instances where users want to mkdir /plans in the root directory but lack permissions; it should be created in a relative directory (./plans), not the absolute root directory(/plans).

To Reproduce
Steps to reproduce the behavior:

1. Go to Architect mode
2. Task to rebuild the structure
3. Zoo wanna makir a "plans" dir, but it failed in "/plans", should be "./plans"
4. See error

Expected behavior
create plans dir in ./ , not in the /

Screenshots

Date/time: 2026-07-20T11:27:10.882Z
Extension version: 3.70.0
Provider: openai (proxy)
Model: gpt-4o

Error handling partial write_to_file:
EROFS: read-only file system, mkdir '/plans'

Video
NA

What version of zoo are you running
Version: 3.70.0 (ce7f7dc)=

Additional context
NA

[taltas]

@zoomote can you take a look at this? Reprouce and diagnose

[zoomote]

I'm on it. I started a task for this issue, and I'll keep updates here.

See task

[zoomote]

Reproduced and diagnosed: the Architect mode customInstructions ended with "put it in the /plans directory", and the leading slash makes models treat /plans as an absolute filesystem path — hence EROFS: read-only file system, mkdir '/plans' when saving a plan file.

Fix: the instruction now says ./plans and explicitly clarifies it's relative to the workspace root (packages/types/src/mode.ts), with the affected system-prompt snapshots regenerated. Full pnpm test passes (6786 tests, including the prompt snapshot tests).

Draft PR: #968 — I'm doing a self-review on GitHub and will share what I find.