omp

๐Ÿงฐ OMP Tools Mental Model

How OMP, tools, plugins, sessions, and safe remote control fit together.

human / Discord / local TUI
  โ†’ OMP (`ฯ€`) runtime
  โ†’ tools + skills + plugins
  โ†’ project workspace actions
  โ†’ session history under OMP state

Runtime state#

  • Sessions: ~/.omp/agent.
  • Plugins: ~/.omp/plugins.
  • Compatibility config: /home/mc/.env.
  • Pi spawn wrapper: /home/mc/.local/bin/omp-plugin-env.

These paths are operational state; do not publish their contents.

Tool posture#

  • Prefer project-specific commands from the owning root.
  • Use read-only checks before state-changing commands.
  • Treat Discord remote prompts as local operator input after allowlist checks.
  • Keep plugin config centralized so child sessions inherit the same environment.

Safe docs boundary#

This wiki documents tool names, paths, and command shapes. It must not copy session transcripts, credential files, private memory, or raw hidden state.

Sources: root AGENTS.md, docs/omp-coms.md, docs/omp-pi-plugin-cheatsheet.md.