ByteAsk gives Claude Code and Codex an index of your whole repo, so they start in the right file. Its Cloud Agent takes bugs from Slack, Jira or the browser, builds and tests in a sandbox, and opens a draft PR. Start with $50 of credit, no card.
Hey Product Hunt 👋 Anirudha and Pratyush here (ex-Optiver, ex-ThirdAI, YC F26).
> SOTA on Multi-SWE-bench (C/C++) > 60% fewer tokens than Claude Code and Codex > Auto debug / perf / optimize / test with native C/C++ tools > Free plan. Open-source CLI: github.com/ByteAsk/cli
Why we built it: in C++ the name isn't the code. Ask an agent to fix validate(order) and it greps, finds three functions called validate, reads all of them and edits the wrong one. The wrong edit still compiles. Which overload runs, which template gets instantiated and which #ifdef branch is live all depend on your build, and text search never sees the build.
What ByteAsk does:
Context indexes your repo the way your build does (LLVM in 13.7 min; Graphify hadn't finished after 3 h). Connect it with one prompt in Claude Code or Codex.
The harness builds with your toolchain, runs only the tests your change reaches, and uses sanitizers, gdb and perf on failures.
Cloud agents take bugs from Slack, Jira or the CLI, try fixes in parallel and send one PR with the proof attached.
Honest numbers (papers, code and tasks at byteask.ai/research): against Codex CLI on the same OpenAI model, both fixed 129 of 144 runs. ByteAsk didn't fix more, but it used 63–80% fewer tokens and cost 59–70% less. The biggest savings were on little-known projects the model hasn't memorized.
Free plan: $5 of usage a month, one cloud agent task, no card. On-prem or air-gapped? Book a call.
Tell us where it breaks on your codebase. That's the feedback we want most.
The 'agent greps around and lands in the wrong overload' problem is my daily life — I run Claude Code on my own repos all day and the first file it picks is wrong more often than I'd like to admit. The index updating on push plus picking up uncommitted changes is the part that would actually make me trust it. Curious how it handles Swift, though — the benchmarks and examples are all C/C++, and my world is Swift packages where the build graph looks pretty different.
congrats on the launch anirudha. to your question, where i would expect it to break is monorepos with shared packages. agent fixes one app and quietly breaks another app that uses the same package. does it run tests for all affected packages before the pr, or only the one it touched?
the validate(order) example is painfully real, three functions with the same name and the agent picks the one that still compiles
also like that you posted same fixes as Codex, just cheaper, instead of a made up win rate. does the index rebuild on eveyr commit or only when the build config changes??? on a big repo that feels like where the time goes
About ByteAsk Cloud Agents on Product Hunt
“Find the fix in big codebases. Ship it from Slack.”
ByteAsk Cloud Agents launched on Product Hunt on November 15th, 2026 and earned 87 upvotes and 6 comments, placing #12 on the daily leaderboard. ByteAsk gives Claude Code and Codex an index of your whole repo, so they start in the right file. Its Cloud Agent takes bugs from Slack, Jira or the browser, builds and tests in a sandbox, and opens a draft PR. Start with $50 of credit, no card.
ByteAsk Cloud Agents was featured in Developer Tools (523.3k followers), Artificial Intelligence (484k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 268.4k products, making this a competitive space to launch in.
Who hunted ByteAsk Cloud Agents?
ByteAsk Cloud Agents was hunted by Garry Tan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how ByteAsk Cloud Agents stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hey Product Hunt 👋 Anirudha and Pratyush here (ex-Optiver, ex-ThirdAI, YC F26).
> SOTA on Multi-SWE-bench (C/C++)
> 60% fewer tokens than Claude Code and Codex
> Auto debug / perf / optimize / test with native C/C++ tools
> Free plan. Open-source CLI: github.com/ByteAsk/cli
Why we built it: in C++ the name isn't the code. Ask an agent to fix validate(order) and it greps, finds three functions called validate, reads all of them and edits the wrong one. The wrong edit still compiles. Which overload runs, which template gets instantiated and which #ifdef branch is live all depend on your build, and text search never sees the build.
What ByteAsk does:
Context indexes your repo the way your build does (LLVM in 13.7 min; Graphify hadn't finished after 3 h). Connect it with one prompt in Claude Code or Codex.
The harness builds with your toolchain, runs only the tests your change reaches, and uses sanitizers, gdb and perf on failures.
Cloud agents take bugs from Slack, Jira or the CLI, try fixes in parallel and send one PR with the proof attached.
Honest numbers (papers, code and tasks at byteask.ai/research): against Codex CLI on the same OpenAI model, both fixed 129 of 144 runs. ByteAsk didn't fix more, but it used 63–80% fewer tokens and cost 59–70% less. The biggest savings were on little-known projects the model hasn't memorized.
Free plan: $5 of usage a month, one cloud agent task, no card. On-prem or air-gapped? Book a call.
Tell us where it breaks on your codebase. That's the feedback we want most.