File contents are visible again
Code stopped showing up. A tool call in chat would render its header —
create_pcb.py +2 −3 — and then nothing underneath. Opening a file beside the
Preview panel gave a blank pane. The file was fine and the edit had been made;
you just could not see any of it.
The syntax highlighter compiles a small WebAssembly module, and a security
policy added back in 0.1.0-beta.8 was refusing to let it. Everything that
depends on highlighting — diffs, the file viewer, code blocks — therefore
painted nothing at all. It only ever happened in the installed app, never in
development, which is why it went unnoticed for five releases.
Fixed by permitting WebAssembly specifically. Nothing else was loosened.
The advisor stops going "unavailable" mid-session
Each agent consults a stronger model — Claude Sonnet 5 or Kimi K3 — for
planning and review. After a handful of turns it would start answering
"Advisor is unavailable" and never recover, even though the advisor itself
was up.
There is a per-session limit on how many consults an agent may make, and failed
attempts were being charged against it. So a brief upstream hiccup could quietly
spend the whole allowance, and the advisor stayed switched off for the rest of
that session. Only successful consults are counted now, and the allowance itself
is larger. If you do reach it, the message says so plainly instead of implying an
outage.
Long sessions cost less and stay quicker
A session's history was only ever summarised when it neared the model's absolute
limit — around a million tokens. In practice that never happened, so a long day's
work kept re-sending an ever-growing transcript with every single message.
History is now condensed once a session gets genuinely large, at a natural pause
between tasks rather than in the middle of one. Long sessions get noticeably
cheaper to keep going, and the agent's memory of what it is doing is unaffected.
Upgrading
Install over your current version — your projects, settings and sign-in are kept.
Known issue
Requests can occasionally be blocked by the network layer in front of our API,
surfacing as "Forbidden: request was blocked by a gateway or proxy." It is
not your account and not your credentials — signing out will not help. It is
being raised with the hosting provider; starting a fresh session is the current
workaround.