The latest release
More focused approvals, better context and safer restores
New capabilities 3
-
Focused approvals instead of repeated prompts
Recurring test, build and development commands can be approved with an appropriate argument scope. The dialog shows the complete rule before you agree. Exact, one-time approval remains available for other invocations.
-
Trust mode directly in VS Code
You can now enable or disable trust mode in the VS Code extension and see its current state. Enabling it requires explicit risk confirmation: it reduces normal approval prompts but does not provide an isolated execution environment.
-
From the dashboard to your first project
The new quickstart walks you through CLI installation, sign-in and starting in your own project. It also explains how to set up the VS Code extension, including its CLI requirement.
Refinements 5
-
Updated model selection
Model selection has been expanded and updated, including Claude Opus 5.5, Claude Sonnet 5.5, GPT-6.1 Sol and Lura. Available models still depend on your plan and team access policies.
-
Less repetition during longer tasks
Recorded findings and decisions from earlier tasks can be retrieved selectively within a session. Unchanged file excerpts already retained in context are reused; overlapping reads add only the missing ranges.
-
More trial credit with a clear scope
Credit for new trials has doubled: €10 for Pro, €15 for Pro+ and €20 for Ultra. Model selection during the trial is limited to Lura; image and video generation are not available during the trial.
-
Review existing permission rules when upgrading
Configured approvals are presented for renewed review at startup. New Bash(path) rules apply to script and executable entrypoints; use CommandCwd(path) for working-directory approvals. Stored legacy approvals keep their previous meaning. Settings are not rewritten automatically.
-
General improvements
Further stability and security improvements, updated dependencies and more reliable CLI and VS Code extension publishing.
Reliability & fixes 3
-
Checkpoints leave unrelated files alone
Restoring a checkpoint now restores only the files involved in the changes being rolled back. Other project files are preserved. Checkpoint compatibility on Windows has also been improved. Checkpoints cover native file changes, not every side effect of shell commands.
-
More reliable plan continuation and completion
Implementation plans are now bound more reliably to their task. Plans and progress stay more consistent when activating and continuing work; completion takes recorded verification results into account.
-
Fewer interruptions during browser checks
Browser sessions now remain available for up to 15 minutes without activity. Saving screenshots correctly respects the configured project directory and permitted temporary locations.