OpenProse expresses multi-agent workflows as declarative contracts in Markdown, while the user's harness compiles and runs them.
2
Contracts can run as event-driven jobs triggered by schedules, webhooks, GitHub issues, or pull requests, with separate agents checking the result against the declared outcome.
3
A strong run can be pinned into a reusable workflow, allowing teams to start with an open-ended goal and later reduce cost and variation with more specific instructions.
Summary
Dan Barrett, Raymond Weitekamp, and Jose Montes de Oca present OpenProse as a way to write multi-agent workflows in plain Markdown. A contract describes the desired outcome, inputs, outputs, agents, skills, tools, and constraints. A coding harness such as Claude Code or Codex compiles and runs it, so OpenProse does not replace the harness. The team focuses on event-driven jobs rather than chat sessions. Schedules, webhooks, GitHub issues, and pull requests can trigger workflows such as a skeptical senior review of AI-generated code. Each run is checked against a contract by fresh sessions, which gives the workflow an external standard instead of relying on the same agent to approve its own work. The demos also cover a bank model-documentation workflow, where regulatory requirements become the contract. The speakers are candid that this approach fits repeatable, auditable work better than exploration, and that its flexible execution can produce different results across models.
Dan Barrett says the persistent problem is getting intent out of a person's head and into a capable system. OpenProse treats the desired end state as a contract. The author describes what must be true and leaves the harness to decide how to reach it. This differs from earlier prompt engineering, manual context engineering, and hand-built harnesses. Barrett argues that specifying the procedure too tightly can waste model capability and force an expensive model to do work that a cheaper model could handle. The contract can stay broad when the system is still exploring, then become more specific after a good run.
OpenProse is Markdown compiled by the user's harness
Raymond Weitekamp says the two facts to remember are that OpenProse is all text and that it runs event-driven multi-agent workflows. A program can declare sub-agents, skills, available tools, inputs, outputs, and required dependencies. For example, a workflow can require Exa for search and refuse to run if that skill or tool is unavailable. The compiler and runtime are also prompts. OpenProse is therefore a layer above existing harnesses rather than a replacement for Claude Code or Codex. The same Markdown program can be exported and used in another environment.
Weitekamp defines a job as a contract plus a trigger. The trigger can be a schedule, a webhook, a new GitHub issue, or a pull request. The hosted product currently makes webhooks and cron jobs available, with GitHub events wired directly. An issue workflow can take the issue as input and produce a commit. A pull-request workflow can run an adversarial review. This moves the system away from conversations and toward standing jobs that handle an event from start to finish.
A winning run can become a more deterministic workflow
When an open-ended contract produces a good result, the team can capture the agent trace and turn it into a reusable workflow. Dan Barrett describes this as pinning the how after initially declaring only the what. The result can shift from a flexible, expensive execution toward more specific and deterministic instructions, which can reduce the cost of later runs. Weitekamp adds that a golden session can be converted into a reusable workflow. He also warns that model behavior and user expectations change, so a pinned workflow is not automatically a permanently stable endpoint.
Separate review sessions check each run against the contract
The pull-request demo uses a 'grumpy senior developer who doesn't like AI-generated code' as the reviewer persona. New pull requests trigger review agents, and the development agent must respond to their feedback before its job is complete. Weitekamp describes runs with one review round and others with 14 rounds before the reviewers aligned and allowed the change to pass. Dan Barrett says the important distinction is that each fresh session is compared against a declarative contract. The workflow avoids asking the same model to create and approve its own work.
OpenProse fits repeatable, auditable work better than exploration
Raymond Weitekamp says OpenProse is for work that happens repeatedly, needs to be reliable and auditable, and has a known desired result. Chat is better when someone is exploring a problem and does not yet know its shape. The team presents the contract as a way to turn institutional operating knowledge into versioned documentation that can live in Git, Notion, or Jira. The approach is less strict than DSPy because it does not require every return object and interface to be fully specified, but it still requires the user or an agent to express the intended outcome.
Regulated model documentation can be expressed as a contract
Dan Barrett demonstrates a workflow for documenting quantitative models. Regulatory and internal requirements describe the desired document, including the model's purpose, testing conditions, upstream references, and other compliance details. The workflow runs in Codex with a public model, so the demo does not expose bank data. Barrett presents the use case as an in-house deployment on a company's own harness and models, keeping data and institutional procedures inside the organization. The generated documentation is then subject to review by quants, auditors, compliance teams, and regulators.
Composition lets contracts define both workflow shape and intermediate checks
The speakers describe composition as a core feature. Multiple contracts can be injected into one run, requiring the agent to satisfy several conditions. Smaller contracts can also act as intermediate checkpoints in a larger workflow. The team says common patterns such as fan-out and fan-in, adversarial review, and loops that continue until a condition is met can be expressed in a Prose program. This allows the author to constrain important stages without writing every implementation step. They compare the structure to a directed graph of contracts whose downstream work proceeds when an upstream condition changes.
"We want to tell it what to do, not how to do it because the harness in its infinite wisdom and its infinite intelligence is going to figure that out."Dan Barrett04:42
Who should watch
You are building agent workflows that need to run from webhooks, schedules, issues, or pull requests instead of inside a chat.
Your team wants operating procedures in Markdown that can be versioned and run on an existing coding harness.
You work on repeatable compliance, operations, product, or documentation tasks and need each run checked against an explicit outcome.