How Rihario Works

Rihario operates as a cloud-based, autonomous browser orchestration engine. The Rihario System Architecture adheres to a strict deterministic flow for Guest and Registered execution modes.

Core System Flow (Guest Mode)

1. Ingestion

User submits a URL via the landing page. The API validates reachability and headers (CSP, CORS) to determine testability.

2. Provisioning

A transient, sandboxed browser container (Chromium) is spun up in an isolated worker node. This container has zero persistence and is destroyed after execution.

3. Exploration (The "Vibe" Check)

The AI Agent attaches to the CDP (Chrome DevTools Protocol). It identifies interactive elements using a semantic heuristic (not just CSS selectors). It begins a random-walk exploration to identify the "Happy Path" (e.g., finding the primary CTA).

4. Reporting

Screenshots, network logs, and DOM snapshots are streamed back to the dashboard. The "IronMan HUD" overlay is generated by mapping element coordinates to the visual report.

Core System Flow (Registered Mode)

1. Authentication Injection

For authenticated tests, specific credentials (stored encrypted) are retrieved. The agent injects these into the login form or bypasses UI via session token injection if configured.

2. State Management

The Cookie Banner State Machine activates to dismiss tracking consents automatically. This prevents "pop-up fatigue" from blocking the test.

3. Goal-Directed Execution

Unlike Guest mode, Registered mode follows specific "Implementation Plans" (e.g., "Go to settings and change password"). The AI uses the Self-Healing Memory to recall element locations even if classes have changed since the last run.

System Components

  • Worker Node: Stateless execution environment.
  • Browser Matrix: Parallel grids for Chrome, Firefox, Safari, Edge.
  • Bloom Judge: An LLM-based auditor that scores the AI's behavior against safety and compliance guidelines.