Each coding agent session starts blank: the business rules, design system and conventions the user explained, and what the last session learned, are gone.
Omoikane is a template every new software system starts from.
Its agents keep a wiki of that knowledge on their own, from what the user states while building, without asking the user to write anything down.
Every system also starts with the development skills.
/omoikane-mode routes each task (feature, bug, refactor, security audit) to a playbook, the skills it needs and the principles that apply.
Named after 思金神 (Omoikane), the kami who gathers the thoughts of the other gods and returns a synthesis. Built on Karpathy's LLM Wiki pattern, with brainmaxxing, ai-memory, pstack and Cloudflare's security-audit-skill with its post Build your own vulnerability harness as references. Omoikane's addition: coding sessions are a source too.
Clone this repository as the root of a new software system and run python omoikane/bin/new-system.py (Setup, below). Code lives at the root; omoikane/ is its memory. Every coding session that edits files is captured on stop and distilled into decision and gotcha pages, and every new session starts with the wiki index in context. Documents the system's domain comes from (specs, business rules, design-system docs) go into the inbox and through /ingest.
Omoikane is for software development, not generic research (#111).
- A source arrives in
omoikane/raw/inbox/: a clipped article, a synced file, or a coding session written there by theStophook (omoikane/bin/session-capture.py, no LLM). - At the end of the day the user runs
/wrap-up [days]in a fresh session: the agent runs/distillon each captured session and/ingeston each other source, moves each file toomoikane/raw/sources/, and reads the commits of the period for what no session covered. Nothing runs in the background. Optionally,omoikane/bin/wiki-ingest.ps1does the inbox part headless on a schedule (install-schedule.ps1). - The agent writes and updates pages under
omoikane/wiki/, appends toomoikane/log.md, and leaves anything it could not decide inomoikane/_review.md. wiki-index.pyregeneratesomoikane/index.mdfrom page frontmatter.wiki-lint.pychecks links, orphans, frontmatter andcode:paths without an LLM.- The
SessionStarthook (omoikane/bin/session-context.py) injects the index into every new session, domain rules, decisions and gotchas first, plus any captured session not yet distilled. You read the wiki in Obsidian (vault:omoikane/), answer_review.md, and ask questions with/ask.
| Task | Claude Code | OpenCode |
|---|---|---|
| Route a software task to a playbook, its skills and principles; holds for the session | /omoikane-mode |
same |
| Ingest one source | /ingest omoikane/raw/inbox/<file> |
same |
| Distill one captured session | /distill omoikane/raw/inbox/sessions/<file> |
same |
| Ask the wiki | /ask <question> |
same |
| Semantic health check | /lint |
same |
| Mark stale, redundant, low-value pages; merge duplicates | /prune |
same |
| Practices across sessions (also every 5 distills, headless) | /synthesize [n sessions] |
same |
| End of day: inbox, recent commits, synthesize when due | /wrap-up [days] |
same |
| Process everything in inbox (headless) | omoikane/bin/wiki-ingest.ps1 |
omoikane/bin/wiki-ingest.ps1 -Agent opencode |
| Structural checks (no LLM) | python omoikane/bin/wiki-lint.py |
same |
Score a headless distill of the fixtures, before changing distill.md |
python omoikane/bin/distill-fidelity.py score <omoikane-dir> tests/fixtures/distill-*.md |
same |
Promote rules ticked in _review.md into AGENTS.md |
python omoikane/bin/wiki-rules.py |
same |
| Measure what every session loads | python omoikane/bin/context-budget.py |
same |
| Rebuild index | python omoikane/bin/wiki-index.py |
same |
| Start a new system from a fresh clone | python omoikane/bin/new-system.py |
same |
| Take the template's later fixes, keeping the system's memory | python omoikane/bin/update-from-template.py |
same |
| Seed the inbox from an existing project's docs, rule files and history | python omoikane/bin/bootstrap.py [--from <path>] |
same |
| Tests | python -m unittest discover -s tests |
same |
Both agents run the same prompt files in omoikane/prompts/; the skill and command folders are thin wrappers.
Pi runs the same skills as /skill:<name>: .pi/settings.json points it at .claude/skills/.
Every skill under .claude/skills/ taken from another project is listed in omoikane/skills.md, with its upstream, commit, licence and what Omoikane changed; each keeps its upstream LICENSE in its own folder. Omoikane itself is MIT (LICENSE).
A personal skill of the same name in ~/.claude/skills/<name>/ wins over the project's copy in Claude Code, and OpenCode reads both folders; remove the personal copy to run the template's there. Pi does not read ~/.claude/skills/ and keeps the project's copy.
The two scripts are harness-independent; each harness registers them its own way, and the registration is committed in the repository.
| Harness | Registration | Index at start | Capture on stop |
|---|---|---|---|
| Claude Code | .claude/settings.json |
SessionStart |
Stop, SessionEnd |
| Pi | .pi/extensions/omoikane.ts |
before_agent_start (system prompt) |
agent_end, session_shutdown |
| OpenCode | .opencode/plugins/omoikane.ts |
experimental.chat.system.transform |
session.idle, plugin dispose |
Pi loads a project extension only after you trust the project (pi asks once; headless runs need --approve or defaultProjectTrust).
OpenCode installs @opencode-ai/plugin into .opencode/ on first start and ignores those files itself.
Manual capture from a saved session: python omoikane/bin/session-capture.py --harness pi --transcript <file>.jsonl, or opencode export <id> > s.json then --harness opencode --transcript s.json.
git clone <repo> my-project
cd my-project
python -m unittest discover -s tests # sanity check
python omoikane/bin/new-system.py # empty the template's own memory; then commit
# --from <another system>: keep its conventions and design-system rules
git remote add origin <new-system-url> # the script renamed the template's remote to `template`
omoikane/bin/install-schedule.ps1 # optional, instead of /wrap-up: Task Scheduler job every 30 minnew-system.py removes the wiki, log entries, review items and captures the template carries about its own development, which the brief would otherwise inject into every session of the new system. It refuses a tree with uncommitted changes and commits nothing, so git restore . undoes it. It also renames origin to template: the scheduled run publishes to origin, and the new system's pages must not reach the template. It moves the template's MIT LICENSE to omoikane/LICENSE, where it covers Omoikane's files; the root licence is the new system's to choose. docs/specs/ holds the template's own plans; delete it or keep it as history.
update-from-template.py merges template/main into the system without committing and keeps the wiki, captures, log, review queue and rules block as the system has them; read git diff --cached, then commit. A system made before the script existed first takes it with git fetch template, git checkout template/main -- omoikane/bin/update-from-template.py omoikane/bin/wikilib.py omoikane/bin/wiki-index.py and a commit.
Requirements: Python 3.11+, claude or opencode on PATH for headless runs (wiki-ingest.ps1); interactive pi sessions run the skills as /skill:<name>, git.
Architecture, conventions and the reasoning behind them: docs/architecture.md. The agent's own operating manual: AGENTS.md.