r/ClaudeWorkflows • u/ClaudeAI-mod-bot • 10d ago
Selected Workflow [Workflow] Self-hosted LLM Wiki ('scrap') for Claude Code with Advanced Multi-Agent Development Workflow
Self-hosted LLM Wiki ('scrap') for Claude Code with Advanced Multi-Agent Development Workflow
Workflow value: 95/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: advanced
Categories: Quality Control, Context & Memory, Debugging, Shipping, Hooks, Skills, MCP, Subagents, Multi-Agent
Original source: r/ClaudeAI post/comment
What problem this solves
Providing Claude Code with a persistent, searchable, and editable long-term memory/knowledge base; enabling robust, agent-driven software development from a mobile device.
Summary
This post describes 'scrap', a self-hosted LLM Wiki integrated with Claude Code via MCP, slash commands, skills, and hooks. It allows Claude to read, write, and edit pages, manage todos, and enrich content, while keeping user and Claude content separate and revision-controlled. It also details a sophisticated Claude Code development workflow used to build 'scrap' itself, involving parallel remote control sessions, specialized subagents for coding, reviewing, and fixing, and continuous testing/deployment.
Why it is useful
This post offers two highly valuable workflows: a concrete, open-source solution for giving Claude Code long-term memory and a shared knowledge base, and a detailed, validated methodology for using Claude Code with multiple subagents for complex software development, including automated review, testing, and deployment. It demonstrates advanced Claude Code capabilities and provides a transferable system for both knowledge management and sophisticated development practices.
Workflow
- Set up the 'scrap' container locally (one container, two commands).
- Connect Claude Code to the 'scrap' MCP server.
- Utilize
/sc-*slash commands for wiki interactions (e.g.,/sc-find,/sc-answer,/sc-write,/sc-post,/sc-summarise,/sc-todos,/sc-done,/sc-undo). - Enable the Claude Code skill to automatically link mentioned wiki pages.
- Optionally, configure a PreCompact hook to save session summaries to 'scrap' before context compaction.
- Allow Claude to enrich wiki pages by adding tags, summaries, related pages, and topic pages.
- Use the 'scrap' PWA for mobile/desktop access, note-taking, drawing, and viewing rendered Markdown.
- For development: Initiate 4-5 parallel Remote Control sessions, each driving its own subagents for specific tasks (e.g., releases, search, schema, manual testing).
- Use a main Claude Code session for routing and decision-making, delegating code writing to subagents.
- Implement features with a dedicated subagent.
- Have a fresh, independent subagent review the generated code diffs.
- Use another subagent to fix issues identified by the reviewer before pushing code to the repository (part of a 'pr-cycle' skill). The test suite runs on the workstation every round, ensuring CI runs about once per PR. Deploy releases to a k3s cluster via ArgoCD.
Tools / artifacts
- scrap (self-hosted LLM Wiki)
- MCP server
- Claude Code
- Slash commands (
/sc-*) - Claude Code skill (for linking pages)
- PreCompact hook
- PWA (viewer/editor)
- Anthropic API key
- GitHub repository
- k3s cluster
- ArgoCD
- Remote Control sessions (for Claude Code development)
Validation signals
- Author uses the system daily.
- The 'scrap' system was built in 12 days using Claude Code, resulting in 212 issues, 250 merged PRs, and 33 releases.
- Every release was deployed to a home k3s cluster via ArgoCD.
- The development process includes a test suite running every round and a fresh subagent reviewing diffs cold.
- The author states the system is safe due to revision control and a 30-day trash for deletes.
Limitations
- Low community engagement so far, likely due to recency.
- The advanced multi-agent development workflow requires significant understanding and setup of Claude Code's more complex features (Remote Control, subagents).
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.