Changelog

What shipped. Every week, in plain words.

New features and improvements across ReasonOS, newest first.

September 2026

  1. Every click drawn on the page, and a design reviewer on every screen

    Open any step of a QA run to see exactly where the agent clicked, drawn on the page it clicked, with a crop of the element beside each action. A design reviewer looks at every screen the run visits and flags what a top-tier team would not ship — misrendered or misaligned elements, confusing flows, sloppy copy — as findings beside the step, numbered on the page. Requests open to their headers, bodies and timing, and each step keeps its console, its document and the browser’s load.

    Learn more →
  2. AI orchestration for role-based agent teams

    Set up Design, Risk Assessment, Impact Analysis, Code, Test Generation, Code Review and AI Test & Iteration roles. Assign primary agents and independent reviewers, keep people at decision gates, preserve workflow evidence, and compare recorded outcomes.

    Learn more →
  3. A step-by-step view of every QA run

    Open any run to see each step’s outcome, its retries and which steps were reused from a previous run. Repeat runs of the same test now behave the same way.

    Learn more →
  4. Claude Code, Codex and Gemini in the editor

    Chat with Claude Code, Codex or Gemini inside a branch, approve their actions as they work, and set a default agent for each project.

    Learn more →
  5. A guided start for QA

    A setup guide, a test picker and a live replay make it quicker to write your first tests and watch them run.

    Learn more →
  6. Bring your own AI subscription

    Link your own Claude, ChatGPT or Google account, or give a project its own API keys, so agents run on the plan you already pay for. Keys are encrypted and never reach a branch.

    Learn more →
  7. Email notifications

    Hear when a CI run finishes, a review or merge happens, a QA suite settles, someone mentions or assigns you, or opens a document you shared. Choose what you get in Settings.

  8. Page previews for documents

    Uploaded decks and documents now render page by page, so readers never need to download a file.

    Learn more →
  9. Document library, share links and data rooms

    Keep a shared library, send a link per recipient, build data rooms, and give people access to documents without access to code.

    Learn more →
  10. Guided tours inside the product

    Built-in walkthroughs cover the platform, stacked changes, working together in a branch and reliable builds.

  11. Bring a repository, build it with no setup

    Import an existing repository and run, build and test it without writing any build files first.

    Learn more →
  12. Required two-factor sign-in

    Organizations now require an authenticator app by default, and admins can cap how long a branch’s credentials last.

  13. Workspace activity log

    Owners and admins can browse and filter every sign-in, push, merge, permission change and secret change in one log.

August 2026

  1. A shared build cache

    Builds reuse results a teammate, an agent or CI already produced, and each project shows how much the cache saved.

    Learn more →
  2. Agentic QA

    Write tests as plain sentences. An agent runs them in a real browser with recordings, screenshots of every step, test personas and saved sign-in states.

    Learn more →
  3. Issues, cycles and initiatives

    Plan work next to the code: issues link to their branch and review, cycles track progress, and initiatives group the bigger bets.

    Learn more →
  4. Ask your codebase a question

    A map of your code, built without sending it to a model: ask where something happens, see who calls it and what a change would touch.

    Learn more →
  5. Custom roles, teams and managed secrets

    Write roles from allow and deny rules, grant them to nested teams, and keep secrets encrypted and scoped to a project or an environment.

  6. Branch rules with required checks

    Protect branches: require reviews, passing CI and QA checks, linear history or signed commits before anything merges.

    Learn more →
  7. Stacked reviews

    Split a large change into small ones that are reviewed separately and land in order.

    Learn more →