September 2026

Approve a milestone's cost before it runs

Starting a milestone now opens a short confirmation that shows the estimated credits and, when the work would go beyond your monthly allotment, the exact dollar amount.

Milestones that fit within your included credits start for free; anything that would incur overage runs only after you approve the charge. Nothing bills silently. Credits are deducted when the milestone's pull request is created.

This applies to plans on the credit-based billing model; some organizations, such as self-managed deployments, don't see the confirmation step.

Edit approved project specs

Approving a Project Spec no longer locks it. You can keep refining an approved spec with Knowledge chat, adjusting its prose or repository topology, the same way you did before approval.

If milestone planning has already run, your edits apply to future milestones only; the source repositories chosen at project creation stay fixed.

Code review: tags, effort estimates, and frontend tests

The Code Review drawer gained three things:

• Issue tags: create and assign tags to review issues from the issue card, then filter and group the list by them.
• Effort estimates: issues the review agent has sized show a T-shirt-size badge (XS–XL), so you can triage by how much work each one is.
• Run the frontend tests from chat: on projects with a frontend, ask the chat to run or re-run the milestone's Playwright suite, for example after it fixes a UI bug. Results and screenshots refresh in the drawer's Validation tab when the run finishes.

Run a single milestone at Low validation

When one milestone is expensive to validate, such as a slow or unreliable app runtime, you can run that milestone only at the Low level without changing the project setting.

Open the caret beside Approve & Start in Project Knowledge and choose Start With Low Validation. Run an ad-hoc validation after the PR merges to cover the project's real level.