Keep project decisions, debugging notes, and session discoveries in a lasting Markdown wiki. Organize pages with tags and categories, connect related notes with links, and retrieve information through keyword searches.
Persistent markdown project wiki stored under repository omx_wiki with keyword search and lifecycle capture
Review the instructions the agent will receive before you install.
Persistent, self-maintained markdown knowledge base for project and session knowledge.
omx wiki wiki_ingest --input '{"title":"Auth Architecture","content":"...","tags":["auth","architecture"],"category":"architecture"}' --json
omx wiki wiki_query --input '{"query":"authentication","tags":["auth"],"category":"architecture"}' --json
omx wiki wiki_lint --json
omx wiki wiki_add --input '{"title":"Page Title","content":"...","tags":["tag1"],"category":"decision"}' --json
omx wiki wiki_list --json
omx wiki wiki_read --input '{"page":"auth-architecture"}' --json
omx wiki wiki_delete --input '{"page":"outdated-page"}' --json
omx wiki wiki_refresh --json
architecture, decision, pattern, debugging, environment, session-log, reference, convention
omx_wiki/*.mdomx_wiki/index.mdomx_wiki/log.mdUse [[page-name]] wiki-link syntax to create cross-references between pages.
At session end, discoveries can be captured as session-log-* pages. Configure via wiki.autoCapture in .omx-config.json.
omx_wiki/; legacy .omx/wiki/ is read-only compatibility input when no canonical wiki existsNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Clean up working code by identifying duplication, dead code, unnecessary layers, and error paths that hide failures. Preserve behavior with targeted tests, simplify the requested files in stages, and report verification results and remaining risks.
Investigate repository behavior, architecture, or possible causes without changing files. Trace relevant code and supporting material, then rank explanations by evidence and confidence, with concrete file references and clear distinctions between observations, conclusions, and unresolved questions.
Ask Claude or Gemini through a locally installed command-line tool for focused questions, reviews, brainstorming, or second opinions. Save the prompt, original response, summary, and next steps in a reusable Markdown file.
Take an idea or issue through requirements clarification, reviewed planning, implementation, and verification. Supervise all stages in one recoverable OMX workflow, preserving artifacts and progress so work can resume or return to planning when findings require changes.
Run a persistent research workflow with a defined goal and explicit acceptance checks. It saves progress and finishes only when a recorded result passes either a validation script or an architect review of the research output.
Find the replacement for a research command removed in OMX 0.21. This migration notice directs existing autoresearch-goal usage to $autoresearch, the canonical research loop that requires validation before proceeding.