Feature: Add tasksDirectory setting (like plansDirectory)

[nikitaCodeSave]

Feature Request

Add a tasksDirectory setting to settings.json to allow storing task lists per project, similar to how plansDirectory works for plans.

Problem

Currently, tasks are stored only in ~/.claude/tasks/<session-id>/ or ~/.claude/tasks/<CLAUDE_CODE_TASK_LIST_ID>/. There is no way to store tasks in the project directory.

Current behavior

Data Type	Directory Setting	Project-level Support
Plans	plansDirectory ✅	Supported
Skills	.claude/skills/ ✅	Supported
Commands	.claude/commands/ ✅	Supported
Agents	.claude/agents/ ✅	Supported
Tasks	❌ None	Only ~/.claude/tasks/

Proposed solution

Add a tasksDirectory setting in settings.json:

{
  "tasksDirectory": ".claude/tasks"
}

This would:

• Store tasks in .claude/tasks/ within each project
• Allow tasks to be committed to version control if desired
• Enable project-specific task persistence without symlinks
• Be consistent with existing patterns (plansDirectory, .claude/skills/, etc.)

Workaround

Currently using symlinks:

mkdir -p .claude/tasks
ln -sf /path/to/project/.claude/tasks ~/.claude/tasks/project-name

With CLAUDE_CODE_TASK_LIST_ID=project-name in settings.

Environment

• Claude Code version: 2.1.17
• OS: Linux

[github-actions]

Found 3 possible duplicate issues:

1. [FEATURE] Project-Specific Todo Storage #7274
2. [Feature Request] Persistent todo list management across projects with project-specific configuration #14927
3. [FEATURE] Decouple default task tracker via hooks and allow substituting for an alternative task tracker. #12582

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[nikitaCodeSave]

Not a duplicate

The suggested duplicates are about different features:

• [FEATURE] Project-Specific Todo Storage #7274 — session persistence/restore
• [Feature Request] Persistent todo list management across projects with project-specific configuration #14927 — session management improvements
• [FEATURE] Decouple default task tracker via hooks and allow substituting for an alternative task tracker. #12582 — task state persistence

This issue is specifically about directory configuration parity — adding tasksDirectory setting similar to existing plansDirectory.

Current workaround

I'm using a wrapper script (~/bin/cc) that sets CLAUDE_CODE_TASK_LIST_ID per project:

#!/bin/bash
export CLAUDE_CODE_TASK_LIST_ID="$(basename "$(pwd)")"
exec claude "$@"

This gives each project its own task list, but tasks still live in ~/.claude/tasks/ rather than in the project directory.

A native tasksDirectory setting would:

• Allow tasks to be stored in .claude/tasks/ within the project
• Enable version control of tasks if desired
• Be consistent with plansDirectory pattern

[MarvDann76]

I think this is a good idea especially when teams are working on long running low priority refactors for example where different team members need to pick up where another left off in a previous iteration.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.