and do you ever look at the code afterwards? The 'software factory' gets exponentially nastier the longer it is kept running without someone with actual experience 'shoving it' back in shape ever so often ... and even then.
I've done the same but using Notion, and I've found really interesting to let the agents write a small "Dev Blog" post on a Notion page with what they built in the sessions, with screenshots, videos etc.
Also working with parallel sandboxes is a must: I use a manger session that read/write the issues from Notion and dispatch them to workers, it handles similar work to the same box to minimize merge conflicts.
PS: I'm using AgentBox for this (discl: I'm the author, free OSS): npm -g i @madarco/agentbox but now also Claude is releasing Projects (still rolling out) and Cursor had cloud agents for a while
trying to code while driving is a terrible idea, and it is not changed by whether complaining it about it is virtue signalling
"is a lot higher than the chances" - you killing people due to such stupid idea is far far worse, so that despite it being less likely it has far greater negative impact
This is exactly the kind of bullshit that's more signaling than anything realistic. Most people that use a headset in their car or have a chat with a LLM about system design, and sure, nowadays even push some generated code out, don't do this while speeding at insane speeds towards a family. It's 2026, some people might literally be in a self driving car.
Just horrible takes you're somehow equating using your mouth and brain in a car for any non car function to killing people.
I swear to God, you people are just amazing. I hope you never speak to your friends or family in a car. God forbid your child ask you a question. "Daddy, why are cows brown?" cause that would make you engage your brain and kill people.
Signalers... and now I'm ashamed for having posted three comments to this thread with no other contribution than agitating signalers, and myself in the process.
- Create a Git Hub project board for issues
- Connect Grok to the above
- Use Grok voice mode to take ideas, have Grok refine them with me and then save them as issues
- Created slash commands in OpenCode like /ni (new issue), /do (do an issue), /curr (what is the current issue), /done (self explanatory)
- I generally tell the OpenCode instance to /do <number> and then off it goes
This give me several benefits:
- I can use Grok Voice while walking or driving to develop and test ideas
- I can lose my entire local OpenCode setup but still have relevant data in the issues
- multiple machines can read from GitHub
- I could go even further and have separate user accounts for each of my bots.
Having been both a PM, dev, SRE and manager, this really does feel like managing a team of devs.