Skip to main content

Changelog

User-facing changes to Hyrax — things you'd notice in the product.

November 17, 2026​

  • API note. Reading change reviews over REST now needs the view_jobs scope, as their MCP tools already did: GET /api/change-reviews with …/facets, …/lookup and …/readiness, and GET /api/change-reviews/{issue_identifier} with …/criteria, …/comment, …/ticket-freshness and …/branch-status. A key without the scope gets a 403 that names it. Before, any key on the workspace could read them. A change review's pull request review results (pr_reviews) also need the view_repositories scope, as the pull request reviews themselves do, over REST and in the MCP get_change_review tool. Without it, pr_reviews is empty.

November 16, 2026​

  • API note. Reading pull request reviews, open pull requests and guidance over REST now needs the view_repositories scope, as their MCP tools already did: GET /api/reviews, GET /api/guidance, and …/reviews, …/reviews/{pr_number}, …/pulls and …/guidance under /api/repos/{github_org}/{github_repo}/{github_base_branch}. Cost forecasts need the submit_analysis_jobs scope: GET …/forecasts, GET /api/forecasts/lookup and the MCP forecast tool. A key without the scope gets a 403 that names it. Before, any key on the workspace could read them.

November 11, 2026​

  • The Hyrax Risk check shows while a review runs. When a review starts, a Risk rating queued Hyrax Risk check now goes up beside Review queued, where the risk rating is on. It's replaced by the rating when the review posts. If the review ends without posting a rating, Hyrax still completes the check, with a rating or as Not rated (neutral). See PR review.

November 9, 2026​

  • Change a repository's settings from chat and your AI tools. Hyrax chat and the MCP update_repo tool can now change the settings on a repository's Settings page: PR review, how fixes land and what happens when one fails, pull request contents, missions, the ticket system and the repository's notes. Chat still asks before it changes anything. Changing them needs the manage_repos permission. The branch commit-mode fixes collect on is still set in Hyrax only. See the MCP server.
  • API note. A test or build command override that is only spaces now clears the override, on PATCH /api/repos/{github_org}/{github_repo}/{github_base_branch} and the MCP update_repo tool alike. Before, the PATCH stored the spaces. Some malformed ticket_config values that made the PATCH fail with a 500, such as a list for system or a string for config, are now refused with a 422.
  • Choose when the Hyrax Risk check passes. Each repository now has a risk check threshold, under Risk policy on its Settings page. A pull request rated at or above it gets a neutral Hyrax Risk check, and one rated below it gets success. The default is 8, so a pull request rated 7 out of 10 now passes the check. Before, 7 and up reported neutral. A pull request Hyrax couldn't read in full is still neutral. See PR review.
  • API note. PATCH /api/repos/{org}/{repo}/{branch} and the MCP update_repo tool take risk_threshold, from 1 to 10. The repository detail and get_repo return it. See the MCP server.

November 8, 2026​

  • API note. Where Plans are offered, moving a triage issue that is on no Plan to open is refused with issue_not_on_a_plan: a 409 from POST /api/issues/{ref}/status, and the outcome not_on_a_plan from the MCP update_issue_status tool. In Hyrax, Make it a draft starts a draft Plan from the issue instead. Closing it is unchanged. See the MCP server.

November 4, 2026​

  • AI tools can mark a finished Plan done. Once every done-when line is met and none of the Plan's issues is still open, an AI tool acting for someone who may edit the Plan can mark it done. Until then, a person marks it done on the Plan's page. See Plans.
  • API note. PATCH /api/plans/{ref} with state done and the MCP update_plan tool with state done now succeed for an API key once every done-when line of the Plan is met and none of its issues is still open, sent without new done_when lines. It is also refused for a Plan with no done-when lines, for an alert's standing Plan, while a line counts as met only because its last open issue was dropped, and while someone's choice to keep the Plan open stands. Before then the move is still refused with plan_done_needs_a_person, and the error names the lines not met yet and says whether work is still open. A key with an agent label is recorded as that agent, and any other key as the person it acts for. See the MCP server.
  • API keys can't change Areas and Spaces at all. They can still read them. Changing a Space's or an Area's details, such as its summary, goal or whether it's active, paused or done, and changing its repositories or its people, now needs a person in the web app, as creating, renaming, moving, archiving and deleting one already did. Nor can the AI tools that use API keys.
  • API note. Every write of an Area or a Space by an API key is refused with space_tree_needs_a_person, whatever its scopes: a 403 over REST, and a tool error on the MCP server. Over REST that adds PATCH, PUT /repos and PUT / DELETE /members/{user_id} on /api/spaces/{slug} and /api/areas/{slug}, POST /api/spaces/{slug}/repos/{repo_id}/leave, and POST / DELETE on /api/spaces/{slug}/linear-selections. On the MCP server it covers every call of update_space, update_area, add_repo_to_space, remove_repo_from_space, add_repo_to_area and remove_repo_from_area. See the MCP server.
  • API note. A person-only step now refuses every API key, with or without an agent label: POST /api/issues/{ref}/review answers 403 human_review_required, and POST /api/plans/{ref}/related/{issue_ref}/keep and the MCP keep_plan_related tool answer 403 needs_a_person. An API key's change to an issue no longer marks it reviewed.
  • API note. The MCP set_tenant_setting and clear_tenant_setting tools are gone from the MCP server. A signed-in person can still set or clear a workspace setting in Hyrax chat.

November 3, 2026​

  • Issues no longer have a type. Bug, Feature and Task are gone from issues. Labels still organise them.
  • AI tools can't use Mark done. Marking a Plan done is for a person who may edit it, on the Plan's page. An AI tool can still do the Plan's work. See Plans.
  • API note. An API key can no longer move a Plan to done, whatever its scopes. When the key's person may edit the Plan, the move is refused with plan_done_needs_a_person: a 403 from PATCH /api/plans/{ref}, and a tool error from the MCP update_plan tool. A key's other moves of a Plan are unchanged. See the MCP server.
  • API note. Issue records no longer carry type, over REST and on the MCP server. A request that sends type is refused as an unknown field: creating or updating an issue, the type query parameter on GET /api/issues and GET /api/spaces/{slug}/issues, and the type argument of the MCP list_issues, file_issue and update_issue_fields tools. Over REST that is a 422, and on the MCP server a tool error. See Issues.

October 28, 2026​

  • API keys can't create, rename, move, archive, unarchive or delete Areas and Spaces. Nor can the AI tools that use them. A person does that in the web app. See Organizing work.
  • API note. An API key that creates, renames, moves, archives, unarchives or deletes an Area or a Space is refused with space_tree_needs_a_person, whatever its scopes: a 403 over REST, and a tool error on the MCP server. On the MCP server that covers create_space and create_area, and a new title or an archive or unarchive through update_space or update_area. A key can still change a Space's or an Area's other details and its repositories. See the MCP server.

October 27, 2026​

  • Manage risk rules from your AI tools. The MCP update_repo tool now takes risk_rules, so an agent can set a repository's risk rules, the same list as Risk policy on its Settings page. It replaces the whole list, and an empty list clears it. get_repo returns the current list. Changing them needs the manage_repos permission. See the MCP server.
  • API note. Fields, query parameters, paths, error details keys and MCP tool outputs that named a Space as a "project" now say "space", and the old names are removed. For example, issue records carry space_id and space_slug in place of project_id and project_slug, and MCP issue tools such as get_issue and list_issues return space_id. No MCP tool's inputs changed. See the API reference.
    • Query parameters. project is now space on GET /api/jobs (and its /facets, /summary and /active reads), GET /api/observations, GET /api/code-health/spaces, GET /api/reviews, GET /api/change-reviews (and its /facets read), GET /api/work/progress, GET /api/work/build, GET /api/tinker/space-sets, GET /api/tinker/forge, GET /api/tinker/briefs, GET /api/tinker/runs and GET /api/linear/candidates. project_id is now space_id on GET /api/issues and GET /api/issue-labels.
    • Unrecognized query parameters. Each of those reads now returns 422 for any query parameter it doesn't recognize, not only for the old names. Before, most of them, GET /api/jobs and GET /api/observations among them, ignored one and returned the list unfiltered.
    • Paths. /api/code-health/projects is now /api/code-health/spaces, /api/tinker/project-sets is now /api/tinker/space-sets, /api/tinker/project-sets/move is now /api/tinker/space-sets/move, …/tinker/sets/{set_ref}/pick/projects is now …/tinker/sets/{set_ref}/pick/spaces, and /api/plans/{ref}/build/projects is now /api/plans/{ref}/build/spaces.
    • Team context. Entries and the digest carry space and source_space_slug in place of project and source_project_slug, over REST and on the MCP server. Team context questions carry space_slug in place of project_slug, and a Team context error's details.project is now details.space. An entry's scope keeps its project value.
    • Error details. Keys such as project_id, project, project_slug and project_title are now space_id, space, space_slug and space_title. Some keys that hold an Area's id are now area_id.
    • Removed. POST …/tinker/sets/{set_ref}/pick/preview no longer returns subproject_title or subproject_slug.
    • Kept. Error codes and enum values keep their names. Names about a project in another tracker, such as Linear, keep "project": a Space's external_project_url, and a setup run's ticked_projects and no_project counts.

October 23, 2026​

  • Work happens on a Plan. An issue must be on a Plan before you or your AI tools can claim it, move it to In progress or Blocked, assign it to someone or start a mission on it. An issue on no Plan stays in the Backlog until it's put on one. On the issue's page those controls stay in place, turned off, with the reason. Put the issue on a Plan from its Plan row. See Issues.
  • New mission files an issue when you name none. With no issue picked, New mission files your directive as a new issue, optionally on a Plan, and opens it. Start the mission from that issue once it's on a Plan. See Missions.
  • API note. Starting a mission without an issue ref, or with space, is refused with mission_needs_an_issue. Claiming, keeping a claim on, assigning, or moving to in_progress or blocked an issue on no Plan, and starting a mission on one, are refused with issue_not_on_a_plan. Over the MCP server, the claim, status and issue-update tools answer not_on_a_plan. See the MCP server.
  • Risk rules for each repository. On a repository's Settings page, under Risk policy, list the paths your team always treats as high risk. When a pull request changes code under one of them, the Hyrax Risk check rates it High risk and names the rule, unless it already found something riskier or couldn't read the whole pull request. Changes to tests, test fixtures and Markdown docs don't count. See Pull request review.

October 21, 2026​

  • A Hyrax Risk check on reviewed pull requests. Reviews now post an advisory Hyrax Risk check (where the merge recommendation is on, which is the default), next to Hyrax Review. It rates the pull request's risk out of 10. Low risk and Medium risk report success, High risk reports neutral and names the main reason, and Not rated means Hyrax didn't read the whole pull request. The rating never fails and doesn't read your CI, so a failing build no longer raises it. It replaces the two 📋 lines at the top of the review comment, Suggested review depth and Merge recommendation, which new reviews no longer show. See Pull request review.

October 20, 2026​

  • Plans replace Projects. Issues now belong directly to a Space. Each Project became a Space in the same Area, keeping its issues, repositories and team context, and each Space's Inbox moved its issues into the Space. A Plan (PLN-N) says why work exists: a goal, objectives and when it's done. A Plan can cover Spaces in any Area, and each Space approves it on its own. See Organizing work.
  • Areas hold people too. An Area's people and repositories reach every Space in it.
  • Every mission works one issue. Pick the issue when you start a mission, or Hyrax files your directive as a new issue in a Space you choose. See Missions.
  • Issues have a type: Bug, Feature or Task.
  • API note. The /api/projects/... routes are now /api/spaces/..., and the MCP project tools are now Space tools, such as list_spaces and create_space, alongside new Area and Plan tools. The old names are removed. See the MCP server.

October 12, 2026​

  • Switch from the top of the rail. The card at the top of the rail names where you are. Open it, then click an Area or a Space to see what's inside, and All spaces in … or All projects in … at the top of the next column to go there. Click a Project to go to it, or All areas to go to the whole workspace. Type to find any of them, or type an issue's ref, such as ISS-12, to go straight to that issue. You stay on the same page, when the place you go to has one. The path in the top bar names where you are. The top bar's Go to… menu is gone. See Organizing work.

October 9, 2026​

  • API note. The deprecated health-score fields (overall_score, benchmark_scores, latest_benchmark_*, last_benchmark_status, org_averages and weakest_domains) and virtual_patch_counts are removed from repository records, the workspace dashboard, and the MCP get_repo and workspace_overview tools. They have always been empty, null or zero since health scores and Virtual Patches were retired. The …/benchmarks/progression and …/benchmarks/trends repository routes are removed too, and now return 404. The MCP workspace_overview tool is now cursor-paginated like the other list tools: it takes limit and cursor and returns the repo rows as data, with next_cursor and has_more, in place of the old repos list. See the API reference.

October 8, 2026​

  • Projects and Issues for every workspace. Every workspace now uses the new layout, organized into Areas, Spaces and Projects, with Issues to track work. If your workspace has never had a Space, Hyrax creates a Space named Default and puts your repositories in it, along with an Area named Default to hold it if you have no Area yet. That happens on its own, shortly after this update reaches your workspace.
  • Team context for every workspace. Team context, where your team writes down the decisions, conventions, runbooks and warnings your agents should know, is now on every plan. It used to be a private beta that had to be turned on for each workspace. Entries can be read and written in the web app, through the REST API and through the MCP server, and what an agent writes stays a proposal until a person confirms it. See Team context, and Members & roles for who can do what.
  • API note. Team context routes and MCP tools no longer refuse a call with plan_restricted. An API key created before this update may not include the Team context permissions; create a new key to use them. See Endpoint reference: Team context.

October 6, 2026​

  • Discovery is no longer limited to your first repository. Before, only your first repository and public repositories added by URL started Discovery on their own. Now Discovery starts automatically when you add any repository on the web or through the REST API, unless something holds it back, such as your workspace's usage limits. Adding a repository through the MCP server or chat doesn't start it. If a repository hasn't been discovered, including one you added before this change, start Discovery from its Discovery tab. See Discovery & AI agent context.
  • Virtual Patches is retired. Audits no longer learn scanner patterns from earlier runs or apply them to later ones, and the Virtual Patches page, its sidebar item, and its Settings toggle are gone. Virtual Patches never edited your files, so nothing in your repositories changes, and findings your audits already produced stay as they are. Later audits use Hyrax's standard scanner patterns and severities, so a pattern Virtual Patches had turned off or re-rated for your workspace runs as standard again.
  • API note. On repository records, virtual_patch_counts is deprecated: it now always reads {"patterns": 0} and will be removed in a later release. The MCP tools for listing learning improvements and setting learning flags are removed, and workflow='learn' continues to return 422. See the API reference.

October 1, 2026​

  • Every review now posts a fresh comment. Hyrax used to edit its review summary in place when the findings hadn't changed, which sent no notification and left the summary far up a long thread — so a re-review after a force-push could change the merge recommendation without anyone seeing it. Each review now posts at the bottom of the thread and folds the previous summary into a pointer that keeps the commit it reviewed, its finding count, and its merge recommendation when one was shown. Ticking a checkbox still edits the summary in place, and closing and reopening a pull request doesn't re-review a commit Hyrax has already reviewed. See Pull request review.

September 15, 2026​

  • Publish is retired — your AI agents read repo context over MCP instead. The Publish workflow opened a pull request that wrote generated documentation (HYRAX.md, a .hyrax/ directory, ignore files, and a block in your CLAUDE.md) into your repository. It's gone, and nothing replaces it in your repo: the same context — architecture, conventions, how-to guides, open findings — is served live by the MCP server, so a connected agent always reads the latest Discovery run rather than a copy that went stale when it merged. If you did merge a Publish pull request, the files it created are yours to keep or delete; Hyrax won't touch them again. Anything earlier on this page that describes publishing context into your repo is superseded. See Discovery & AI agent context.
  • API note. publish is no longer a valid workflow value and returns 422. See the API reference.

August 25, 2026​

  • Creating a workspace asks who you are. The workspace-creation screen now asks for your name, your company name, and your company URL, and every field carries a visible label instead of placeholder text that vanished as soon as you typed. See Quickstart.

August 24, 2026​

  • A clearer answer when a run is refused for credit. A Free workspace that has used up its credit is now told what its next monthly credit will be, instead of being pointed at a reset that might not cover the run it just refused. See Plans & pricing.

August 16, 2026​

  • Your remaining credit is in the top bar, on every plan. Free workspaces hold real spending credit — a one-time signup credit plus a monthly one — but the top-bar figure only ever appeared for paid workspaces, and Free's Settings → Plan showed the plan picker with no balance on it. Both now show what you have left ("$29.04 credit left", or "No credit left" when it runs out). It's a remaining balance rather than the paid plan's "$12 of $30" ratio: your signup credit and your monthly credit are one pool, not a countdown to a renewal date. See Plans & pricing.
  • Connecting a GitHub organization drops you straight into your new workspace. Finishing the connect could land on a "Hyrax is not configured" screen for a workspace that had just been created successfully — a refresh fixed it, but nothing said so. It doesn't happen any more, and if a workspace ever can't be loaded the screen now re-checks by itself and offers a retry instead of a dead end. Accepting an invitation had the same rough edge and is fixed with it. Connecting also shows a proper progress indicator now — setting up a workspace takes a few seconds and the button used to look inert while it worked.

August 11, 2026​

  • Two plans: Free and Paid, and Paid is priced per seat. Hyrax used to have three plans — Free, Pro, and Team — at a flat price each. It now has two, Free and Paid, and Paid costs $30 per seat, per month, with every dollar of the subscription coming back as spending credit for that month. No feature is withheld by plan: every workflow, the workspace audit log, Virtual Patches, the Todo list and notifications feed, and programmatic access through the REST API and the MCP server run on both, and repositories are unlimited on both. Anything earlier on this page described as a Pro or Team feature is now on every plan. Members are unlimited on Free; on Paid each member occupies a purchased seat, which you can add to or reduce yourself from Settings → Plan. Pro and Team are no longer offered; workspaces already on one keep everything they had, on the terms they signed up under. See Plans & pricing and Seats.

August 8, 2026​

  • Every plan now gets both audit depths, and the Mini audit is gone. The audit used to come in three depths that followed your plan. It now comes in two — the Standard audit and the Full audit — and both run on every plan, including Free. The Mini audit, a capped quick pass that only existed as Free's substitute, has been retired: with the real audits available to everyone there was nothing it was better at. What bounds your usage is your workspace's credit, not your tier. See Workflows and Audit depth.
  • Connecting a repo starts PR review, not an audit. New repositories arrive with pull request review switched on, so Hyrax starts working on the pull requests you open without you configuring anything. Your first repository still runs Discovery automatically to learn the codebase; audits are now always something you choose to run. Repositories you add later don't run Discovery on their own — start it from the repo's Discovery tab when you're ready (an audit needs it first). Public repositories added by URL are the exception: they always run Discovery, because without the GitHub App there are no pull requests for Hyrax to review.
  • API note. mini_audit is no longer a valid workflow value and returns 422. Use standard_audit or audit. See the API reference.

August 6, 2026​

  • Sign up with any email address. Hyrax no longer turns away signups from personal email providers — gmail.com, outlook.com and the rest now work like any other address.

July 28, 2026​

  • Signing in is Google or an email code. The "Continue with GitHub" button is no longer on the sign-in page — new accounts sign in with Google or with a one-time code sent to your email. If you already sign in with GitHub, that keeps working. Connecting GitHub is unchanged and remains a separate step, about repository access only. (This supersedes the June 17 note below, which listed GitHub as a sign-in option.) See Members & roles.

July 23, 2026​

  • Findings Hyrax can't fix now wait for your review — nothing is silently dropped. When automatic fix attempts are exhausted, a finding no longer disappears as "abandoned"; it stays open and moves into a needs-review lane on the Findings tab with clear next steps — dismiss it, mark it addressed, or try one more attempt. Cancelled fixes and infrastructure hiccups (a build/CI blip on our side) no longer count against a finding's attempt limit, so a finding whose only failures were noise stays freely retryable. See Findings.

  • When Hyrax thinks a finding is a false positive, it tells you. If the fix agent repeatedly concludes there's nothing to change, the finding is flagged as a suspected false positive — with the agent's reasoning shown inline — and you decide: Confirm false positive (dismiss it), Keep open (you disagree; it stays a real issue), or Try one more attempt. Hyrax never auto-dismisses it for you.

  • Notifications in the top bar. Pro and Team workspaces get an in-app notifications feed: the bell in the top bar now shows what happened in your workspace — a finished audit, a merged fix pull request — with an unread badge and a quick preview of recent items; opening an item marks it read. The Todo list moved to its own button beside the bell, which shows your open count and takes you straight to the Todo page. (This supersedes the July 10 note below about what the bell shows.) See Todo & notifications.

July 10, 2026​

  • A Todo for your workspace. Pro and Team workspaces get a Todo page — a prioritized list of what needs attention across your repos, from onboarding gaps and stale audits to unaddressed critical findings and stale fix PRs — each item with a one-click action. A Todo button in the top bar shows your open count and takes you to the list from anywhere in the app. See Todo & notifications.
  • Every resolution in one place. Each repository's Completed tab is now the full resolution record: fix pull requests in one lane, and a new Resolved lane listing everything closed without a pull request — findings you marked addressed or dismissed — with filters and the time each item was resolved.
  • Virtual Patches, on by default. Team workspaces now get Virtual Patches automatically: Hyrax studies what each audit found — and what you dismissed — and mines learned scanner patterns, scoped to your workspace, that apply at audit time without modifying any of your files. Each repository's Virtual Patches page lists every learned pattern and how it has performed, so you can turn any of them off (or back on) at any time — or switch the whole feature off in Settings. See Plans & pricing.

July 9, 2026​

  • See who changed what. Team workspaces get a Workspace changes log under Settings — a timeline of changes made in your workspace (role changes, invites, API keys, settings edits, repository changes) and who made each one. See Plans & pricing.

July 8, 2026​

  • Inactive Free workspaces pause after 90 days. A Free workspace with no activity for 90 days is now paused instead of staying live indefinitely: it becomes read-only and nothing is deleted. We email you about a week before the pause and again when it happens, and you can restore the workspace yourself with one click. Paid plans are unaffected. See Plans & pricing.

July 1, 2026​

  • See why to trust a finding. Each finding's detail page now has a Trust section: how the finding was detected, the evidence behind it, a Citation verified ✓ badge when the finding's detection query matched code in the repository at the time the finding was created, and a copyable check you can run yourself to confirm it. The findings list also gains a Category filter, so you can narrow the list to just security, performance, or any other category.

June 17, 2026​

  • New sign-in. Hyrax now uses hosted, password-free single sign-on — continue with GitHub, Google, or a one-time code sent to your email. There's no Hyrax password to set or remember, and connecting GitHub is now only about repository access, separate from how you log in. See Members & roles.
  • Two-factor by default. Every account is protected by a two-factor security floor, satisfied automatically by your verified login email — nothing to set up. You can additionally add an authenticator app or a passkey for stronger protection. See Security.

June 5, 2026​

  • Three audit depths, one per plan. The audit now scales with your plan: Free runs the Mini audit (a quick pass, up to 5 findings), Pro runs the new Standard audit (a focused 24-tool sweep across security, correctness, maintainability, performance, and dependencies), and Team adds the Full audit (the complete ~39-tool catalog, adding architecture analysis). The Run Audit button runs your plan's everyday audit — the Mini audit on Free, the Standard audit on Pro and Team; Team also gets a separate Full audit button for the complete catalog. See Plans & pricing and Workflows.

June 1, 2026​

  • First release. Connect a GitHub repository and Hyrax profiles it, audits it for prioritized findings, ships fixes as pull requests, reviews your incoming pull requests, and publishes your repo's context for AI coding tools. See How Hyrax works to get started.