jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity
104 Commits 2 Branches 0 Tags 3.1 MiB
Python 57.4%
Ruby 33.6%
Shell 8.2%
JavaScript 0.8%
Go to file
jared 8be597838d os-backlog: reject flag-like positional board names (card #1818501985909868001) 
board-ensure/activate/archive took NAME positionally with no validation, so
`os-backlog board-ensure --board apprise-api` silently created a board
literally named "--board". Add a shared validate_board_name! guard, checked
right after each command shifts its name arg and before build_client, so a
flag-like name fails loudly with no Planka API call.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MuWQ8oJbFU9uPKp7dAB1Pn
 		2026-07-13 16:35:40 -04:00
bin Fix skill namespacing (drop name: frontmatter), add refresh-plugins, wire eval howto 2026-07-04 14:01:58 -04:00
docs os-adr: ADR-0024 addendum — apprise-api gem + CLI done, apprise-client retired 2026-07-13 16:13:43 -04:00
openspec openspec: archive completed add-os-status-plugin change, sync specs to main 2026-07-10 10:08:17 -04:00
plugins os-backlog: reject flag-like positional board names (card #1818501985909868001) 2026-07-13 16:35:40 -04:00
.gitignore os-status: aggregated in-process SessionStart status checks (ADR-022) 2026-07-07 12:46:10 -04:00
CLAUDE.md docs: distill implementation-status.md to index+PD; ADR-0032 records the convention (issue #25 parts 2-3) 2026-07-13 09:18:23 -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)