- 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.
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
alexpotato · · focus · HN ↗
- 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.
madarco · · focus · HN ↗
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
llmpress · · focus · HN ↗
[dead]