Skip to main content

Workflows

A workflow is a job you run against a repository. Each does one thing well, and most teams use several on a regular cadence. You start most of them from the web app, and every one of them through the REST API or the MCP server. For what each plan includes — and how each run draws on your monthly credit — see Plans & pricing.

At a glance​

WorkflowWhat it doesYou getPlans
Full auditThe deepest audit — the complete ~39-tool catalog, including architecture analysisFindingsEvery plan
Standard auditA focused 24-tool audit across security, correctness, maintainability, performance, and dependenciesFindingsEvery plan
DiscoveryProfiles your repo so every other workflow understands it; starts automatically when you add a repo (usage limits permitting); otherwise start it from its Discovery tabStored repo contextEvery plan
RevalidateRe-checks existing findings against the latest commit without generating new onesUpdated finding statusesEvery plan
PR reviewReviews incoming pull requests automaticallyA PR comment + check runEvery plan
FixFixes a specific finding and opens a pull requestA pull requestEvery plan
Mission (beta)Plans a directive you write, works it step by step, and opens one pull requestA pull requestPaid, on request

Plan and access limits​

  • Only missions are withheld by plan. Every other workflow above is available on every plan, including Free, and there is no per-month run count. Missions are a beta that Hyrax support turns on for a Paid workspace on request. What you spend is the credit your workspace holds: each run draws against it, and a bigger or deeper run draws more.
  • Public repos are read-only. A public repository connected without installing the Hyrax GitHub App can run the workflows that don't write back: either audit depth, Discovery, and Revalidate. PR review runs too — started through the API for a specific pull request — but its results stay in the app: without the App, nothing can post to GitHub and nothing triggers a review automatically. Fix and missions need the App, and installing it later doesn't change a repo added this way: to run either, remove the repo and add it again with the App installed. See Public & private repositories.

See Plans & pricing for the full per-plan breakdown.

The audit comes in two depths — Standard (the everyday default) and Full. Audit depth covers what each depth runs and how the audit button and its level picker behave.

Full audit​

The flagship, and the deepest sweep. A full audit runs the complete ~39-tool catalog — every category, including architecture analysis and the full operations set — and produces findings (concrete problems to fix, each with a priority, a category, and the exact file location). It's a deliberate action: you choose when to run it. See Audit tools & languages for what it covers and How Hyrax works for what happens during a run.

Available on every plan. You run it from the audit button's level picker — Audit depth covers the button behavior. It sits behind the picker rather than on the button itself because it is slower and costs more, so choosing it should be deliberate.

Standard audit​

The everyday audit. It runs the same engine as the Full audit over a focused 24-tool subset — security, correctness, maintainability, performance, and dependencies — dropping the architecture group and most of operations. It produces the same kind of findings as the full audit, just over a leaner set of concerns, which keeps each run cheaper. It's what the audit button runs by default (Audit depth).

Available on every plan.

Discovery​

Profiles a repo — its architecture, conventions, and how-to knowledge — so audits and fixes on it are sharper, and so the AI coding tools you connect over the MCP server read your real conventions instead of guessing. See Discovery & AI agent context.

Discovery starts automatically when you add a repository on the web or through the REST API, unless something holds it back, such as your workspace's usage limits. Adding one through the MCP server or chat doesn't start it. It's a prerequisite for auditing that repo. If it hasn't run, or after big changes, start it from the repo's Discovery tab — one click. (Audits never start on their own: your first audit on a repo is always something you choose.)

Available on every plan.

Revalidate​

Re-checks your existing findings against the current state of the repo and updates their status — without generating new findings. Use it to cheaply confirm that work resolved what it was supposed to, instead of paying for a full audit.

In the web app it's Re-check findings: a button beside Run audit on Code health, and the last item in the audit menu on a repository's page. It closes the open findings the current code has fixed, and they move to Resolved. You can also start it through the REST API or the MCP server.

Available on every plan.

PR review​

Reviews a pull request and posts a single review comment plus a Hyrax Review check run. You can require it for merge — see Pull request review for what that means for pull requests Hyrax skips. It is on by default for every repository you connect, and runs automatically on incoming pull requests; turn it off per repo in the repo's settings.

Available on every plan.

Fix​

Fixes a specific finding and opens a pull request. The finding stays open until that pull request is merged. See Fixes.

Available on every plan.

Mission​

A mission takes a directive you write — "Add retry with backoff to the payment client and cover it with a test" — and works it to a pull request. Hyrax plans the work, runs it as a series of steps on one branch, marks the pull request ready so your CI runs, and checks the whole branch. Hyrax never merges it. See Missions.

Missions are in beta. They are available on Paid workspaces, need on-demand spending turned on, and Hyrax support turns them on for your workspace on request.

Where to go next​