← 2.1.9 Primitive inconclusive · runtime-test

plansDirectory Setting

New setting plansDirectory allows customizing where plan mode stores plan files.

plansDirectory is a Claude Code 2.1.9 setting that customizes the file system path where plan mode stores plan files.

How It Works

The setting allows users to override the default plan storage location (~/.claude/projects/{project}/plans/) with any custom path. It accepts both absolute paths and project-scoped relative paths via settings.json:

{"plansDirectory": "/path/to/custom/plans"}

or project-scoped:

{"plansDirectory": "./plans"}

Test Status

The feature was not runtime-tested. The 2.1.9 test documented setup steps and expected behavior (set the setting, enter plan mode, write a plan, verify the file location) but stopped at code review stage without executing them. Epistemic status: inconclusive.

Use Cases

The setting targets four practical scenarios: storing plans in version control instead of ~/.claude, centralizing team-accessible plan files, organizing plans within existing project structures, and placing plans in directories covered by backup policies.

Caveats

Without runtime verification, the actual behavior remains unconfirmed. The setting may not handle all path types (environment variables, symlinks, relative traversal) predictably. Path resolution timing relative to plan mode initialization, permission requirements, and directory creation behavior are undocumented. Teams considering this for git-tracked or shared workflows should verify these gaps before production use.

Evidence & receipt
  • file2.1.9/tests/03-plans-directory/TEST-RESULTS.md
◇ ed25519 receipt
idprimitive_b87f5a35cd195354f70581ef
alged25519
pubkey9b87705613b1e2fd064d57fa75a6b679d2856ceafad6b1daa8f982493871b6dd
sigc1a2fcb23ef3924722e5e471fc7a25790a9102c0a2d3bf0ae0498361897c4e3837a1f3c8697af74ac9e0f4a13001fe356be6ef584355593dabfa448bb274f502

Signed with an ed25519 key held off the repo. Anyone can verify against the published public key; nobody without the secret key can forge it. Click verify: it recomputes the signature in your browser. The signature proves integrity and authorship of this exact content — not a third-party timestamp or that the underlying claim is objectively true. signedAt is when the @f3/attest pipeline ran, not when the work happened; the evidence refs carry the source dates.

Connected