Skip to content

ByteAsk CLI v0.2.0

Choose a tag to compare

@pratyushiitd pratyushiitd released this 02 Nov 18:59
· 2 commits to main since this release

ByteAsk CLI 0.2.0

The previous release was 0.1.16 on 9 October. This one rebuilds the engine on all four platforms.

Update with byteask --update, or pip install -U byteask, or npm i -g @byteask/cli.


Ultra plan

  • Ultra ($200 for 30 days) is now on /upgrade next to Pro and Max: $20 of model use per 5 hours and
    $60 per week. A Max subscriber can renew Max or move up to Ultra from the same screen.
  • Every plan row now shows its real limits (for example $4 per 5h, $8 per week on Pro) instead of a
    multiple of Free.

Leaner sessions

  • Rarely used tools now load on demand, so each request carries a smaller fixed prompt. Interactive tools
    (questions in Plan mode, images, web search) are always loaded.
  • The always-on C/C++ guidance is now a short set of rules: build and test with the project's own build
    system, keep your build tree and files, use sanitizers and debuggers when the symptoms call for them.
  • A long wait on a running command now ends as soon as you send a message.

C/C++ tools

  • New: cpp_finish_check. Before saying a change works, the agent can build the affected code and run the
    project's tests, within 90 seconds, and report PASS, FAIL or NOT RUN with the reason. It never deletes files
    and never sends the agent back on its own.
  • New debugging tools: debug_core (diagnose a core dump), debug_reverse (step backwards through an rr
    recording, Linux), cpp_kdb (inspect a stopped Linux kernel over KGDB/KDB, Linux), plus cpp_impact
    (related places a change may need), cpp_test_select (run the tests a change affects) and
    cpp_repo_history.
  • Safer by default: on Linux the C/C++ tools run in their own sandbox (where none can start, they run
    without one and say so), cpp_compile_db never writes into your project, and cpp_format only formats the
    lines you changed, only where the project has a .clang-format.
  • More accurate cpp_check, cpp_tidy and cpp_sanitize (MemorySanitizer mode, allocation and free stacks
    in sanitizer reports, builds sized to the machine's memory).

Full access means full access

  • With full permission (approval policy never and no sandbox), ByteAsk no longer stops to ask: the C/C++
    tools run without consent prompts and the agent works around changes it did not make instead of pausing.

ByteAsk Context

  • byteask context connect adds ByteAsk Context (the hosted, build-aware code index) as an MCP server and
    signs you in. byteask context disconnect removes it.

Other changes

  • Locked models in /model show a lock and cannot be selected; /usage shows when extra credit expires.
  • byteask toolbox brings ByteAsk's C/C++ and reference tools to Claude Code and Codex.
  • byteask policy shows or resets the local policy file (~/.byteask/policy.toml).