<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>ByteAsk changelog</title>
    <link>https://byteask.ai/changelog</link>
    <description>Releases of the ByteAsk CLI, and changes to ByteAsk plans and setup.</description>
    <language>en-us</language>
    <item>
      <title>One plan and one setup prompt</title>
      <link>https://byteask.ai/changelog#2026-11-10</link>
      <guid isPermaLink="false">2026-11-10</guid>
      <pubDate>Tue, 10 Nov 2026 13:38:47 GMT</pubDate>
      <description>&lt;p&gt;ByteAsk now has one plan for Context, the Cloud Agent and the ByteAsk CLI. It is billed per workspace (a person or a GitHub organization), with no per-seat charge, and the plan fee is all usage credit.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Plans:&lt;/strong&gt; Free includes $5 of usage credit every month, with no card. Pro is $20 a month, Max $100 and Ultra $200, each with that much credit every month. Annual plans get 2 months free. Enterprise is custom.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Models&lt;/strong&gt; are billed at the provider's list price + 20%. Bring your own Anthropic or OpenAI key on any plan, with no markup.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;The cloud sandbox&lt;/strong&gt; (4 CPU, 12 GB, for a Cloud Agent task's build and tests) is $0.40 an hour, billed per minute. Setup and environment builds are free, and Context lookups and indexing are included within your plan's limits.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Existing paid CLI subscribers keep their current terms until their paid period ends.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Everything is on &lt;a href="https://byteask.ai/pricing"&gt;the pricing page&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;One setup prompt&lt;/h2&gt;
&lt;p&gt;Every install button on byteask.ai now copies one short prompt. Paste it into Claude Code, Codex, Cursor or another MCP client, and the agent follows &lt;a href="https://byteask.ai/agent-guide.txt"&gt;the setup guide&lt;/a&gt;: it asks which products you want, tells you the cost first, and shows a dry run of every change before it makes it. Claude Code and Codex get the full Context setup; Cursor and other MCP clients get the MCP server. The same steps by hand are in &lt;a href="https://byteask.ai/docs/setup/"&gt;the docs&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.2.4</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.2.4</link>
      <guid isPermaLink="false">v0.2.4</guid>
      <pubDate>Tue, 10 Nov 2026 08:46:55 GMT</pubDate>
      <description>&lt;h2&gt;ByteAsk CLI 0.2.4&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;ByteAsk&amp;#39;s best-measured harness configuration is now the default.&lt;/strong&gt; Nothing to set up: every setting below is on
for new and updated installs, and each one can be changed in &lt;code&gt;~/.byteask/config.toml&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;With ByteAsk Context connected&lt;/strong&gt; (&lt;code&gt;byteask context connect&lt;/code&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;ByteAsk follows a short set of working rules: reproduce the problem first, make the change complete across the
related places (Context&amp;#39;s &lt;code&gt;find_related_changes&lt;/code&gt; and &lt;code&gt;get_symbol&lt;/code&gt; list candidates), keep the repository&amp;#39;s own
helpers and names, and check the change with &lt;code&gt;cpp_finish_check&lt;/code&gt; before finishing. Your own &lt;code&gt;developer_instructions&lt;/code&gt;
replace them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Context&amp;#39;s code pack waits up to 2 minutes on large repositories, and a top-level CMakeLists.txt, meson.build or
configure.ac marks a repository as C/C++.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;cpp_finish_check&lt;/code&gt; lists the places Context says may need the same change, right after its verdict.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Headless runs (&lt;code&gt;byteask exec&lt;/code&gt;) offer a smaller tool set; interactive sessions keep every tool.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;C/C++ checks:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;cpp_finish_check&lt;/code&gt; builds and runs the nearest tests&amp;#39; programs first and names the other tests the change reaches.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A change that no compiled file reaches is reported as not checked, never as passed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;When a turn ends with a C/C++ change nobody checked, ByteAsk runs the check once and shows the result.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;C/C++ tools whose program is not installed are not offered.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Builds and long commands:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;ByteAsk&amp;#39;s background builds run at idle priority, give way to your builds in the same tree, and stop first under
memory pressure.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The environment note states the memory limit and a job count that fits it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;On a long-running command without a terminal, ByteAsk waits 30 s before the first check and up to 3 minutes
between checks; every wait ends as soon as the command exits.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Platforms:&lt;/strong&gt; Linux (x86_64, arm64) and Windows carry everything above. The macOS engine in this release is the 0.2.3 engine; the 0.2.4 macOS engine follows.&lt;/p&gt;
</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.2.3</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.2.3</link>
      <guid isPermaLink="false">v0.2.3</guid>
      <pubDate>Tue, 03 Nov 2026 19:41:54 GMT</pubDate>
      <description>&lt;h2&gt;ByteAsk CLI 0.2.3&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Your own provider key now unlocks that provider&amp;#39;s Pro models.&lt;/strong&gt; On the Free plan with your own Anthropic (or other
provider) key saved and BYOK active, that provider&amp;#39;s models are now selectable in &lt;code&gt;/model&lt;/code&gt;. They used to show as
&amp;quot;Available on ByteAsk Pro&amp;quot;. Those turns go straight to the provider on your key.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;ByteAsk Context: a one-line check for the change.&lt;/strong&gt; With ByteAsk Context connected (&lt;code&gt;byteask context connect&lt;/code&gt;) in a
CMake project, ByteAsk now finds the tests that cover the place Context points to and starts building them in the
background. It then gives the agent one command that builds and runs only those tests, instead of building and testing
the whole project. This applies in full-access sessions.&lt;/p&gt;
&lt;p&gt;0.2.1 and 0.2.2 were skipped so that every channel carries the same version.&lt;/p&gt;
</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.2.0</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.2.0</link>
      <guid isPermaLink="false">v0.2.0</guid>
      <pubDate>Mon, 02 Nov 2026 18:59:01 GMT</pubDate>
      <description>&lt;h1&gt;ByteAsk CLI 0.2.0&lt;/h1&gt;
&lt;p&gt;The previous release was 0.1.16 on 9 October. This one rebuilds the engine on all four platforms.&lt;/p&gt;
&lt;p&gt;Update with &lt;code&gt;byteask --update&lt;/code&gt;, or &lt;code&gt;pip install -U byteask&lt;/code&gt;, or &lt;code&gt;npm i -g @byteask/cli&lt;/code&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;Ultra plan&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Ultra ($200 for 30 days)&lt;/strong&gt; is now on &lt;code&gt;/upgrade&lt;/code&gt; 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.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Every plan row now shows its real limits (for example &lt;em&gt;$4 per 5h, $8 per week&lt;/em&gt; on Pro) instead of a
multiple of Free.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Leaner sessions&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;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.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The always-on C/C++ guidance is now a short set of rules: build and test with the project&amp;#39;s own build
system, keep your build tree and files, use sanitizers and debuggers when the symptoms call for them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A long wait on a running command now ends as soon as you send a message.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;C/C++ tools&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;New: &lt;code&gt;cpp_finish_check&lt;/code&gt;.&lt;/strong&gt; Before saying a change works, the agent can build the affected code and run the
project&amp;#39;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.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;New debugging tools:&lt;/strong&gt; &lt;code&gt;debug_core&lt;/code&gt; (diagnose a core dump), &lt;code&gt;debug_reverse&lt;/code&gt; (step backwards through an rr
recording, Linux), &lt;code&gt;cpp_kdb&lt;/code&gt; (inspect a stopped Linux kernel over KGDB/KDB, Linux), plus &lt;code&gt;cpp_impact&lt;/code&gt;
(related places a change may need), &lt;code&gt;cpp_test_select&lt;/code&gt; (run the tests a change affects) and
&lt;code&gt;cpp_repo_history&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Safer by default:&lt;/strong&gt; on Linux the C/C++ tools run in their own sandbox (where none can start, they run
without one and say so), &lt;code&gt;cpp_compile_db&lt;/code&gt; never writes into your project, and &lt;code&gt;cpp_format&lt;/code&gt; only formats the
lines you changed, only where the project has a &lt;code&gt;.clang-format&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;More accurate &lt;code&gt;cpp_check&lt;/code&gt;, &lt;code&gt;cpp_tidy&lt;/code&gt; and &lt;code&gt;cpp_sanitize&lt;/code&gt; (MemorySanitizer mode, allocation and free stacks
in sanitizer reports, builds sized to the machine&amp;#39;s memory).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Full access means full access&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;With full permission (approval policy &lt;code&gt;never&lt;/code&gt; 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.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;ByteAsk Context&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;byteask context connect&lt;/code&gt; adds ByteAsk Context (the hosted, build-aware code index) as an MCP server and
signs you in. &lt;code&gt;byteask context disconnect&lt;/code&gt; removes it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Other changes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Locked models in &lt;code&gt;/model&lt;/code&gt; show a lock and cannot be selected; &lt;code&gt;/usage&lt;/code&gt; shows when extra credit expires.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;byteask policy&lt;/code&gt; shows or resets the local policy file (&lt;code&gt;~/.byteask/policy.toml&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p class="bx-changelog-trim"&gt;&lt;a href="https://github.com/ByteAsk/cli/releases/tag/v0.2.0" rel="noopener"&gt;Read the full release notes&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.16</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.16</link>
      <guid isPermaLink="false">v0.1.16</guid>
      <pubDate>Fri, 09 Oct 2026 01:03:01 GMT</pubDate>
      <description>&lt;p&gt;ByteAsk CLI v0.1.16&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;/model&lt;/code&gt; now reliably shows what your plan includes. Models you can&amp;#39;t use are marked 🔒 Pro, and retired models are hidden. If the list ever looked out of date for you, this fixes it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Bring-your-own-key users on an Anthropic key: Claude Fable 5.1 and Claude Haiku 5.5 now work, and Claude Haiku 4.5 no longer fails on effort settings.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The engine is unchanged from v0.1.15.&lt;/p&gt;
</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.15</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.15</link>
      <guid isPermaLink="false">v0.1.15</guid>
      <pubDate>Sun, 27 Sep 2026 19:21:45 GMT</pubDate>
      <description>&lt;h1&gt;ByteAsk CLI 0.1.15&lt;/h1&gt;
&lt;p&gt;The previous release was 0.1.14 on 23 September. This one rebuilds the engine on all four
platforms.&lt;/p&gt;
&lt;p&gt;Update with &lt;code&gt;byteask --update&lt;/code&gt;, or &lt;code&gt;pip install -U byteask&lt;/code&gt;, or &lt;code&gt;npm i -g @byteask/cli&lt;/code&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;Debugging on a Mac&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;debug_session&lt;/code&gt; now runs on &lt;strong&gt;lldb&lt;/strong&gt;, so interactive debugging works on Apple Silicon Macs,
where gdb does not run. lldb is the default on macOS, and a Mac is never told to install gdb.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A crash dump from another machine opens with that machine&amp;#39;s libraries: pass &lt;code&gt;sysroot&lt;/code&gt; to
&lt;code&gt;debug&lt;/code&gt; or &lt;code&gt;debug_session&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;After a crash, ByteAsk runs the post-mortem commands first and tells you what failed and where.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;C/C++ tools you can trust&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Program arguments reach your program exactly as written, including empty and quoted ones.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A tool no longer reports a run as clean when it never ran, was cut short or was only partly
instrumented.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;No C/C++ tool can end your turn or hang it any more.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A misnamed argument is refused with a clear message instead of being silently ignored.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;cpp_perf&lt;/code&gt;, &lt;code&gt;cpp_bench&lt;/code&gt;, &lt;code&gt;cpp_sanitize&lt;/code&gt; and &lt;code&gt;cpp_layout&lt;/code&gt; give more precise results.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Security: the debug tools refuse commands that could run programs on your machine without
your approval, and a function name passed to &lt;code&gt;cpp_decompile&lt;/code&gt; can no longer run commands.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Other changes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;&lt;code&gt;/model&lt;/code&gt; is now three short steps:&lt;/strong&gt; provider, then model, then reasoning effort.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;When your free messages run out,&lt;/strong&gt; the sign-in prompt opens by itself. Type your email; you
no longer need to type &lt;code&gt;/login&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;The first-run setup menu&lt;/strong&gt; lists &lt;em&gt;Use ByteAsk managed (recommended)&lt;/em&gt; first, already selected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Settings you set with &lt;code&gt;byteask features&lt;/code&gt;&lt;/strong&gt; now survive signing in, signing out and
switching between ByteAsk, your own keys and a subscription.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Update prompt:&lt;/strong&gt; an interactive launch asks &lt;em&gt;Update now? [Y/n]&lt;/em&gt; again when a new version is
out.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The model list refreshes on every launch, including before you sign in.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Conversation titles and catch-up summaries use a small, fast model.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p class="bx-changelog-trim"&gt;&lt;a href="https://github.com/ByteAsk/cli/releases/tag/v0.1.15" rel="noopener"&gt;Read the full release notes&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.14</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.14</link>
      <guid isPermaLink="false">v0.1.14</guid>
      <pubDate>Wed, 23 Sep 2026 16:25:17 GMT</pubDate>
      <description>&lt;h1&gt;ByteAsk CLI 0.1.14&lt;/h1&gt;
&lt;p&gt;The previous release was 0.1.13 on 20 September. This one rebuilds the engine on all four
platforms.&lt;/p&gt;
&lt;p&gt;Update with &lt;code&gt;byteask --update&lt;/code&gt;, or &lt;code&gt;pip install -U byteask&lt;/code&gt;, or &lt;code&gt;npm i -g @byteask/cli&lt;/code&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;Use your ChatGPT subscription&lt;/h2&gt;
&lt;p&gt;ByteAsk can run on a ChatGPT &lt;strong&gt;Plus&lt;/strong&gt; (or higher) subscription instead of ByteAsk credits.
Choose it from &lt;code&gt;/login&lt;/code&gt;. This option is being switched on in stages over the coming days, so
you may not see it yet.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Sign-in happens in a pane inside ByteAsk. When it finishes or you press &lt;code&gt;esc&lt;/code&gt;, the pane
closes and leaves nothing behind in your terminal.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;ChatGPT &lt;strong&gt;Free&lt;/strong&gt; and &lt;strong&gt;Go&lt;/strong&gt; plans are refused at sign-in with a clear message, because OpenAI
serves no coding models on them. The refusal happens before anything is saved, so an
existing sign-in is kept. From the refusal screen you can try a different account or go back.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;To switch back, use &lt;code&gt;/login&lt;/code&gt; and choose &lt;em&gt;Use ByteAsk managed&lt;/em&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Fixes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Questions about ByteAsk itself are now answered from ByteAsk&amp;#39;s documentation.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The &lt;code&gt;Token usage: …&lt;/code&gt; line no longer prints when a session ends.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The background app-server no longer tries to install or update another product.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The browser pages at the end of a sign-in, and the device-code screen, now show ByteAsk
branding.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p class="bx-changelog-trim"&gt;&lt;a href="https://github.com/ByteAsk/cli/releases/tag/v0.1.14" rel="noopener"&gt;Read the full release notes&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.13</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.13</link>
      <guid isPermaLink="false">v0.1.13</guid>
      <pubDate>Sun, 20 Sep 2026 20:37:10 GMT</pubDate>
      <description>&lt;h1&gt;ByteAsk CLI 0.1.13&lt;/h1&gt;
&lt;p&gt;The previous release was 0.1.12 on 8 September. This one rebuilds the engine on all four
platforms.&lt;/p&gt;
&lt;p&gt;Update with &lt;code&gt;byteask --update&lt;/code&gt;, or &lt;code&gt;pip install -U byteask&lt;/code&gt;, or &lt;code&gt;npm i -g @byteask/cli&lt;/code&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;Less noise in the model&amp;#39;s context&lt;/h2&gt;
&lt;p&gt;Command output is now cleaned before the model reads it. Colour codes and progress-bar
redraws are removed, repeated lines are folded into a count, and long build, install and
test logs keep every warning, error and summary line while the routine lines are counted.
The full original output is always saved on your machine, and the model can open it when it
needs a line that was folded away. What you see in your own terminal does not change.&lt;/p&gt;
&lt;p&gt;ByteAsk can also read several files, or several ranges of one file, in a single step, and
search with context lines, instead of one shell command per file.&lt;/p&gt;
&lt;p&gt;Long sessions hold up better after the history is compacted: the agent keeps a note of the
files it had open and its most recent results, so it does less re-exploring.&lt;/p&gt;
&lt;h2&gt;C and C++&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;cpp_sanitize&lt;/code&gt; accepts &lt;code&gt;sanitizer: &amp;quot;tsan&amp;quot;&lt;/code&gt;, so data races can be found. It can also build
your project&amp;#39;s own CMake or Make target with sanitizers on, so a multi-file program no
longer needs every source file listed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;On macOS a clean sanitizer run now says that leaks were not checked (LeakSanitizer does
not exist on macOS). It used to read as a clean result.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;debug_record&lt;/code&gt; (rr) handles bugs that fail one run in twenty: it can record under rr&amp;#39;s
chaos scheduler until a run fails and then replay that run, including backwards. When rr
cannot work on a machine it says why, and what to use instead.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;cpp_symbolize&lt;/code&gt; resolved caller frames to the wrong line. Fixed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;cpp_layout&lt;/code&gt; reported nested members of unknown size as padding. Fixed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;cpp_godbolt&lt;/code&gt; could pick the wrong compiler for a request like &amp;quot;clang 18&amp;quot;. Fixed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;cpp_binary&lt;/code&gt; can explain a link failure caused by a libstdc++ ABI mismatch, and its
header view shows the NX and RELRO state.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;cpp_compile_db&lt;/code&gt; can generate &lt;code&gt;compile_commands.json&lt;/code&gt; for Makefile projects.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A Python project with a Makefile no longer gets the C/C++ guidance, and a repository
whose C++ sits several folders down now does.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;debug_attach&lt;/code&gt; no longer offers a gdb session that has already exited.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Account and updates&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;/upgrade&lt;/code&gt;: on a Pro plan the arrow keys did not move. Fixed; Pro can be renewed from
the picker.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;/usage&lt;/code&gt; shows your plan in its title.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The update check now reads ByteAsk&amp;#39;s own feed, and it is on. It had been off since the
first release.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The referral programme no longer grants a free Pro month, and the footer and hints that
still mentioned it are gone. Referral credit is unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The plugin marketplace is off by default. &lt;code&gt;features.plugins = true&lt;/code&gt; in
&lt;code&gt;~/.byteask/config.toml&lt;/code&gt; turns it back on.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;/export&lt;/code&gt; suggested a file name that was not ours. It now suggests &lt;code&gt;byteask-session.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Old state from before the rename is cleared from &lt;code&gt;~/.byteask&lt;/code&gt; on launch. Your sign-in,
settings and history are kept.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p class="bx-changelog-trim"&gt;&lt;a href="https://github.com/ByteAsk/cli/releases/tag/v0.1.13" rel="noopener"&gt;Read the full release notes&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.12</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.12</link>
      <guid isPermaLink="false">v0.1.12</guid>
      <pubDate>Tue, 08 Sep 2026 13:11:36 GMT</pubDate>
      <description>&lt;h1&gt;ByteAsk CLI 0.1.12&lt;/h1&gt;
&lt;p&gt;The previous release was 0.1.11 on 30 July. This one rebuilds the engine on all four
platforms and carries six weeks of our own work plus a large upstream merge.&lt;/p&gt;
&lt;p&gt;Update with &lt;code&gt;byteask --update&lt;/code&gt;, or &lt;code&gt;pip install -U byteask&lt;/code&gt;, or &lt;code&gt;npm i -g @byteask/cli&lt;/code&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;Your transcript stays yours&lt;/h2&gt;
&lt;p&gt;&lt;code&gt;/usage&lt;/code&gt;, &lt;code&gt;/referral-code&lt;/code&gt;, &lt;code&gt;/upgrade&lt;/code&gt; and &lt;code&gt;/voucher&lt;/code&gt; used to print into your terminal&amp;#39;s
real scrollback. Checking your quota wedged a dashboard permanently into the middle of
your conversation, and nothing could take it back.&lt;/p&gt;
&lt;p&gt;They are panes now, like &lt;code&gt;/model&lt;/code&gt;. They open over the composer, and &lt;code&gt;esc&lt;/code&gt; closes them and
leaves the transcript exactly as it was.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;enter&lt;/code&gt; never closes a pane. It only does what the footer says, so muscle memory trained
by &lt;code&gt;/usage&lt;/code&gt; cannot fire a payment link on &lt;code&gt;/upgrade&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The operator announcement banner is gone for the same reason. It inserted itself at the
top of every session and, being scrollback, could not be dismissed.&lt;/p&gt;
&lt;h2&gt;&lt;code&gt;/usage&lt;/code&gt; tells you more, and tells the truth&lt;/h2&gt;
&lt;p&gt;The meters are twice the resolution and now show when each window resets.&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;5-hour  ████████████████░░░░  82%   resets in 47m
Weekly  ██████░░░░░░░░░░░░░░  31%   resets in 6d 23h
Extra   $12.00 left of $15.00 · covers spend past your limits
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Plan pricing used to read &amp;quot;$20/month&amp;quot;. That was wrong. We sell a one-time 30-day pass, and
the pane now says so: &lt;strong&gt;one payment for 30 days, no auto-renew, your plan switches as soon
as payment completes.&lt;/strong&gt; Your current plan is marked in the list.&lt;/p&gt;
&lt;p&gt;Our pricing page still describes a monthly subscription. The page is what is out of date,
and we are fixing it.&lt;/p&gt;
&lt;h2&gt;You will stop being logged out&lt;/h2&gt;
&lt;p&gt;If you were ever stuck behind &lt;code&gt;Reconnecting… 4/5&lt;/code&gt; with no explanation, this is the release
that fixes it.&lt;/p&gt;
&lt;p&gt;Sessions lasted 30 days and nothing renewed them. When yours expired, the client kept
sending the dead credential, and running &lt;code&gt;/login&lt;/code&gt; could appear to succeed while the new
credential silently failed to save. One account sat locked out for six weeks.&lt;/p&gt;
&lt;p&gt;Your session now renews itself quietly at launch, well before it expires. Anyone already
expired is healed on their next launch with no email round-trip. Renewal edits only the
credential, so your trusted projects, reasoning effort and configured tools all survive
it. And a credential that cannot be written now says so loudly instead of reporting
success.&lt;/p&gt;
&lt;h2&gt;Errors say what happened, immediately&lt;/h2&gt;
&lt;p&gt;Every unexpected response used to be treated as temporary. A &amp;quot;please sign in&amp;quot; or a plan
limit would spin &lt;code&gt;Reconnecting…&lt;/code&gt; for about six seconds and then be replaced by a generic
retry error, so you never saw the sentence that told you what to do.&lt;/p&gt;
&lt;p&gt;Only genuine server errors and rate limits retry now. Everything else is shown at once, in
our words. A failed payment link is one line telling you to contact us, rather than an
internal cause you cannot act on.&lt;/p&gt;
&lt;h2&gt;Models&lt;/h2&gt;
&lt;p&gt;The picker shows 20 models, up from 18, with nine new ones. &lt;code&gt;auto&lt;/code&gt; is now a chain across
three models and two providers rather than a single fixed choice, so if one is having a
bad day your turn quietly lands on the next. Its first choice also got five times cheaper.&lt;/p&gt;
&lt;p&gt;Model descriptions were rewritten so that &amp;quot;fast&amp;quot;, &amp;quot;balanced&amp;quot; and &amp;quot;deep&amp;quot; mean the same thing
everywhere, instead of each vendor&amp;#39;s marketing language.&lt;/p&gt;
&lt;p&gt;Anthropic models are currently out of service and hidden.&lt;/p&gt;
&lt;h2&gt;Accessibility&lt;/h2&gt;
&lt;p&gt;A screen-reader mode renders panes as linear, announce-once text instead of in-place
repaints, and substitutes a plain symbol set when your terminal is not UTF-8. Turn it on
with &lt;code&gt;--ax-screen-reader&lt;/code&gt;, the &lt;code&gt;BYTEASK_AX_SCREEN_READER&lt;/code&gt; environment variable, or
&lt;code&gt;tui.screen_reader&lt;/code&gt; in your config.&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;From upstream&lt;/h2&gt;
&lt;p&gt;We merged roughly 2,000 commits of upstream work. The parts you will notice:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;New commands.&lt;/strong&gt; &lt;code&gt;/recap&lt;/code&gt; summarizes the conversation on demand. &lt;code&gt;/cd&lt;/code&gt; and &lt;code&gt;/pwd&lt;/code&gt; change
and show the working directory mid-conversation. &lt;code&gt;/agents&lt;/code&gt; opens a command center grouping
your agent sessions into needs-input, working, ready and finished. &lt;code&gt;/copy&lt;/code&gt; can now target
the last code block or quote, not just the whole response.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;New subcommands.&lt;/strong&gt; &lt;code&gt;byteask queue --thread &amp;lt;session&amp;gt; --message &amp;quot;…&amp;quot;&lt;/code&gt; sends a message into
a running session from another terminal. &lt;code&gt;byteask agents&lt;/code&gt; browses sessions across the
local daemon.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sessions reconnect themselves&lt;/strong&gt; when a connection drops, instead of dying and taking your
draft with it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;code&gt;/keymap&lt;/code&gt; can genuinely rebind keys now&lt;/strong&gt;, including two-key chords like &lt;code&gt;g g&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Links in model output are clickable&lt;/strong&gt; where your terminal supports it, including local
file paths that keep their line and column.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Vim mode gained&lt;/strong&gt; undo and redo, dot-repeat, search motions, and character find.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The model can ask you structured questions&lt;/strong&gt; - a small form with options rather than only
free text - and &lt;code&gt;/status&lt;/code&gt; now shows this thread&amp;#39;s token usage.&lt;/p&gt;
&lt;h3&gt;Two changes worth reading before you update&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;An auto-reviewer can now approve some risky actions without asking you, and it is on by
default.&lt;/strong&gt; The permission menu offers an explicit choice between &amp;quot;Approve for me&amp;quot; and &amp;quot;Ask
for approval&amp;quot;, and anything auto-denied is labelled in your approval history. If you want
to be asked about everything, choose &amp;quot;Ask for approval&amp;quot;. Relatedly, what counts as
auto-approvable under &amp;quot;ask only when needed&amp;quot; is now decided by explicit rules rather than a
built-in guess about which commands are safe.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;code&gt;byteask exec --full-auto&lt;/code&gt; has been removed.&lt;/strong&gt; It was deprecated with a warning in
0.1.11; it is now an error. Use &lt;code&gt;--sandbox workspace-write&lt;/code&gt;. If you have scripts passing
it, they will fail on this version.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;byteask mcp-server&lt;/code&gt; now warns that it is deprecated. It still works.&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;Under the hood&lt;/h2&gt;
&lt;p&gt;Our C/C++ and reference tools are no longer exposed to the internal thread that
summarizes your conversation. Upstream strips every tool from that thread because a
summarization prompt can contain untrusted text from your transcript; ours had no way to
be stripped, which meant tools that compile and run your code, and tools that make network
calls, were reachable from it. They are now excluded before that thread reads anything.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;/referral-code&lt;/code&gt; prints all three share commands complete, rather than one whole and one
truncated. The installer tells you if a referral code was rejected instead of failing
silently, and reports where it put things and whether your PATH needs a change.&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;Known issues&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Upgrading is currently failing.&lt;/strong&gt; Our payment provider began requiring a contact number
we do not collect. Everything else works normally. Email &lt;a href="mailto:contact@byteask.ai"&gt;contact@byteask.ai&lt;/a&gt; and we will
sort your plan out directly.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The update prompt still blocks startup with a yes/no question. It should be a line you
can ignore, and will be.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The pricing page still describes a monthly subscription rather than the 30-day pass we
actually sell.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.11</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.11</link>
      <guid isPermaLink="false">v0.1.11</guid>
      <pubDate>Thu, 30 Jul 2026 19:05:09 GMT</pubDate>
      <description>&lt;p&gt;ByteAsk CLI v0.1.11&lt;/p&gt;
&lt;p&gt;Highlights:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Operator alerts rendered at the top of the session&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;/login&lt;/code&gt; rebuilt as a native bottom-pane settings surface&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;byteask exec&lt;/code&gt; now renders extension tool calls (cpp_*/ref_*) - previously invisible&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;cpp-tools: real sanitizer output, project builds, bounded execution, trust gate&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Hardware-aware performance verification&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p class="bx-changelog-trim"&gt;&lt;a href="https://github.com/ByteAsk/cli/releases/tag/v0.1.11" rel="noopener"&gt;Read the full release notes&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.10</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.10</link>
      <guid isPermaLink="false">v0.1.10</guid>
      <pubDate>Thu, 23 Jul 2026 11:54:53 GMT</pubDate>
      <description>&lt;h2&gt;What&amp;#39;s new&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Status/result messages (e.g. key-add errors) no longer leak onto unrelated screens after navigating away.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;install.sh / install.ps1 now say plainly when a best-effort ripgrep install didn&amp;#39;t work, instead of failing silently.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All 4 platform binaries included below.&lt;/p&gt;

&lt;p class="bx-changelog-trim"&gt;&lt;a href="https://github.com/ByteAsk/cli/releases/tag/v0.1.10" rel="noopener"&gt;Read the full release notes&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.9</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.9</link>
      <guid isPermaLink="false">v0.1.9</guid>
      <pubDate>Sat, 18 Jul 2026 10:08:07 GMT</pubDate>
      <description>&lt;h2&gt;ByteAsk CLI v0.1.9&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Security &amp;amp; abuse-resistance hardening.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Engine unchanged from 0.1.8 - the binaries below are identical; 0.1.9 ships client + gateway improvements.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Install:&lt;/strong&gt; &lt;code&gt;curl -fsSL https://code.byteask.ai/install.sh | sh&lt;/code&gt;  ·  &lt;code&gt;pip install byteask&lt;/code&gt;  ·  &lt;code&gt;npm i -g @byteask/cli&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Binaries are gzip-compressed; &lt;code&gt;SHA256SUMS&lt;/code&gt; lists the checksums.&lt;/p&gt;

&lt;p class="bx-changelog-trim"&gt;&lt;a href="https://github.com/ByteAsk/cli/releases/tag/v0.1.9" rel="noopener"&gt;Read the full release notes&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.8</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.8</link>
      <guid isPermaLink="false">v0.1.8</guid>
      <pubDate>Wed, 15 Jul 2026 20:18:45 GMT</pubDate>
      <description>&lt;h2&gt;ByteAsk CLI v0.1.8&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;See your tools working&lt;/strong&gt; - every ByteAsk tool call (&lt;code&gt;autosar_ref&lt;/code&gt;, &lt;code&gt;mcu_ref&lt;/code&gt;, &lt;code&gt;cpp_godbolt&lt;/code&gt;, &lt;code&gt;debug&lt;/code&gt;, …) now shows a live cell in the TUI with the tool name, arguments, and result - the same visibility web search always had. Interrupted calls show cleanly; retryable tool replies no longer render as failures.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Referral upgrades&lt;/strong&gt; - you AND your friend now each get $10 of usage per referral, and &lt;strong&gt;3 successful referrals earn your first month of Pro free&lt;/strong&gt;. &lt;code&gt;/referral-code&lt;/code&gt; shows your live progress.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Reliability: turn-abort no longer leaves stuck in-progress items in thread history.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Install:&lt;/strong&gt; &lt;code&gt;curl -fsSL https://code.byteask.ai/install.sh | sh&lt;/code&gt;  ·  &lt;code&gt;pip install byteask&lt;/code&gt;  ·  &lt;code&gt;npm i -g @byteask/cli&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Binaries are gzip-compressed; &lt;code&gt;SHA256SUMS&lt;/code&gt; lists the checksums.&lt;/p&gt;
</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.7</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.7</link>
      <guid isPermaLink="false">v0.1.7</guid>
      <pubDate>Wed, 15 Jul 2026 10:13:07 GMT</pubDate>
      <description>&lt;h2&gt;ByteAsk CLI v0.1.7&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Grounded reference tools&lt;/strong&gt; - &lt;code&gt;autosar_ref&lt;/code&gt;, &lt;code&gt;mcu_ref&lt;/code&gt;, &lt;code&gt;fpga_ref&lt;/code&gt;, &lt;code&gt;hft_ref&lt;/code&gt;, &lt;code&gt;grid_ref&lt;/code&gt;, &lt;code&gt;scpi_ref&lt;/code&gt;, &lt;code&gt;x86_ref&lt;/code&gt;: page-cited lookups over the ByteAsk corpus for embedded / firmware / hardware / safety-critical C++ (MISRA, AUTOSAR, Intel SDM, IEEE 1547, SCPI, Xilinx, ITCH, and more).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Renamed the native-debugger tools&lt;/strong&gt; - &lt;code&gt;cpp_debug&lt;/code&gt;/&lt;code&gt;cpp_debug_session&lt;/code&gt;/&lt;code&gt;cpp_debug_attach&lt;/code&gt;/&lt;code&gt;cpp_record&lt;/code&gt; → &lt;code&gt;debug&lt;/code&gt;/&lt;code&gt;debug_session&lt;/code&gt;/&lt;code&gt;debug_attach&lt;/code&gt;/&lt;code&gt;debug_record&lt;/code&gt; (they debug any native binary, including Rust).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Removed&lt;/strong&gt; the &lt;code&gt;/app&lt;/code&gt; slash command.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Gateway maintenance: &lt;code&gt;auto&lt;/code&gt; model routing, Gemini/Anthropic reliability fixes.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Install:&lt;/strong&gt; &lt;code&gt;curl -fsSL https://code.byteask.ai/install.sh | sh&lt;/code&gt;  ·  &lt;code&gt;pip install byteask&lt;/code&gt;  ·  &lt;code&gt;npm i -g @byteask/cli&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Binaries below are gzip-compressed; &lt;code&gt;SHA256SUMS&lt;/code&gt; lists the checksums.&lt;/p&gt;
</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.6</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.6</link>
      <guid isPermaLink="false">v0.1.6</guid>
      <pubDate>Mon, 13 Jul 2026 13:37:30 GMT</pubDate>
      <description>&lt;p&gt;ByteAsk CLI v0.1.6 - fixes API-key paste hanging on macOS Terminal (wrapper terminal-reset). Engine binaries unchanged from v0.1.5.&lt;/p&gt;
</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.5</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.5</link>
      <guid isPermaLink="false">v0.1.5</guid>
      <pubDate>Mon, 13 Jul 2026 12:44:48 GMT</pubDate>
      <description>
&lt;p class="bx-changelog-trim"&gt;&lt;a href="https://github.com/ByteAsk/cli/releases/tag/v0.1.5" rel="noopener"&gt;Read the full release notes&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.4</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.4</link>
      <guid isPermaLink="false">v0.1.4</guid>
      <pubDate>Tue, 07 Jul 2026 13:59:30 GMT</pubDate>
      <description>&lt;p&gt;ByteAsk CLI v0.1.4 - Gemini/Anthropic fixes (CRLF SSE, tool-schema, thought-signature), gateway model allowlist, Linux bubblewrap auto-install + sandbox fallback, referral across curl/pip/npm, catalog trim (Sonnet 4.5 removed).&lt;/p&gt;
</description>
    </item>
    <item>
      <title>ByteAsk CLI v0.1.3</title>
      <link>https://github.com/ByteAsk/cli/releases/tag/v0.1.3</link>
      <guid isPermaLink="false">v0.1.3</guid>
      <pubDate>Mon, 06 Jul 2026 08:53:57 GMT</pubDate>
      <description>&lt;p&gt;ByteAsk CLI v0.1.3 - the AI coding agent for your terminal.&lt;/p&gt;
&lt;p&gt;Engine binaries for all supported platforms are attached below; installers fetch the latest automatically.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Install&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;macOS / Linux: &lt;code&gt;curl -fsSL https://code.byteask.ai/install.sh | sh&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Windows (PowerShell): &lt;code&gt;irm https://code.byteask.ai/install.ps1 | iex&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;code&gt;pip install byteask&lt;/code&gt;  ·  &lt;code&gt;npx @byteask/cli&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Verify downloads against &lt;code&gt;SHA256SUMS&lt;/code&gt;.&lt;/p&gt;
</description>
    </item>
  </channel>
</rss>
