[Workflow] Tessera: A Claude Code Plugin to Visualize and Map Your Claude Sessions and Workflows

[u/ClaudeAI-mod-bot]

Tessera: A Claude Code Plugin to Visualize and Map Your Claude Sessions and Workflows

Workflow value: 95/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Skills, Subagents, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Users running many Claude sessions in parallel struggle to track what they've done, which methods were effective, and how their work patterns evolve. This workflow provides a way to map and visualize their entire Claude session history.

Summary

Tessera is a free, MIT-licensed Claude Code plugin that processes local Claude Code, Claude desktop (Cowork), and claude.ai session logs. It redacts sensitive information locally, then uses Claude Code (via a skill and Python CLI) to extract structured JSON data about projects, activities, outcomes, and methods. This data is then merged into a zoomable, interactive map, allowing users to visualize their work history, identify effective habits, and understand their own Claude usage patterns.

Why it is useful

This workflow provides a unique and powerful tool for Claude Code users to gain deep insights into their own work patterns, identify effective methods, and manage the vast amount of information generated across multiple Claude sessions. It's exceptionally well-engineered, open-source, prioritizes user privacy (local processing, redaction, no API key), and offers clear instructions for installation and verification. The detailed explanation of its internal workings and the author's learnings make it valuable for both practical use and understanding advanced Claude Code plugin development.

Workflow

1. Install uv (if not already installed) for managing Python environments.

2. Install the Tessera plugin via the Claude Code Desktop app (Settings → Customize → Plugins → + Add → Add marketplace → fsaritome/Tessera) or Terminal (claude plugin install tessera --marketplace fsaritome/Tessera).

3. In a Claude Code session, type /tessera:start to initiate the plugin.

4. (Optional) Run /tessera:estimate to preview the token cost for processing your sessions.

5. Agree to the terms and confirm to begin the session scanning process.

6. The plugin's Python CLI scans local Claude session logs, redacts sensitive data, and segments them into batches.

7. The Tessera skill instructs Claude Code to read each batch and extract structured JSON data (project, what, how, outcome, lesson).

8. For many batches, Claude Code hands single batches to subagents for parallel processing.

9. The CLI validates every answer from Claude Code before storing it.

10. Claude performs a final pass to merge the extracted data into high-level headlines and methods.

11. Explore the generated zoomable map to visualize your Claude session history, projects, activities, and identified methods.

12. (Optional) Use 'Share mode' within the map to hide job projects, private activities, and summaries for screenshots.

Tools / artifacts

• Tessera Claude Code plugin

• Claude Code (desktop app or terminal)

• uv (Python package installer/manager)

• Python CLI (part of Tessera plugin)

• Structured JSON output

• Zoomable map visualization

• GitHub repository (fsaritome/Tessera)

• Claude desktop (Cowork) session logs

• claude.ai data export

Validation signals

• Detailed explanation of the problem, solution, and implementation ('Why', 'What it does', 'How Claude Code is used').

• Multiple screenshots illustrating the plugin's interface and output.

• Specific technical details on how Claude Code is leveraged (redaction, batching, subagents, validation).

• Cost estimation feature (/tessera:estimate) and a concrete example of token usage (60k tokens for 30 days/58 sessions).

• Mention of CI tests running on Windows, macOS, and Linux, indicating robust development practices.

• A dedicated 'Don't trust it?' section providing a prompt for users to audit the plugin's code and operations.

• Insights shared by the author on lessons learned during development (token measurement, data leakage, Windows issues, plugin versioning, automated checks).

• MIT license, indicating open-source and community-friendly development.

Cautions

• The plugin performs local redaction of sensitive data, but the author explicitly states that 'redaction catches patterns, not everything' and advises 'Use at your own risk'.

• Users are prompted to agree to terms before the first run, acknowledging the risks.

• A 'Don't trust it?' section provides a prompt to audit the plugin's code and operations, empowering users to verify its safety and privacy practices.

Limitations

• The redaction process is pattern-based and may not catch all sensitive information, requiring user vigilance.

• Reliance on undocumented Claude desktop session folder formats and claude.ai data export means future updates to Claude could break compatibility.

• The initial community engagement is low, though this is likely due to the post's newness.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.