Entries for August 20, 2026

  1. Portrait of Onur Solmaz
    @onusoz · /2026/08/20 · View on
    This is your daily reminder that you can just vibe your dream terminal dashboards with @ratatui_rs and it just works amazingly
    @onusoz ·
    God save my soul I might have built quite a bit of a rube goldberg machine here in pi My "autoimplement" skill of 6 months is now an actual graph based workflow I even have "autoplan". It automates the inquisition I make the model perform on itself. It creates the plan, and pings me on telegram whether or not to move forward with it The idea is to have reactive agents which auto-react to events, plan, ask for approval and then fix things as autonomously as possible The good thing is, I can now enforce the model programmatically not to chase P2 and P3 review issues ad infinitum Same for long running CI. I can now automatically detect inefficient CI that takes longer than 5~10 minutes and optimize it automatically as well Let me know what works for you and what breaks (wip):
  2. Portrait of Onur Solmaz
    @onusoz · /2026/08/20 · View on
    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):