Stats
Actions
Tags
From ws-clamp
Knowledge about Claude Code's project data model, storage locations, and path encoding
How this skill is triggered — by the user, by Claude, or both
Slash command
/ws-clamp:claude-project-dataThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides knowledge about how Claude Code stores project data, session history, and settings.
This skill provides knowledge about how Claude Code stores project data, session history, and settings.
Claude Code maintains project data in three interconnected locations:
| Location | Purpose | Format |
|---|---|---|
| Project directory | Your code + .claude/ settings | Directory with config files |
~/.claude/projects/[encoded-path]/ | Session history per project | JSONL session files |
~/.claude/history.jsonl | Global project index | Line-delimited JSON |
When you work with Claude Code in a project, it creates and maintains data across these locations. Moving a project with mv breaks the references because the encoded path changes.
Claude encodes project paths by replacing / with - for the folder name in ~/.claude/projects/. For example:
/Users/john/projects/my-app → ~/.claude/projects/-Users-john-projects-my-app/The clamp utility handles all three locations atomically when moving projects, with rollback on failure.
references/data-stores.md for detailed data store documentationreferences/encoded-paths.md for path encoding detailsexamples/common-workflows.md for usage patternsnpx claudepluginhub wsagency/ws-claude-marketplace --plugin ws-clampPersists project memory across Claude Code sessions. Auto-loads context on startup, tracks git activity, and saves session state via deterministic Node.js scripts.
Shows dashboards summarizing Claude Code projects with sessions, branches, contributions, and activity stats. Activates on 'project overview', 'show project X', or similar queries.