Looks great! What's your experience of using this for working on real world production code?
Show HN: Engine – A multi-LLM alternative to Codex
11–16 of 16 posts
Re: Show HN: Engine – A multi-LLM alternative to Codex
#12Looks great! What's your experience of using this for working on real world production code?
60% of the time, it works every time
Re: Show HN: Engine – A multi-LLM alternative to Codex
#13Looks cool - do you have any benchmarks? How do you compare to other products out there?
Re: Show HN: Engine – A multi-LLM alternative to Codex
#14Looks cool - do you have any benchmarks? How do you compare to other products out there?
We last submitted a SWE-Bench verified result in November 2024 - at the time I believe we were in the top 5 entrants.
We expect Engine to be as good as the other code-writing agents out there at the moment - we understand almost everyone in the space to be using very similar base models and agent scaffolding.
Re: Show HN: Engine – A multi-LLM alternative to Codex
#15I've already merged my first Engine PR! Being able to review PRs like normal and it updates its work is very cool.
Re: Show HN: Engine – A multi-LLM alternative to Codex
#16What are the limitations are there in terms of tasks this can handle? How does this compare with the other products out there? There are plenty of options...
Depends on your set of tasks but we use Engine for the bottom ~50% of issues by complexity. We have a pretty good swe-bench score from a while back but it's got much better since! We have also focused on workflow integrations so you can assign issues from Linear, Jira, Trello etc which makes it more useful for teams.
Seems to me that integrations will be the most important component of tools like this. As an engineer I get my context from video calls with customers and other engineers, slack messages, emails, docs online, using the product myself, etc. So an auto-engineer should do the same.