Installation Guide
Relevant source files
The following files were used as context for generating this wiki page:
The installation and initialization process in OhMyOpenCode centers on the "Prometheus" strategic planning system. Prometheus is responsible for transitioning a user's high-level request into a concrete, executable work plan stored in .sisyphus/plans/*.md. This guide details the initialization of project knowledge through hierarchical agent documentation and the specific workflow for generating these plans.
Sources: src/agents/prometheus/identity-constraints.ts:1-15, src/features/builtin-commands/templates/init-deep.ts:1-5
Project Initialization via /init-deep
Before an implementation agent can begin work, the environment must be initialized with structural project knowledge. The /init-deep command generates a hierarchical knowledge base consisting of AGENTS.md files at the root and complexity-scored subdirectories.
Initialization Workflow
The system follows a four-phase discovery and generation loop to ensure the agents have the necessary context for the specific codebase.
- Discovery & Analysis: Fires background exploration agents to predict standard patterns and identify entry points.
- Scoring & Decision: Evaluates directory complexity using a scoring matrix (file count, code ratio, symbol density).
- Generation: Writes the root
AGENTS.mdfollowed by parallel subdirectory generation. - Review: Deduplicates and trims content to ensure brevity and relevance.
Sources: src/features/builtin-commands/templates/init-deep.ts:15-35, src/features/builtin-commands/templates/init-deep.ts:130-150
Scoring Matrix for AGENTS.md Locations
| Factor | Weight | High Threshold | Source |
|---|---|---|---|
| File count | 3x | >20 | bash |
| Subdir count | 2x | >5 | bash |
| Code ratio | 2x | >70% | bash |
| Module boundary | 2x | Has index.ts / __init__.py | bash |
| Reference centrality | 3x | >20 refs | LSP |
Sources: src/features/builtin-commands/templates/init-deep.ts:135-155
The Prometheus Planning Lifecycle
Prometheus acts as a strategic consultant that converts requests like "fix X" or "build Y" into a structured work plan. It follows a strict "Planner, not Implementer" identity.
Phase 1: Interview and Grounding
Prometheus begins by classifying the intent (Trivial, Standard, or Architecture) to determine the depth of the interview. It performs "Silent Exploration" before asking the user any questions to resolve discoverable facts.
The "Clearance Check" ensures the core objective, scope, and technical approach are decided before proceeding.
Sources: src/agents/prometheus/gpt.ts:75-95, src/agents/prometheus/gpt.ts:140-160, src/agents/prometheus/identity-constraints.ts:85-105
Phase 2: Plan Generation & Metis Review
Upon passing the clearance check, the system registers a list of TODOs using TodoWrite and consults the Metis subagent for gap analysis.
- Metis Consultation: Identifies missed questions, guardrails, and scope creep risks.
- Incremental Write Protocol: To avoid token limits, Prometheus writes a plan skeleton first and then appends tasks in batches of 2-4.
Sources: src/agents/prometheus/plan-generation.ts:25-50, src/agents/prometheus/plan-generation.ts:75-95, src/agents/prometheus/identity-constraints.ts:145-165
Plan Verification via Momus
After a plan is generated to .sisyphus/plans/{name}.md, the system offers a "High Accuracy Review" loop using the Momus agent.
Verification Criteria
Momus evaluates the plan based on executability rather than perfection, focusing on:
- Reference Verification: Ensuring all referenced files and line numbers actually exist.
- Executability: Verifying each task has a clear starting point.
- QA Scenarios: Confirming every task has agent-executable test steps (e.g., Playwright, Bash, or Curl commands).
Configuration and Output Locations
Prometheus is strictly limited to Markdown output within specific directories to prevent unauthorized modifications to source code during the planning phase.
| Type | Path | Purpose |
|---|---|---|
| Drafts | .sisyphus/drafts/{name}.md | Temporary memory during interview phase. |
| Plans | .sisyphus/plans/{name}.md | Finalized, executable work plans. |
| Evidence | .sisyphus/evidence/task-{N}.ext | Captured output from verification scenarios. |
Sources: src/agents/prometheus/identity-constraints.ts:110-125, src/agents/prometheus/gpt.ts:230-245
Conclusion
The installation of a work environment in OhMyOpenCode requires both the physical documentation of the project via /init-deep and the strategic alignment provided by Prometheus. By enforcing a "Decision Complete" standard for plans and requiring Momus-verified QA scenarios, the system ensures that implementation agents (like Sisyphus) can execute work with zero human intervention.
Sources: src/agents/prometheus/gpt.ts:35-45, src/agents/momus.ts:180-190