Skip to content

Getting Started

How It Works

Ribix has two operating modes that work together: Proactive mode, where Ribix acts like a real user to find bugs before they reach production, and Reactive mode, where it enriches issues your team files in under 60 seconds.

Proactive mode

Proactive mode is triggered by a code push or a manual ribix run. A browser agent navigates your staging environment like a real user, while API and code quality agents test in parallel.

Code push

or ribix run

→

Browser agent

navigates staging

finds anomaly→

Classify

P0–P3 severity

→

Test

failing test written

→

Fix

diff generated

you decide→

Approve → PR

Steps in detail:

  1. Trigger. A push to your main branch (via the GitHub App webhook) or a manual ribix run starts the agent loop.
  2. Navigate. The browser agent renders pages, fills forms, clicks buttons, and exercises API endpoints just as a user would. It builds a coverage map so it does not redundantly explore the same flows.
  3. Classify. Every anomaly (crash, broken UI, API error, performance regression) is classified by severity using P0–P3 conventions. P0 is a complete blocker (app down, data loss); P3 is cosmetic.
  4. Test. For each finding, Ribix writes a failing test against your existing test framework (Jest, Vitest, Pytest, or Go test).
  5. Fix. An LLM generates a minimal patch. Ribix runs your full suite against the patch - if tests still fail, it retries up to 3 rounds before flagging the finding as "needs human."
  6. Approve. You review the test + diff in the CLI or dashboard, then approve or reject. Approval opens the PR on GitHub.

Reactive mode

Reactive mode fires automatically when a new GitHub Issue is opened in a connected repository. Within 60 seconds Ribix posts an enrichment comment with a diagnosis, severity estimate, candidate files, blame-linked suspect changes, and a suggested owner.

Issue opened

on GitHub

→

Webhook

issues.opened

< 60 sec→

Enrich

blame + history

→

Enrichment comment

posted to issue

Enrichment happens silently in the background - your team's GitHub workflow does not change. The ribix-bot comment appears alongside normal issue notifications.

Reactive enrichment requires the GitHub App.

Install and configure the Ribix GitHub App to enable reactive enrichments. See Integrations for setup steps.

Agent types

Ribix runs several specialized agents in parallel during a proactive run. Each agent targets a different class of bug:

Browser agent

Drives a real Chromium browser against your staging URL. Navigates pages, submits forms, triggers JavaScript interactions, and watches for runtime errors, network failures, and visual regressions.

API agent

Calls your REST or GraphQL endpoints directly. Tests edge-case inputs, malformed payloads, and rate-limit behavior. Compares responses against your OpenAPI spec when one is present.

Code quality agent

Analyzes the diff introduced by the latest push. Flags security vulnerabilities, type errors, and logical bugs before they are exercised at runtime.

Design agent

Analyzes your staging UI using AI vision. Checks for accessibility violations, layout breakages, and visual anomalies across viewports. Flags issues in the current rendered state after the push.

Test frameworks

Ribix auto-detects your test framework by scanning package.json, pyproject.toml, and go.mod. Supported frameworks:

FrameworkLanguageConfig fileDetection signal
JestJavaScript / TypeScriptjest.config.*jest in devDependencies
VitestJavaScript / TypeScriptvitest.config.*vitest in devDependencies
PytestPythonpyproject.tomlpytest in dependencies
Go testGogo.mod_test.go files in repo

Ribix runs the detected framework with your existing configuration. It does not modify your test setup. If multiple frameworks are detected (e.g. Jest + Vitest in a monorepo), you can pin the framework with:

ribix connect https://staging.example.com --framework vitest

Next steps