We recently started to use agents to update some documentation across our codebase on a weekly basis, and everything quickly turned into cron jobs, logs, and terminal output.
it worked, but was hard to tell what agents were doing, why something failed, or whether a workflow was actually progressing.
We thought it would be more interesting to treat agents as long-lived workers with state and responsibilities and explicit handoffs. Something you can actually see and reason about, instead of just tailing logs.
So we built Clawe, a small coordination layer on top of OpenClaw that lets agent workflows run, pause, retry, and hand control back to a human at specific points.
This started as an experiment in how agent systems might feel to operate, but we're starting to see real potential for it, especially for content review and maintenance workflows in marketing. Curious what abstractions make sense, what feels unnecessary, and what breaks first.
Repo: https://github.com/getclawe/clawe
These are all proto orchestrators. No one has discovered/converged on what agent orchestration actually looks like.
Other projects include conductor.build, gas town (infamously), and others.
Another layer of abstraction in the infinite castle of computer science.
1: https://www.vibekanban.com/
reply