Feature: Add tasksDirectory setting (like plansDirectory)
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
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗