By verrio1
A programming language for AI sessions - structures English into unambiguous control flow for multi-agent orchestration
OpenProse is a programming language for AI sessions. Activate on ANY `prose` command (prose boot, prose run, prose compile, prose update, etc.), running .prose files, mentioning OpenProse/Prose, or orchestrating multi-agent workflows. The skill intelligently interprets what the user wants.
A shell for the web. Navigate URLs like directories, query pages with Unix-like commands. Activate on `websh` command, shell-style web navigation, or when treating URLs as a filesystem.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A long-running AI session is a Turing-complete computer. OpenProse is a programming language for it.
Website • Language Spec • Examples
⚠️ Beta Software — Read before using
# Research and write workflow
agent researcher:
model: sonnet
skills: ["web-search"]
agent writer:
model: opus
parallel:
research = session: researcher
prompt: "Research quantum computing breakthroughs"
competitive = session: researcher
prompt: "Analyze competitor landscape"
loop until **the draft meets publication standards** (max: 3):
session: writer
prompt: "Write and refine the article"
context: { research, competitive }
claude plugin marketplace add openprose/prose
claude plugin install open-prose@prose
Then launch Claude Code and try:
"run example prose program and teach me how it works"
git clone https://github.com/openprose/prose.git ~/.config/opencode/skill/open-prose
Then launch OpenCode and try:
"run example prose program and teach me how it works"
git clone https://github.com/openprose/prose.git ~/.config/agents/skills/open-prose
Then launch Amp and try:
"run example prose program and teach me how it works"
By installing, you agree to the Privacy Policy and Terms of Service.
Traditional orchestration requires explicit coordination code. OpenProse inverts this—you declare agents and control flow, and an AI session wires them up. The session is the IoC container.
Other frameworks orchestrate agents from outside. OpenProse runs inside the agent session—the session itself is both interpreter and runtime. It doesn't just match names; it understands context and intent.
**...**)When you need AI judgment instead of strict execution, break out of structure:
loop until **the code is production ready**:
session "Review and improve"
The **...** syntax lets you speak directly to the OpenProse VM. It evaluates this semantically—deciding what "production ready" means based on context.
OpenProse runs on any Prose Complete system—a model + harness combination capable of inducing the VM. Currently: Claude Code + Opus, OpenCode + Opus, Amp + Opus. It's not a library you're locked into—it's a language specification.
Switch platforms anytime. Your .prose files work everywhere.
Why not just plain English? You can—that's what **...** is for. But complex workflows need unambiguous structure for control flow. The AI shouldn't have to guess whether you want sequential or parallel execution.
Why not rigid frameworks? They're inflexible. OpenProse gives you structure where it matters (control flow, agent definitions) and natural language where you want flexibility (conditions, context passing).
Enable auto-updates (recommended):
/plugin → Marketplaces → prose → Enable auto-update
Or update manually:
claude plugin update open-prose@prose
cd ~/.config/opencode/skill/open-prose && git pull
cd ~/.config/agents/skills/open-prose && git pull
| Feature | Example |
|---|---|
| Agents | agent researcher: model: sonnet |
| Sessions | session "prompt" or session: agent |
| Persistent Agents | agent captain: persist: true / resume: captain |
| Parallel | parallel: blocks with join strategies |
| Variables | let x = session "..." |
| Context | context: [a, b] or context: { a, b } |
| Fixed Loops | repeat 3: and for item in items: |
| Unbounded Loops | loop until **condition**: |
| Error Handling | try/catch/finally, retry |
| Pipelines | items | map: session "..." |
| Conditionals | if **condition**: / choice **criteria**: |
See the Language Reference for complete documentation.
The examples/ directory contains 37 example programs:
npx claudepluginhub verrio1/prose --plugin webshHarness-native ECC plugin for engineering teams - 67 agents, 278 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Matt Pocock's agent skills for real engineering — grilling, spec/ticket flows, TDD, code review, domain modelling and more. Plug-and-play, not vibe coding.
Consult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, plus codex, antigravity, and grok CLIs when installed) to get diverse perspectives on coding problems
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review