What shipped in Check’d.

Notable releases, newest first, with the day they went live. Smaller fixes land every day and are not listed.

  1. Open-source packages on npm and GitHub

    The CLI, the MCP server and both monitoring SDKs are published on npm under MIT, with their source on GitHub.

    • checkd-cli: the checked command
    • checkd-mcp: the MCP server for AI assistants
    • checkd-browser and checkd-node: the monitoring SDKs

    Developer tools

    Session replay

    Opt-in replay in checkd-browser 1.1.0. It records around errors by default, masks every input in the browser and plays back on the issue page with error, click and request markers.

    • A Replays page with filters for issue, release, page and errors
    • Save a replay as a journey
    • Replay usage on the Plan and usage page

    About session replay Replay docs

    Explain with AI and fix pull requests on issues

    Any issue can be explained in plain English: what is broken, the likely cause, who is affected, where to look, a suggested fix and how sure it is. From there, open a fix pull request on GitHub.

    • Privacy-safe context: no user ids, IP addresses or query strings
    • Reads your code at the matching release when GitHub is connected
    • The CLI and MCP server read the inbox and its cached explanation

    About AI explain and fix

  2. Production monitoring and the unified issue inbox

    Browser and Node.js SDKs send the errors, failed requests and slow pages real users hit. They are grouped by root cause into issues, next to the findings from test runs, scans and load tests.

    • Releases, regressions, users affected, first and last seen
    • Owners, comments and bulk actions
    • Alerts for new issues, regressions and spikes by email or Slack

    About monitoring Monitoring docs

    Journeys, rebuilt

    Record a journey in a browser shown inside Check’d, or describe it in plain English. Journeys replay with several locators per step, self-heal with your approval, and fresh test data on every run.

    • Step editor with screenshots
    • Reusable pieces such as a shared sign-in
    • A bookmarklet for sites our servers cannot reach

    About journeys

    The checked CLI and the MCP server

    Sign in from the terminal by approving a code in the browser, import specs, start runs with live progress and CI exit codes, and connect Claude Code, Cursor or VS Code through MCP.

    CLI docs MCP docs

    Testify is now Check’d

    A new name and the Ch’D mark across the app, emails, reports and the share image, on getchecked.twelveai.app.

  3. Plans in US dollars and a new workspace layout

    Starter $20, Business $100 and Team $200 a month, with usage and extra credit in US dollars. The app moved to a calmer workspace layout with tables and metric strips, and the marketing site was rebuilt.

    Pricing

  4. Ask in real time during runs

    When a test hits something only you know, such as a staff sign-in or a one-time code, the run asks you and carries on. Projects can be archived and restored.

  5. Run depths and the live AI fix panel

    Choose Critical, Standard or Deep for each run, and watch suggested fixes appear on the board as a run finishes.

  6. Senior-QA toolkit

    Requirements traceability, release gates, a written test plan, release certificates, OWASP API Top 10 mapping, contract drift, Gherkin export, compliance packs and a test board.

  7. GitHub pull request checks, GraphQL, Linear and Jira

    Runs on pull requests with a summary on the PR, AI fix pull requests, GraphQL support, findings sent to Linear or Jira, shareable report links and the free site scan.

    Free site scan

  8. Thorough website scans

    Website scans with a site health score, and load tests that stop by themselves before a firewall flags your address.

  9. Parallel test agents and bigger load tests

    Large runs split across parallel test agents, and load tests scale up to 30,000 virtual users on the Team plan.

Try what is new

Start free, no card needed.