Okay, OpenProse made it dead simple to make a multi-agent flow. I have a prose command to orchestrate 5 agents that all coordinate with beads and agent mail. Beautiful. cc @irl_danB
Henry Ventura · @hvent90
View on X →№ Love · Public field notes
Read theirs before ours.
Tweets and DMs from builders shipping with OpenProse. Their reasons for forking will land better than ours.
- openprose/prosestars1.6kforks130
- openprose/pressstars49forks1
I just tried prose.md. Okay I really like. Why? I used it as a loop-wrapper for claude skills. And the SIMPLICITY is great~
Rijnard van Tonder · @rvtond
View on X →
adopted prose the last few days for my opencode workflows. being able to stitch together scripts, runners, sub-agents, skills, commands, etc into prose programs is such a mental-load unlock. i can build mini operating systems to execute complex workflows i've built without needing to remember how it's all wired.
bijan bina · @voidserf
View on X →
As a non-engineer, I cannot not love this idea: Open Prose relies "on the model to do the full orchestration", as opposed to more traditional frameworks who will still "wire all the steps together using a classical runtime (eg:Python)". An absolutely fascinating level of abstraction proposed here... And, on top of offering the project to the community, Dan is incredibly gracious in the replies.
Ben · @cocolitron
View on X →
I think this is immediately an essential tool for me. Just being able to implement a (research<->critique)->(implementation ->critique) loop is great. Does it work to be able to hand off between prose files? Am I even saying that the right way? Like if I did the above setup (coffeescript for prose.md lol) is that possible?
Max Caldwell · @max_takeoff
View on X →
@irl_danB @BenjaminDEKR please do! most interesting project of the last month by far
Gonzalo Nuñez · @gonzalo__nunez
View on X →
@irl_danB I use in folowing way Skill spawns prose Prose spawns parallel agent Each agent calls a skill Skill used to provide context to prose agents
David Hapunkt · @nichtsalsdavid
View on X →
@irl_danB just ran a 100 step process pretty fluidly, batched into groups of 10.
Michael Fraser · @zeroshotnothing
View on X →
example my issue: - have a claude skill to analyze some programs - skill is v long running - want to run it in a loop prose.md takes care of orchestration ^ i don't need to write "call subagents with this skill and do XYZ and aggregate the results"
Rijnard van Tonder · @rvtond
View on X →@Shpigford This looks like a perfect use case for OpenProse prose.md. It will make your e2e workflow more repeatable and reliable. @irl_danB
Winkle · @robbwinkle
View on X →
@irl_danB Actually.. I just tried it in @opencode. This is really interesting. The agent uses them flawlessly on initial testing. (Opus 4.5) I think I'll tryan mcp server and see if it can discover prose as tools and run as sub-processes. Or even a systemd vmspawn server.. very cooool
Tangled Circuit · @tangledcircuit
View on X →
Okay, OpenProse made it dead simple to make a multi-agent flow. I have a prose command to orchestrate 5 agents that all coordinate with beads and agent mail. Beautiful. cc @irl_danB
Henry Ventura · @hvent90
View on X →As a non-engineer, I cannot not love this idea: Open Prose relies "on the model to do the full orchestration", as opposed to more traditional frameworks who will still "wire all the steps together using a classical runtime (eg:Python)". An absolutely fascinating level of abstraction proposed here... And, on top of offering the project to the community, Dan is incredibly gracious in the replies.
Ben · @cocolitron
View on X →@irl_danB I use in folowing way Skill spawns prose Prose spawns parallel agent Each agent calls a skill Skill used to provide context to prose agents
David Hapunkt · @nichtsalsdavid
View on X →@Shpigford This looks like a perfect use case for OpenProse prose.md. It will make your e2e workflow more repeatable and reliable. @irl_danB
Winkle · @robbwinkle
View on X →From the inbox.
DMs and messages from builders. Reproduced with permission, attributed by role.
“hey just wanted to say openprose is pretty great! i've been building a long running multi-step agent, with the logic written in skills, but have been trying to find a better orchestration paradigm. I switched to openprose and its working well + seems it's easier for claude to autonomously improve the .prose file, vs long skill files. (forgive me for finding the github, I was pretty excited :) )”
“i appreciate the work you're doing. imo you're the only one i see in the space rn that's really approaching this from first principles. i'm building a few things with huge implications for finance and healthcare using press as the business logic layer, treating press like an employee. i write the runbook in english, press follows it. Scaling to N workflows without writing business logic in code. just structured prose.”
“Been using prose and it's great I love your work”
“I gotta try OpenProse. As someone who's been getting nerdsniped into building 'nicer' orchestration/experiment-tracking from scratch for the past couple of weeks, I just gotta see how different this is. Also curious to see how this feels alongside DSPy.”
“Saw this morning's post. Early OpenProse user and have been a fan of your thoughts in the space. Right now I'm working on two problems: (1) fitting agentic harnesses to strategy work (subjective and unverifiable output), and (2) the right store/format of context.”
Built something with Prose? Tell us.
A sentence is plenty. A paragraph is better. Every note gets a real reply, and nothing goes on the wall until you say yes, the way you want to be quoted.
Or DM @irl_danB on X.