146 points by codekarate 1 day ago | 42 comments | View on ycombinator
brap about 21 hours ago |
yoz 1 day ago |
jaf12duke 1 day ago |
Gakho 1 day ago |
I've seen this pattern happening in other open-source repos. Do you think it's going to be the norm now?
siscia 1 day ago |
There is a [language](https://redbeardlab.github.io/dotFactory/) that let express complex workflows.
The workflow can be pretty much anything, eg:
1. Clone repo A and B + Start OpenCode + Feed a prompt into it
2. Pick up the commit generated by opencode for both repo, and run CI
Another workflow I created is: every day at 3AM, check that the documentation of the website is up to date, if yes exit, if not update the documentation. Pass the updated documentation to an adversarial LLM and if it pass, merge it - otherwise loop with the feedback from the adversarial one.
You have a concept of trigger, which can be either a webhook, or a github PR or a github issue, or just a cron expression. Or just someone manually clicking.
There is a concept of secrets and config, so the user can create their own secrets to start codex-cloud, or opencode, or making custom API call.
There is also the concept of manual gate, so you can wait for an human to actually click a button.
Finally, it supports running containers. Useful if you want to call an obscure API from your workflow, you don't have to wait for the platform owner to create a step for your API, but you can just run a container into it.
namanyayg about 18 hours ago |
SillyUsername 1 day ago |
moltar 1 day ago |
volkermauel about 13 hours ago |
jobryan 1 day ago |
_pdp_ about 21 hours ago |
Software factories are not a real architecture. They are just AI agents working on the same project. GitHub and similar platforms are already ideal for this. Requirements go in as issues, agents open PRs, someone reviews and merges them.
We used to call this software development.
The only "new" part is that now nobody complains at standups!
tireguess 1 day ago |
saarth28 1 day ago |
undefined about 15 hours ago |
slopinthebag 1 day ago |
solutionsbymeh about 21 hours ago |
gyuminoh 1 day ago |
agent_yard 1 day ago |
MykhailoSailor 1 day ago |
Couple of questions:
1. Did you experiment with not having a separate design/plan phase? From my experience agents usually don’t really know what the plan is until they start editing files and executing tests (in other words, implementing), so the initial plan is usually not great and changing it mid-flight is overhead. I also find reviewing tested code to be much easier than reviewing plans/designs, which are often full of ungrounded assumptions.
2. Is this using your own custom coding agent harness over the raw LLM endpoints users provide? If so, did you consider having it integrate with existing harnesses (e.g. Claude Code, Antigravity, etc.)?