OMA

OMA is a standalone multi-agent runtime for terminal-first coding workflows. It provides a native CLI/TUI experience, an embedded agent hierarchy, durable workspace state under .oma/, and a large local tool surface.

• Turkish README: README.tr.md
• Schema: schemas/oma.schema.json
• Config template: templates/oma.jsonc

What ships

• Native app entrypoint: apps/oma/src/main.ts
• Shared CLI surface helpers: packages/cli/src/
• Ink TUI surface: packages/tui/src/
• Runtime kernel: packages/kernel/src/
• Embedded agents: src/agents/
• Embedded tools: src/tools/
• Durable workspace state: .oma/

Public command surface

V2 Public Stable Commands

Command	Agent	Purpose
/plan	cto	Create an implementation-ready plan
/implement	cto	Execute an implementation-ready task
/validate	cto	Run the smallest sufficient validation scope
/roadmap	cto	Create or revise roadmap-scale plans
/roadmap-status	cto	Summarize current roadmap progress
/roadmap-continue	cto	Continue roadmap execution from current phase

V2 Redesign Candidate Commands

Command	Agent	Purpose
/review	cto	Findings-first review of plan, diff, or workspace
/status	cto	Summarize current repo, plan, validation status
/analyze	cto	Repository, architecture, or target-area investigation

V2 Advanced Commands

Command	Agent	Purpose
/brainstorm	brainstorm	Structured ideation and contradiction finding
/prompt	cto	Turn brainstorm output into a refined prompt artifact
/loop	cto	Execute roadmap items through plan → implement → validate

Quick start

1) Install

bun install

2) Create config

Use one of the canonical config paths:

• ~/.config/oma/oma.jsonc
• .oma/oma.jsonc

Start from the bundled template:

mkdir -p .oma
cp templates/oma.jsonc .oma/oma.jsonc

3) Run the native surface

bun run apps/oma/src/main.ts --help
bun run apps/oma/src/main.ts --version
bun run apps/oma/src/main.ts
bun run apps/oma/src/main.ts plan "Add a multiply function to src/math.ts"

• No arguments launches the native Ink TUI.
• Slash commands such as /plan, /implement, and /validate can be run inside the TUI.
• One-shot commands reuse the same command surface as the TUI.

When a one-shot command creates a new conversation, the CLI prints the session id:

[OMA] Session: <session-id>

You can continue a persisted session with:

bun run apps/oma/src/main.ts --session <session-id> implement
bun run apps/oma/src/main.ts --session <session-id> validate

List the embedded agent hierarchy when needed:

bun run apps/oma/src/main.ts --agents

Config overview

OMA reads JSONC config with this precedence:

1. ~/.config/oma/oma.jsonc
2. .oma/oma.jsonc

Project-local config overrides global config.

Key sections:

• agent
• workflow
• memory
• github
• mcp.context7
• disabledTools
• commandSurface

Minimal example:

{
  "$schema": "https://oma.local/schemas/oma.schema.json",
  "version": 2,
  "workflow": {
    "hookProfile": "standard",
  },
}

Workspace storage

OMA persists workspace state under .oma/:

• Plans: .oma/plans/
• Roadmap: .oma/roadmap/
• Prompts: .oma/prompts/
• Background tasks: .oma/tasks/
• Sessions: .oma/sessions/

Validation

mise run build
mise run lint
mise run typecheck
mise run test

Optional live E2E:

OMA_E2E=true bun test ./test/e2e/oma-workflow.e2e.ts

Docs

• Getting started
• Architecture
• Commands
• Configuration
• ADR-008: Config schema v2
• CHANGELOG