OMP — Oh My Pi Agent Harness

Oh My Pi (OMP) is the coding harness that AI agents operate within on this server. It provides structured access to the filesystem, tools, sub-agents, and external services.

Core Tools

ToolPurposeWhen to use
readRead files, dirs, archives, URLs, SQLite, images, docsAlways for file inspection
writeCreate or overwrite filesNew files
editSurgical line-based edits with snapshot tagsModifying existing files
bashTerminal: git, builds, tests, package managersCompute, not content reads
searchRegex search across filesContent lookup
findFast glob-based file discoveryStructure mapping
lspLanguage Server Protocol: definitions, refs, renameCode intelligence
ast_grep / ast_editStructural AST search and rewriteCodemods
browserHeadless Chromium via PuppeteerJS-dependent pages, UI testing
evalPersistent Python/JS kernelsQuick compute, data processing
taskSpawn parallel sub-agentsDecompose complex work
ircMessage other agentsCoordination
web_searchSearch the webExternal information
debugDAP debugger (gdb, lldb, debugpy, dlv)Step-through debugging
todoPhased task managementMulti-step work tracking

Agent Types

AgentCapabilitiesUse case
taskFull tools (read, write, bash, edit, etc.)General multi-step work
exploreREAD-ONLY (no write/exec)Codebase investigation
planArchitecture planningComplex multi-file design
oracleSenior engineer consultationDebugging, architecture
designerUI/UX specialistVisual implementation
reviewerCode reviewQuality/security analysis
librarianLibrary researchExternal API investigation
quick_taskMinimal reasoning, full toolsMechanical updates only

Internal URIs

URIResolves to
skill://<name>Skill instructions
rule://<name>Rule details
agent://<id>Agent output artifact
artifact://<id>Full output (long results)
history://<id>Agent transcript
local://<name>.mdShared content with sub-agents
memory://rootPersistent memory
mcp://<uri>MCP resource
issue://<N>GitHub issue
pr://<N>GitHub PR
omp://Harness documentation

Key Conventions

  • Snapshot tags: Every read returns a [PATH#TAG] header. Edits require the current tag — stale tags are rejected.
  • No shell for reads: cat, grep, ls, find are intercepted. Use read, search, find tools instead.
  • Parallel by default: Independent work should be parallelized via task sub-agents.
  • Verify before yield: Non-trivial changes must be tested before declaring done.

TYPO3 MCP Integration

The test instance (test.freundeskreis.family) runs hn/typo3-mcp-server v0.2.0 exposing 8 tools:

ToolPurpose
GetPageTreePage hierarchy
GetPageSingle page data
ListTablesAvailable DB tables
GetTableSchemaTable structure
ReadTableQuery table data
WriteTableCreate/update records (workspace-safe)
SearchFull-text content search
GetFlexFormSchemaFlexForm field definitions

All writes go through DataHandler into a TYPO3 workspace — never direct to live tables.

For the full integration matrix showing how TYPO3 MCP connects with other tools, see Skills & Integrations.

See also