---
title: "Composing agent workflows to unblock themselves"
date: 2026-08-20
canonical: https://solmaz.io/x/2090560238889881861/
x_url: https://x.com/onusoz/status/2090560238889881861
license: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
---

Once nice thing with workflow graphs is to be able to compose them

I stitched `autoplan` + `autoimplement` workflows into `monitor` in an "issue detected" path:

monitor -> wait 30min -> issue detected -> autoplan -> autoimplement -> monitor

Previously, monitor would just stop with "blocked" on trivial issues. Now, the workflow deterministically challenges the model whether it actually is a blocker (it literally asks, "are you really sure if it's a blocker")

If the model is like "nah bro, it's actually something I could fix", then it puts the model into this path

The good thing is, I can compose and nest workflows arbitrarily without code duplication

I generally call `autoplan` and `autoimplement` separately. I prefer to read the plans before I hit implement

But by the time I hit `monitor` on a long running job, I expect something to finish by itself (I have given all the information that the system needs, and any new issues should be trivial)

In the screenshot below, the model went into this path and unblocked itself automatically

Repo (still highly experimental, breaking changes will happen):