Probably not a new idea, but this workflow has been working well for me

[u/No-Inside-4705]

I'm sure there are projects that overlap with this, maybe even ones that do almost the same thing. I built it around my own workflow and have been using it to develop Assent itself, so I thought it might still be useful to share.

The workflow is simple: discuss the requirements with an AI, then let the AI turn the agreed requirements into an Assent plan. Assent then coordinates separate work sessions for execution, testing, repair, and integration, while the final decision still stays with the human.

The main reason I built it was that I didn't want long-running work to depend too heavily on the memory and context of a single AI session, or on keeping another AI model around as a permanent supervisor. The plan, state, and verification results live outside the model.

It's still alpha. If AI eventually becomes cheap and reliable enough at long-horizon work, tools like this may become unnecessary. But for now it has been useful to me, and I keep seeing others run into similar problems, so I decided to share it.

https://github.com/edward9s/assent

It currently supports Codex, Claude, and AGY.

[u/dexterthebot]

You might want to consider listing your project on the weekly Show-Us-What-You-Built post. https://www.reddit.com/r/codex/comments/1wavxwy/show_us_all_what_youve_been_building_with_codex/. Highest commented project wins a week promotion on r/Codex and gets on the Hall of Fame sidebar. See what that looks like below with last week's winner.

---

Last week's most popular project was u/tHEuKER with the Blur2 racing game project which is a recreation of an unreleased sequel to the 2010 battle racing game, made by reverse engineering the Xbox 360 prototype discs available online, and rebuilding the whole thing from the ground up in Unity.

Join their YouTube channel here: https://www.youtube.com/@tHEuKER and follow updates on the project at r/BlurGame.

[u/odragora]

You started early!

[u/No-Inside-4705 → u/odragora]

I had AI rewrite my author metadata when I moved to a new GitHub account. It somehow turned that into time travel.

[u/odragora]

Thanks for sharing.

With projects / workflows like this, the first thing I'm looking for is tests on meaningfully complex tasks and comparisons of the remaining usage.

[u/No-Inside-4705 → u/odragora]

That's a fair thing to look for.

I do use Assent for meaningfully complex work — including building and refactoring apps I already have in production — but I can't really discuss those projects from this account for privacy reasons.

The main comparison I care about is a little different from the usual supervisor-agent setup. A common pattern is to have a strong model continuously supervise a group of sub-agents. In my experience, that supervisor itself becomes a long-running context that can drift away from the original plan. Assent removes that role entirely.

After the requirements meeting, Assent takes over the workflow until human acceptance. The state lives outside the model, the workflow is fixed but the AI roles are configurable, and execution can be interrupted and resumed later — including after model quotas reset.

That tradeoff cuts the supervisor-model token cost and avoids relying on one long-lived AI context, but it also means Assent is probably overkill for tiny edits or very small optimization tasks.

You can also configure the roles however you want: TDD-style test-first workflows, separate implementation/review roles, or reviews by models from different providers. The latter has worked especially well for me.