opencode-gladio
v0.5.4
Published
Disciplined orchestration plugin for OpenCode. Automatic 4-tier workflow pipeline, dual review, pipeline integrity hooks, and persistent project memory.
Downloads
103
Maintainers
Readme
opencode-gladio
Disciplined orchestration plugin for OpenCode
Eleven specialists. Forced 4-tier delivery pipeline. Persistent project memory.
Why Gladio
Most OpenCode setups optimize for flexibility.
Gladio optimizes for discipline:
- ambiguity gets challenged before execution
- work is forced into a tiered pipeline
- risky changes get reviewed, verified, and repaired
- project learnings survive across sessions in
.gladio/
This is closer to a senior-engineer operating layer than a simple agent preset.
Quick Start
npx opencode-gladio@latest installOr install globally:
npm i -g opencode-gladio
opencode-gladio installAfter install, open OpenCode and start with your task. polat coordinates the rest.
Verify Your Setup
Inside OpenCode, run:
ping polatThen try a real task, or check the generated config:
opencode-gladio doctor
opencode-gladio config show --jsonThe Pipeline
User task
↓
ClarityGate
↓
Tier classification
↓
Forced worker chain
↓
Verification / review / repair
↓
DoneTier Matrix
| Tier | Trigger | Forced pipeline |
|------|---------|-----------------|
| 1 | Single-file trivial work | polat implements directly |
| 2 | Standard low-risk changes | memati -> halit |
| 3 | Risky or multi-file work | memati -> halit -> aslan-akbey + iskender -> tuncay if needed |
| 4 | Critical paths, data, production risk | Tier 3 + pala chaos testing |
What Makes Gladio Different
- ClarityGate: vague asks trigger focused questions before work starts
- Dual review: risky work gets both correctness and adversarial review
- Pipeline integrity hooks: phase reminders, retry nudges, todo continuation, patch rescue signals
- Persistent memory: Gladio stores high-value learnings in
.gladio/context.json - Project facts injection: languages, frameworks, package manager, and session context feed the coordinator
Persistent Project Memory
Gladio 0.5.0 adds repo-local persistent memory.
Generated files:
.gladio/context.json.gladio/pipeline-state.json.gladio/project.json
What they store:
context.json: saved learnings fromgladio-learnpipeline-state.json: last persisted session snapshotproject.json: detected project facts like package manager, languages, frameworks
These files are bootstrapped automatically when Gladio initializes for a project. pipeline-state.json may remain empty until a session actually runs.
Built-in tools:
gladio-learngladio-recall
CLI helpers:
opencode-gladio memory show
opencode-gladio memory show --json
opencode-gladio memory forget <id>
opencode-gladio memory resetThe installer also adds .gladio/ to .gitignore automatically.
Meet the Crew
Polat
Role: Orchestrator and final coordinator.
polat owns ClarityGate, tier routing, delegation, and final synthesis.
Çakır
Role: Execution lead.
cakir breaks larger asks into scoped tasks and routes specialists.
Memati
Role: Implementer.
memati makes the code changes and carries the main delivery path.
Abdülhey
Role: Researcher.
abdulhey digs through docs, APIs, evidence, and rationale.
Aslan Akbey
Role: Correctness reviewer.
aslan-akbey checks maintainability, logic, and production safety.
İskender
Role: Adversarial reviewer.
iskender looks for edge cases, misuse, security gaps, and race conditions.
Tuncay
Role: Repair specialist.
tuncay performs scoped repairs after review failures.
Halit
Role: Verifier.
halit runs the build-test gate and reports pass/fail clearly.
Güllü Erhan
Role: Frontend specialist.
gullu-erhan handles UI quality, layout polish, and implementation aesthetics.
Laz Ziya
Role: Explorer.
laz-ziya rapidly maps the repo and finds the right files and patterns.
Pala
Role: Chaos tester.
pala pressure-tests critical flows with hostile or abnormal scenarios.
CLI
opencode-gladio install
opencode-gladio fresh-install
opencode-gladio uninstall
opencode-gladio doctor
opencode-gladio config show --json
opencode-gladio memory show --json
opencode-gladio memory forget <id>
opencode-gladio memory reset
opencode-gladio print-configConfiguration
Global config path:
~/.config/opencode/opencode-gladio.jsoncProject-local memory is controlled through the memory block:
{
"$schema": "https://unpkg.com/opencode-gladio@latest/opencode-gladio.schema.json",
"schema_version": 2,
"memory": {
"enabled": true,
"dir": ".gladio",
"max_learnings": 100,
"inject_summary": true
}
}Useful config areas:
{
"ui": {
"worker_visibility": "visible"
},
"hooks": {
"profile": "standard",
"phase_reminder": true,
"todo_continuation": true,
"apply_patch_rescue": true,
"json_error_recovery": true,
"delegate_retry": true,
"chat_headers": true
},
"fallbacks": {
"enabled": true,
"chains": {
"polat": ["zai/glm-5.1", "openai/gpt-5.4"],
"halit": ["opencode-go/kimi-k2.5", "zai/glm-5.1"]
}
}
}Architecture
src/
├── index.ts # Plugin entry
├── agents.ts # 11 agent definitions
├── config.ts # Config schema, defaults, merging
├── cli.ts # Installer + memory CLI
├── installer.ts # OpenCode install wiring
├── doctor.ts # Health diagnostics
├── tier-router.ts # 4-tier classification helpers
├── fallback-manager.ts # Runtime model fallback
├── fallbacks.ts # Startup fallback resolution
├── mcp.ts # Remote MCP registration
├── project-facts.ts # Language/framework detection
├── memory/
│ └── index.ts # Persistent memory store
├── tools/
│ └── index.ts # gladio-learn / gladio-recall
├── prompts/
│ ├── coordinator.ts
│ ├── workers.ts
│ └── layers.ts
├── hooks/
│ ├── session-start.ts
│ ├── system-prompt.ts
│ ├── pre-tool-use.ts
│ ├── post-tool-use.ts
│ ├── phase-reminder.ts
│ ├── todo-continuation.ts
│ ├── apply-patch.ts
│ ├── json-error-recovery.ts
│ ├── delegate-task-retry.ts
│ ├── filter-available-skills.ts
│ ├── chat-headers.ts
│ ├── stop.ts
│ ├── session-end.ts
│ ├── runtime.ts
│ └── sdk.ts
└── __tests__/ # Unit testsDevelopment
git clone https://github.com/beydemirfurkan/opencode-gladio.git
cd opencode-gladio
bun install
bunx tsc --noEmit
bun test
bun run buildLicense
MIT
