plansDirectory Setting — runtime test

Hands-on runtime battle-test of plansDirectory Setting. Result: INCONCLUSIVE.

plansDirectory Setting customizes the filesystem location where Claude Code stores plan files (default: ~/.claude/projects/{project}/plans/).

What Was Tested

A runtime verification of the plansDirectory setting added in version 2.1.9. The test design required: setting plansDirectory in project or global settings.json, entering plan mode, writing a plan, and verifying the file was saved to the custom location.

Test Result: Inconclusive

The test was never runtime-executed. The published results document only the code-review checklist and expected behavior, not actual execution. Status was marked CODE REVIEW with no completion evidence.

How the Setting Works

When configured, plansDirectory overrides the default plan storage path:

// Global: ~/.claude/settings.json
{"plansDirectory": "/path/to/custom/plans"}

// Project-scoped: .claude/settings.json
{"plansDirectory": "./plans"}

Documented use cases include storing plans in version control, team-shared locations, or at custom backup points.

Why It Remains Unproven

The feature was code-reviewed but not runtime-tested. A true test would require launching Claude Code, configuring the setting, authoring a plan, and verifying file placement. Without that execution, behavior remains unconfirmed—implementation may differ from intent, edge cases may exist, and integration with the planning workflow requires observation.

Primary source

⎘ 2.1.9/tests/03-plans-directory/TEST-RESULTS.mdverbatim from the corpus

Test Results: plansDirectory Setting

Feature: Added plansDirectory setting to customize where plan files are stored

Tested: 2026-01-16 Version: 2.1.9

Feature Description

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

Default location: ~/.claude/projects/{project}/plans/ Custom: Whatever path you specify

Test Result: CODE REVIEW

Would need to:

Set plansDirectory in settings.json
Enter plan mode
Write a plan
Verify plan saved to custom location

Expected Usage

// settings.json
{
  "plansDirectory": "/path/to/custom/plans"
}

Or project-scoped:

// .claude/settings.json
{
  "plansDirectory": "./plans"
}

Use Cases

Git-tracked plans - Store plans in repo instead of ~/.claude
Shared plans - Team-accessible location
Custom organization - Integrate with existing project structure
Backup policies - Place plans where backups run

Notes

Useful for teams wanting plan files in version control or shared locations.

Status: CODE REVIEW

Evidence & receipt

file2.1.9/tests/03-plans-directory/TEST-RESULTS.md ↓

◇ ed25519 receipt

idtest_1f851dc3cc7c906c9e3ea79e

alged25519

pubkey9b87705613b1e2fd064d57fa75a6b679d2856ceafad6b1daa8f982493871b6dd

sig

0aec2bbbb856b0e66eef3fd1331d2e02fc3d27af0afa0852529079be374b70843d25353216572454f85435d9d05ccd2be35e337a20d8df5a2a44ee07a473260e

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

verifies plansDirectory Setting Primitive