jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity
99 Commits 2 Branches 0 Tags 3.1 MiB
Python 57.4%
Ruby 33.6%
Shell 8.2%
JavaScript 0.8%
Go to file
jared b0a21d6211 os-backlog: post-ship review corrections for the triage hook + project index (cards #1818330518584820864, #1818330528525321347) 
Codex review + verification pass over f9a81a1/3708c00 found the triage
hook resolving boards differently from the CLI. Corrections:
- Config#planka_board: tracker=planka:<board> now counts as board
  configuration everywhere (Resolver included), not just the explicit
  board key that config-write never writes.
- Triage hook board resolution extracted to pure
  TriageCheck.board_name_for honoring the umbrella rule: the session
  cwd's .cc-os/config overrides the git root's (the hook previously
  walked up and read only the root config).
- config-write keys the global project index by the realpath of the
  directory the config lands in, not the git toplevel — umbrella
  subprojects no longer overwrite the umbrella's row.
- projects <filter> matches name, tracker, or path; hook timeout
  8s->15s; CC_OS_DEBUG=1 surfaces swallowed hook errors on stderr.
Residual (name-only board lookup across all Planka projects) captured
as Backlog card #1818385174308586768. Suite 138/295/0.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VkeTPRWqaqJZEpf48H1aC7
 		2026-07-13 12:27:43 -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-backlog: post-ship review corrections for the triage hook + project index (cards #1818330518584820864, #1818330528525321347) 2026-07-13 12:27: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: post-ship review corrections for the triage hook + project index (cards #1818330518584820864, #1818330528525321347) 2026-07-13 12:27:43 -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)