Solver
Offload coding tasks to AI while you tackle bigger problems
424 followers
Offload coding tasks to AI while you tackle bigger problems
424 followers
Solver is an autonomous coding agent that completes software tasks on its own. Give it work, walk away, and return to finished code ready for review. It operates directly in your git repositories, handling everything from bug fixes to new features.
Free Options
Launch Team / Built With
HabitGo
@mark_gabel 🧠 Don’t be fooled by the name — this thing is a repo assassin.
In the past, implementing ideas through code was a major hurdle.
But with Solver, we’ve stepped into a new era — where coding itself can be outsourced. Congratulation on the launch team! 🎊
Looks very helpful! Which programming languages are supported?
Solver
@maria_kud all of them! Solver is mostly language-agnostic and will work with any Github repo. That said, we've built-in some additional integrations with common languages like Python, JavaScript/Typescript and others.
If your language/toolchain of choice isn't well-supported natively, you can always configure Solver by configuring a custom Docker image for its environment and/or create Memories that tell Solver how to operate effectively in your repo.
We're always eager to hear how you use Solver and whether there are native improvements we can make to facilitate your workflows!
@nico_rako thank you for your reply ☺️
Solver looks like a game changer for developers! The ability to offload entire coding workflows not just autocomplete lines feels like a massive leap forward. Vibe coding is such a cool concept, especially for quickly spinning up prototypes or handling repetitive tasks without breaking focus
Anchor
Wow, incredible stuff! Great job Niko and team
Solver
Thanks @thejcad! Eager to hear your thoughts when you give Solver a try
Excited about autonomous coding—huge time saver for devs! 👀
Fable Wizard
Solver seems like a fantastic tool for development teams, saving so much time on routine tasks so engineers can focus on the creative work that truly matters! The ability to describe what you need and have a solution ready for review sounds like a real time-saver. How adaptable is Solver when it comes to custom workflows, especially for teams with specific coding practices or unique project setups?
Solver
@jonurbonas Thanks for the support, Jonas, and great questions! We've worked on a large variety of projects in our collective careers and we know that no two are alike. Here are some things we've done to keep Solver individualized:
We have a first-class "memories" feature, which allows you to store nuggets of repo-specific knowledge and reuse them in all future sessions (without any credit deduction!). And occasionally, Solver will even proactively suggest new memories on its own for you to review.
Solver builds an index of your repository and "gets to know it" very well, all when you first "activate" that repo in our UI. That index is then incrementally updated for whatever session you're on. That index gives Solver strong code search and code understanding capabilities, all native, that allow it to pivot more into "domain specific engineering" very quickly.
For truly custom workflows, where you perhaps want to use Solver outside of the Solver webapp, we actually have a public API that will soon be separately launched! Today, that API powers much of Solver, especially our Slack integration (if you have the time and inclination - check that out. Tagging `@Solver` in a Slack thread and having the work just get done feels so futuristic), but soon we'll be opening it up to all devs and seeing what they build. We're particularly excited about the possibility of automatically proposing fixes to issues reported in observability tracking systems like Datadog.
Solver
@jonurbonas @Solver @mark_gabel If you're looking to integrate Solver with specific coding practices/toolchains you can combine the memories feature with Solver's execution environment to give Solver a dev environment just like the one you use. If you ask Solver to use any tools (e.g. we use `ruff` to enforce a codestyle) it will install the tools and you can then use a memory to have Solver always run those tools before it completes a task.
@nico_rako put together a great tutorial video on how to do this that @mark_gabel linked in a different reply. If that route still isn't flexible enough you can bring your own docker image and Solver will use that as its executin environment for even more flexibility!