User Manual — Rynci Software

1. Quick start top

Install the evaluation package and run the following using rynci (on Windows, .\rynci.cmd from the extracted folder; on macOS/Linux, ./rynci).

rynci --version
rynci check
rynci demo
rynci verify demo

The demo is synthetic and requires neither Docker nor an account. It does not start the trial.

2. GitHub access top

Public run metadata may be queried without authentication subject to rate limits. For private repositories, create a fine-grained GitHub token with Actions and Contents read permissions.

# macOS / Linux
export GH_TOKEN="YOUR_GITHUB_READ_TOKEN"

# Windows PowerShell
$env:GH_TOKEN = "YOUR_GITHUB_READ_TOKEN"

Never include tokens in a report or checked-in script. Access tokens are not uploaded to Rynci servers.

3. Diagnose a GitHub Actions run top

rynci doctor "https://github.com/OWNER/REPO/actions/runs/RUN_ID" --open
rynci history
rynci show SESSION_ID --open

Diagnoses save evidence locally, identify likely failure categories, and create an HTML report.

4. Replay locally top

rynci replay RUN_URL --clone --until-failure
rynci replay RUN_URL --clone --execute --until-failure
rynci replay RUN_URL --repo ./existing-repository --execute

Without --execute, Rynci generates a plan. With it, Rynci executes a selected supported job through act and Docker. Available job-selection options include --job-id, --until, and --until-github.

Security: A GitHub Actions workflow can execute arbitrary code. Docker is not a strong security boundary; use a disposable VM for untrusted repositories. Hosted GitHub runners and local execution can differ in OS, images, cache, network, secrets, services and architecture.

5. Independent AI-agent verification top

rynci verify init
rynci verify run whyci-verify.json --open
rynci verify demo

Create assertion suites that validate state outside an agent's own success message: HTTP responses, SQLite data, process exit codes, filesystem assertions and optional browser tests. Export reports as HTML, JSON and JUnit. Browser checks require Playwright Chromium.

6. Command reference top

Command	Purpose
`doctor URL`	Diagnose a failed GitHub Actions run.
`replay URL [--clone \| --repo PATH]`	Generate or execute a local replay.
`local --workflow FILE --job ID`	Replay a local workflow job.
`retry SESSION_ID`	Retry a previous local replay session.
`history` / `show SESSION_ID`	Inspect previous local sessions.
`verify init` / `verify run FILE`	Configure and execute independent checks.
`check` / `demo`	Dependency check and local demo (do not start trial).
`license status` / `license activate` / `license pricing`	Trial and registration information.

7. Evaluation and licenses top

Rynci offers a 14-day evaluation and a single $99 Professional license. The key is verified locally; the purchased version remains usable beyond the 12-month update window.

rynci license status
rynci license activate

License terms · Purchase recovery

8. Troubleshooting top

Python module errors: rerun the installer with internet access. GitHub API 401/403/404: check token scope, visibility, rate limits and run URL. Docker/act missing: rynci check explains optional dependencies. Local replay differs from CI: compare architecture, runner image, event inputs and service containers. Trial expired: activate a registration key.

Additional information is available in Support.