jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity
32 Commits 2 Branches 0 Tags 3.1 MiB
Python 57.4%
Ruby 33.6%
Shell 8.2%
JavaScript 0.8%
Go to file
jared 98f8290631 Refine memory-project onboarding: type-based exclude taxonomy + 16k-context model 
Assessment now reasons about ignorable content by category (fetched
deps, build output, caches, tooling/AI-assistant dirs, lockfiles, bulk
data, binaries) so it generalizes across stacks. Onboarding switches to
the config.yaml model qwen25-coder-7b-16k: inference is GPU-bound at
~65 tok/s, so the speed lever is fewer chunks per doc via a larger
context window (GRAPHIFY_OLLAMA_NUM_CTX does not propagate through the
OpenAI-compatible path; context must come from the modelfile). Extends
ADR-017.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 		2026-06-17 10:57:06 -04:00
docs Refine memory-project onboarding: type-based exclude taxonomy + 16k-context model 2026-06-17 10:57:06 -04:00
openspec Source memory plugin in git; port hooks to Python; archive change 2026-06-12 12:42:05 -04:00
plugins/memory Refine memory-project onboarding: type-based exclude taxonomy + 16k-context model 2026-06-17 10:57:06 -04:00
.gitignore Complete memory plugin implementation — hooks, skills, and graph-connectivity findings 2026-06-05 16:39:49 -04:00
CLAUDE.md Refine memory-project onboarding: type-based exclude taxonomy + 16k-context model 2026-06-17 10:57:06 -04:00
README.md Archive memsearch-episodic-layer change 2026-06-09 14:35:50 -04:00
graphify-interview Add Graphify setup & best-practices guide (11 docs + research) 2026-06-03 16:45:07 -04:00
memory-systems-compared060326 Add Graphify setup & best-practices guide (11 docs + research) 2026-06-03 16:45:07 -04:00

README.md

cc-os — Cross-Project Memory for Claude Code

A personal memory system for Claude Code, designed for a multi-client freelancer. The system captures knowledge across projects and surfaces it automatically at the start of each Claude Code session.

Status

The memory plugin is live and working. Design documentation lives in docs/. Both episodic memory (memsearch) and semantic/knowledge memory (Graphify + Obsidian vault) are active.

What it does for you

  • Injects vault context at session start — Claude sees your SecondBrain graph summary, your conventions, and today's journal path before you type the first message.
  • Surfaces project structure on demand — run one command to build a graph of any project; Claude can then query it for patterns, architecture, and conventions.
  • Remembers conventions automatically — memory-write stores evergreen knowledge (coding patterns, client rules, recurring decisions) in the correct vault location with proper tags.
  • Stays fresh without a daemon — the vault graph rebuilds in the background when stale; vault writes immediately invalidate the timestamp so the next session picks up changes.
  • Keeps project repos clean — all indexes are build artifacts (graphify-out/); nothing is committed to project repos.

User guide

See docs/USER-GUIDE.md for setup, onboarding new projects, using the skills, and known limitations.

Directory layout

Path Contents
docs/memory-system/ Architecture, ADRs, build plan, Graphify evaluation
docs/graphify/ Verified Graphify command handbook
docs/USER-GUIDE.md Practical usage guide
openspec/ Spec-driven change management (changes, specs)
graphify-interview, memory-systems-compared060326 Raw source transcripts (do not cite as fact)