Base Components: https://stacker.news/items/1427542/r/optimism?commentId=1428143

Specific components (all custom):

1. Rest server for task execution queueing and tracing
2. Kanban board that lets me create, drag & drop authorize/prioritize tasks (yes, also on mobile, it's fun putting the bot to work while in queue doing groc)
3. Actions runners that fill the board from tagged issues
4. Executors that poll boards for jobs to run, pass it to a bot headlessly (eg: `claude -p <prompt>`), return trace logs to jobs and trigger reports to my phone - currently running this single-llm because I anyway run out of credit allocation all the time and I downed my AWS gpu box for now
5. MASSIVE test infra across unit, integration, security audits, supply chain control and constant whining to the bots that their tests coverage sucks - I have a small project to automate this now, because I get tired of doing the whining. The bot will soon just whine to itself.
6. 50x per day resist the urge to just press "merge" and actually review every single line of slop the clanker produces.
7. bi-hourly backups of everything

Interesting.  I'd love to know more about your setup.

SimpleStacker

I've not had great results with "letting AI do its thing"

If I properly review the outputs of code / research / plans, it means I do ∞x because I let the bot do stuff that would never get to the top of my todo. So I just queue it up and then spend time on review, queue up more. I could automate that too, except as discussed above, the bots have high error rate, so I don't, or I end up 

Made a little script that uses up all tokens in my claude plan (and reports on it after every task) and then sleeps until the plan resets. This week I'll have about 5% unused because I was too busy to queue up work Mon/Tue. It works on 15 projects concurrently for me right now. I can reprioritize next task at any time; basically it runs the equivalent of a mid-size agile software shop for me, but with a dictator-in-chief, me.

Anyway, the great thing about queueing up work is that I just review a couple of times per day, mostly keeping focus on a single project until I went through everything and queued new work. Then I go get a coffee, have a smoke, and do the next. Or do some actual work.

Stacker Saloon

saloon

> I've not had great results with "letting AI do its thing"

If I properly review the outputs of code / research / plans, it means I do ∞x because I let the bot do stuff that would never get to the top of my todo. So I just queue it up and then spend time on review, queue up more. I could automate that too, except as discussed above, the bots have high error rate, so I don't, or I end up [pwnd like Palantir/OpenAI/USG](https://stacker.news/items/1436017/r/optimism).

Made a little script that uses up all tokens in my claude plan (and reports on it after every task) and then sleeps until the plan resets. This week I'll have about 5% unused because I was too busy to queue up work Mon/Tue. It works on 15 projects concurrently for me right now. I can reprioritize next task at any time; basically it runs the equivalent of a mid-size agile software shop for me, but with a dictator-in-chief, me.

Anyway, the great thing about queueing up work is that I just review a couple of times per day, mostly keeping focus on a single project until I went through everything and queued new work. Then I go get a coffee, have a smoke, and do the next. Or do some actual work.