Ship log

Ship notes describe what changed in Critique and what operators and reviewers should notice—plain language, no fluff. Newest releases appear first.

May 2026 — Model catalog refresh across Chat, review, and Remedy

At a glance

• The public model catalog now reflects the new routing ladder: Grok 4.3 replaces the older Grok slot at a lower floor, Qwen3.6-35B-A3B replaces the retired Qwen3.5-27B lane, Ling-2.6-Flash joins as a new 1-credit fast agent model, and Qwen3.6-Max-Preview joins as the higher-end Alibaba lane.
• Pricing moved in both directions to match current shelf reality: GLM-5.1 dropped by 1 credit, MiMo v2.5 rose by 1 credit, and KAT Coder Pro V2 returned to its normal 2-credit price after a month-long discounted partnership window.
• Critique Chat’s picker was cleaned up to match the intended free-chat roster, and saved defaults pointing at removed Chat IDs remap automatically so existing threads reopen without manual repair.

May 2026 — Speech input across Chat and Builder

At a glance

• Critique Chat voice input now runs through OpenRouter's dedicated speech-to-text path instead of a conversational audio workaround, which makes transcription behavior simpler and easier to track.
• Builder now has the same microphone capture flow as Chat, so operators can dictate a build prompt directly into the workspace composer before launching a run.
• Speech transcription responses now carry the provider generation identifier alongside the transcript, which gives operators and support a cleaner handle for tracing voice requests.

May 2026 — Repository map intelligence, usage clarity, and snapshot-first dashboards

At a glance

• The dashboard repository vector map now reads like an architecture brief: it highlights central nodes, fan-out risk, isolated files, and test relationships, and a Signals panel calls out why parts of the topology matter—not only that they exist.
• Act on this map connects the graph to the rest of Critique: open a node or neighborhood in Chat with a prefilled prompt, copy an agent handoff, or export JSON, Markdown, agent handoff text, or DOT/Graphviz for tools outside the app.
• From the same view you can run GitHub-oriented actions—copy review-ready Markdown, draft an issue from the selection, or attach the selected context to a PR by number—without losing map context.
• The usage area emphasizes managed execution instead of raw provider plumbing; hidden model visibility rules are respected, and charts and labels resolve to catalog display names where Critique has them.
• PR reviews now support a clearer premium-first path: when a repository is set to Auto or Premium OpenCode Review, Critique attempts the full OpenCode-led audit first, falls back to the collector-backed review path if that premium run fails, and labels the resulting review authority so operators can tell whether the output came from native OpenCode, collector fallback, or backend-only synthesis.
• Metering and credits now line up with how reviews actually run: multi-pass work (reasoning plus structured output) rolls into one honest usage picture, OpenRouter-style native and reasoning token fields parse consistently, sandbox and OpenCode completions surface customer-safe labels, and credits no longer snap tiny when a large uncataloged-token call would warrant more—legacy rows can correct upward when token evidence shows they were too low. Assistant and fix-prompt traffic now leaves durable usage records.
• OpenRouter traffic defaults site attribution to Critique’s public home, and review calls send the current attribution headers expected by the provider.
• Dashboard GitHub data defaults to persisted snapshots in Critique: full reconciliation runs after Connect or Re-Sync repositories, not on ordinary loads of usage analytics or review-run detail—the UI states that repository access stays cached until you re-sync.

April 2026 — PR review runtime unification and live-run clarity

At a glance

• PR review routing now separates OpenCode agent, Collect sandbox, and GitHub-backed review types so operators can choose the exact backend and understand whether an agent stream should exist.
• OpenCode agent reviews now start from a single sandbox path: Critique prepares the PR context, launches the OpenCode audit, streams the run, and consumes the final review output without a separate collector sandbox blocking the agent.
• Review usage and live-run diagnostics are more accountable: token-bearing calls no longer display zero credits from legacy rows, and sandbox setup or failure events remain visible even when the agent never reaches a rich tool stream.

April 2026 — OpenCode operator hardening for longer review sessions

At a glance

• The live review stream is easier to read at a glance: tool calls, thinking, and assistant messages now surface with clearer tags and cleaner output, and the dashboard shows whether the sandbox, OpenRouter, and QStash prerequisites are ready.
• Long-running sandbox reviews now recover more gracefully when the agent goes quiet. Critique can send a follow-up into the same OpenCode session, and if the sandbox stalls entirely, the review can fall back to the backend publish path instead of dying silently.
• Review prompts now push for deeper autonomous work by default: Critique expects subagents to be used early on non-trivial changes, avoids permission-seeking loops, and treats missing env-dependent validation as a cue to switch to targeted checks instead of stalling.

April 2026 — Workspace Build: branch-aware sandboxes and the full Builder model roster

At a glance

• Build mode in /workspace now offers searchable repository and model pickers; models come from the same remedy / Builder catalog as /builder, filtered by the selected repo’s plan (ultra-only checkpoints stay ultra-only).
• You can choose a Git branch or tag (GitHub-backed list plus manual ref), optionally set a sandbox-only branch (git checkout -b) before OpenCode runs, and those choices persist on the Builder job record for later inspection.
• The builder execution path checks out the requested ref in E2B, then creates the local work branch when provided—still no automatic push to GitHub; PR flow stays manual.

April 2026 — Transparent automation credits end to end

At a glance

• Usage analytics now reconcile OpenRouter-style payloads (including nested cache fields) across review, remedy, sandbox OpenCode completions, and builder jobs so token math and credits derive from identical inputs.
• The automation ledger separates review-agent, remedy, and builder rows; each exposes prompt versus completion totals, billed credits, latency, and textual purpose fields so accountants can chase down the exact workload.
• When sandbox PR reviews emit granular OpenRouter completions, aggregated lead rows skip double-accounting—the quota matches one OpenRouter session on the bookkeeping side while granular rows carry the explanatory trail.