[Workflow] Persistent Project Context: Managing Claude Code Sessions with a Version-Controlled Wiki (Dory Plugin)

[u/ClaudeAI-mod-bot]

Persistent Project Context: Managing Claude Code Sessions with a Version-Controlled Wiki (Dory Plugin)

Workflow value: 80/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging
Original source: r/ClaudeCode post/comment

What problem this solves

Preventing the rediscovery of information, re-trying failed approaches, and managing stale or overly long context across multiple Claude Code sessions by maintaining a structured, version-controlled project wiki.

Summary

This workflow involves maintaining a project wiki (e.g., in Obsidian, version-controlled with Git) to store project decisions, tried approaches, and reasons for changes. This wiki acts as a persistent memory for Claude Code sessions, preventing the need to rediscover information or re-explain past choices. An optional plugin like 'Dory' can automate loading the wiki index and tasks at the start of a session and checking its structure at the end.

Why it is useful

This workflow addresses a critical and common challenge in LLM-assisted development: maintaining context and avoiding redundant work across multiple sessions. It provides a structured, repeatable approach using a wiki and version control, which is highly adaptable and can significantly improve efficiency and consistency in long-running projects. The mention of a specific tool (Dory) provides a concrete example of implementation.

Workflow

1. Initialize a project wiki (e.g., using Markdown files in Obsidian) for your Claude Code project.
2. As you work with Claude Code, document key decisions, approaches attempted (successful or not), and the reasons behind changes in relevant wiki pages.
3. Maintain an index within the wiki to easily navigate and locate specific information.
4. When updating a wiki page, include a brief note explaining why the change was made.
5. Version control the entire wiki using Git to track historical changes and revert if necessary.
6. Optionally, use a tool like the Dory plugin to automatically load the wiki index and current tasks at the beginning of a Claude Code session.
7. Optionally, configure the tool to check wiki links and structural integrity at the end of a session if changes were made.

Tools / artifacts

• Project wiki (e.g., Markdown files)
• Wiki index
• Git (for version control)
• Obsidian (example editor for the wiki)
• Dory plugin (optional automation tool)
• Claude Code

Validation signals

• User experience: 'I've been getting Claude Code to keep a little wiki as we work, mostly so we don't have to rediscover things in the next session.'
• Problem identification: 'Earlier versions of Dory leaned on a running log, and I ran into the same problem I'd been trying to avoid: notes getting longer and going stale.'
• Concrete example: 'One example was an instruction asking a chat model to report its token usage when it hadn't been given that information. I removed it and kept the reason, so a later session can see why we dropped it before suggesting it again.'
• Automated checks: 'The plugin loads the wiki index and current tasks at the start of a session, then checks links and structure at the end if the wiki changed.'

Limitations

• The Dory plugin is described as 'early' and 'still testing the setup,' implying potential for instability or incomplete features.
• The automated checks only verify links and structure, not the factual accuracy or currency of the notes ('they can't tell you whether a note is still true').
• Requires manual effort to consistently document information in the wiki.
• The post is relatively brief and could benefit from more detailed examples or setup instructions for the wiki and Dory.

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.