Signed in. No key to paste.
Managed
Sign in and use OpenAI, Anthropic and Google models through ByteAsk. No API key to paste.
AI coding agent for C and C++
Backed by Y CombinatorByteAsk works in your terminal. It edits the code, runs the compiler, the sanitizers and your tests, and can drive the gdb session you already have open. You review the diff.
Zero data retention. Your code is processed, then dropped.
Compilers, sanitizers, debuggers, profilers and binary analysis, each one a visible tool call.
Standards and datasheets returned as excerpts, or an explicit miss.
The full dataset, looked up rather than recalled.
Your flags, your build system. The diff you review has already been built.
Through a bridge you arm yourself, inside the session you already have open.
Frames, files and line numbers intact, so you can audit the reasoning.
Read-only commands run. Anything that changes state is proposed first.
Linux allows one debugger per process. ByteAsk joins through a bridge you start in your gdb, reads the live state, and asks before it changes anything.
How a session is wired.
Your gdb holds the process. A second debugger is refused by the kernel. ByteAsk goes through the bridge you started. Check it yourself: while your gdb holds a process, run gdb -p <pid> in another shell.
ByteAsk builds with your flags, runs the sanitizers, and runs your tests. It hands back the raw report with the frames, files and line numbers intact, so you can check the agent's reasoning against the same evidence.
g++ 12.2 with AddressSanitizer, captured 2026-09-03. Source and script in demo/outputs. The overflow is the one bug in order_book.cpp: cancel_all() walks the level array one iteration too far.
ctest on the same tree, same run. The three demo tests from the same tree, each a plain executable that returns zero when it passes. Nothing in these two blocks was typed by hand. They are what the tools printed.
Each one runs as its own step you can see, with its arguments and its output, so nothing the agent does is hidden behind a summary.
It reads the project the way clangd does. Generates compile_commands.json, then navigates by symbol rather than by grep.
Sanitizers, debuggers and deterministic replay. ASan, UBSan, TSan and Valgrind, batch and stateful gdb or lldb, and rr for a trace you can replay.
Your config, not ours. clang-tidy and clang-format read the .clang-tidy and .clang-format already in your tree.
Measure, then change. perf and Callgrind for the real workload, QuickBench for a single function.
Down to the instruction. objdump, nm and readelf, PIE-aware symbolization, and decompilation when there is no source.
Reference documents it can cite. Built-in reference tools search these standards and datasheets and return the exact passage with a citation. If there is no match, they say so instead of guessing.
Sign in and use OpenAI, Anthropic and Google models through ByteAsk. No API key to paste.
Use your own OpenAI, Anthropic or Gemini key. Traffic goes straight to the provider, not through ByteAsk.
Point ByteAsk at vLLM, Ollama, llama.cpp, LM Studio, TGI, SGLang or a LiteLLM proxy. Self-hosted models are not metered.
One line on Linux, macOS or Windows, or a plugin for your editor.
Sign in with a link sent to your email.
Say what you want in plain language, in your terminal.
It has already been built, run and tested.
A plugin for 6 editors, all driving the same CLI. Pick one, or stay in the terminal.
Also on Windsurf and
VSCodium via Open VSX.
Every connector needs the byteask CLI on your PATH. Check with byteask --version.
Pick your platform
Zero-retention by design. Your machine carries a short-lived token and nothing more.
Your prompts and code are processed to answer the request, then dropped. Nothing is kept. Read the privacy policy
Your repositories are not used to train any model. Ours or anyone's.
A signed magic link logs you in. No password to manage, and nothing to paste or leak.
ByteAsk joins the gdb session you already have open through a bridge you start, instead of competing with it for the process. It also builds, runs the sanitizers and runs your tests before you see the diff.
Linux allows one debugger per process. While your gdb is attached, the kernel refuses a second one. Check it yourself: run gdb -p <pid> in another shell.
No. Use managed models with no key to paste, your own OpenAI, Anthropic or Gemini key, or point ByteAsk at your own server.
Self-hosted models are not metered.
Reference tools search the standards and datasheets and return the exact passage with a citation. If there is no match, they say so instead of guessing.
There is a plugin for 6 editors, all driving the same CLI, plus Windsurf and VSCodium via Open VSX. Every connector needs the byteask CLI on your PATH.
Writes the change, then proves it compiles, runs and passes.
$ curl -fsSL https://code.byteask.ai/install.sh | shbyteask in the terminal.