jourilo

Walk every journey. Find the friction. Prove the fix.

Jourilo uses your product in a real browser, shows where people get stuck with screenshot evidence,
traces each problem to its root cause and proves every fix with a before/after run.
A CLI and a Claude Code plugin. Local-first, open source.

Install · Claude Code · How it works · Benchmarks · Guide · Docs

It walks the journey, step by step

Jourilo signs up, checks out and follows calls to action like a person would, with a real screenshot of every step.
When a journey breaks, you see exactly where.

Evidence you can see

Every finding comes with the element outlined on its screenshot, the measured values, the WCAG criterion, reproduction
steps and the likely source line. Findings with one cause are grouped into one fix. Verified defects, items that need a
person and conversion hypotheses are always kept apart, and there is no made-up overall score.

Audit → Understand → Fix → Verify

Fix it yourself, automatically or with your agent

• Automatic fixes for mechanical defects (missing lang, viewport, autocomplete, focus styles, paste blocking,
  image sizes, placeholder labels): jourilo optimize previews minimal diffs and writes them only with --apply, as
  one reversible change.
• Repair prompts for everything else: select findings or root causes in the report and copy or download an
  editable Markdown prompt for Claude Code or any coding agent. It carries ids, pages, screenshots, likely source files
  and reproduction steps, and asks the agent to revalidate, change as little as possible, add regression tests and
  verify with Jourilo.
• Experiment briefs for conversion hypotheses, never code changes or promised lifts.

Prove it

jourilo verify repeats the same pages, viewports and journeys and shows what is fixed, new or still present, with the
same region of the page before and after.

One file, any screen, two languages

The report is a single offline HTML file. It follows the browser's language and theme, and you can switch between
English and Turkish and between light, dark and system appearance.

Install

Requires Node.js ≥ 20.10.

npm install -g jourilo

jourilo setup

jourilo audit http://localhost:3000 --repo .

setup downloads Playwright's Chromium once. The report is written to .jourilo/runs/<run-id>/report.html.
More commands and the full loop: docs/WORKFLOW.md and the CLI reference.

In Claude Code

/plugin marketplace add cihantopac/jourilo
/plugin install jourilo@jourilo

Then /jourilo:jourilo https://your-site.dev or /jourilo:jourilo . for a repository. Claude answers in a few lines
(blocked journeys, three priorities, the fixes available, the report path and one next step) and keeps the evidence in
the report. All commands: docs/PLUGIN.md.

Benchmarks

On the 955 W3C ACT Rules test cases that map to WCAG criteria,
written by the ACT Rules Community Group and not for Jourilo (measured again on 2026-11-12 for 1.2.1, with the same result):

Jourilo runs axe-core and adds its own keyboard-trap and focus-indicator checks. Many misses are criteria only a person
can judge, which every report lists. No automated run shows WCAG conformance. Method, fixture benchmark and a
comparison with Pa11y and Lighthouse: docs/EVALUATION.md.

Safe by default

Audits are read-only, respect robots.txt and run behind a network guard that keeps audited pages away from your
machine and network. Journeys never pay, delete or cancel on non-local hosts. Secrets are masked in screenshots and
redacted from reports. Details: docs/PRIVACY.md · SECURITY.md.

The family

Jourilo works on its own and pairs with its siblings through a small, optional contract
(docs/INTEGRATIONS.md):

• Relivaro — code quality, security and release readiness.
• Searvex — SEO and AI-search findings; Jourilo shows them for the same pages.
• Markilo — brand identity; Jourilo checks against its tokens and never
  changes a locked brand. Jourilo's own logo was made with Markilo.

Documentation

Guide · CLI · Plugin · Journeys · Run format ·
Evaluation · Limitations · Architecture ·
Decisions · Roadmap · Changelog · 1.2 release notes

Contributions are welcome: see CONTRIBUTING.md. Every rule needs a fixture that proves it fires and a
control that proves it does not.

License

Apache-2.0. Bundled third-party code: THIRD_PARTY_NOTICES.md.