Launching today

Osloq
An AI agent that reproduces GitHub issues for you
181 followers
An AI agent that reproduces GitHub issues for you
181 followers
Most AI dev tools just read your code and guess. Osloq actually runs it. Connect your GitHub, pick an issue, and an AI agent spins up a real sandbox, clones your repo, runs it, and tries to reproduce the bug the way a developer would. You get a report backed by real evidence. What happened, the steps it took, and whether the bug is real, not a hallucinated guess. No local setup, no "works on my machine." It handles the tedious reproduction step so you jump straight to fixing.








How does the sandbox handle repos with heavy infra dependencies like docker compose or database services. Does it spin those up too or just the app code in isolation?
Running the actual code instead of reasoning about it is the right call. Curious how Osloq handles repos with external service dependencies - database calls, third-party APIs - where the bug only shows in a specific environment setup.
The sandbox repro thing is genuinely cool, I picked a flaky issue from one of my repos and it came back with actual logs and the failing test. Wish I'd had this last week when I burned an afternoon chasing a "bug" that turned out to be a stale local DB.
Tried it on a tricky bug I'd been putting off and the agent actually cloned the repo and walked through reproduction steps I hadn't even considered. Loved that the report felt grounded in real output rather than speculation.
I would like support for retrying failed reproductions. Multiple execution attempts could separate random failures from actual bugs.
Really smart move focusing the agent on reproducing issues specifically, instead of trying to fix everything. Repro is the annoying part that eats up so much of my morning, and getting a clean repro is half the battle anyway.
@yibo_wang3 thanks! yeah, that's exactly the bet
actually runs the repo in a sandbox to verify bugs, that part genuinely sold me. way more useful than the usual "here are 5 possible causes" guesswork from other tools.
@eminenv9f thanks! that was exactly the goal