Work through your audits
from the terminal
Use Tityra from your terminal to read website content audit reports and work with findings. Choose the projects and permissions you share, with explicit confirmation required for changes.
Version 1.1.7. Node.js 22.14.0 or later. macOS, Linux and Windows.
Used by many

CHOOSE PROJECT ACCESS
Use approved projects and permissions.
READ REPORTS AND FINDINGS
Read released reports in your terminal.
WORK IN SCRIPTS AND AGENTS
Read commands and required inputs.
Copy linkStart in your terminal
Tityra CLI 1.1.7 is available as the stable release of @tityra/cli. Install it with npm install --global @tityra/cli@latest.
Install the stable releaseTerminal
$npm install --global @tityra/cli@latest
$tityraBefore you start
Use Node.js 22.14 or later on macOS, Linux or Windows. Run tityra to open the terminal workspace. It checks your connection and prompts for browser sign-in if needed, then lets you choose a project. Use the arrow keys and Enter to navigate; Escape or Ctrl+C exits.
Use @latest to follow stable releases, or @1.1.7 to pin this version. Use tityra --help or a command's --help to see its current options.
Copy linkChoose what the CLI can access
Browser sign-in uses the Tityra customer consent screen. Select the projects to share and review the requested permissions. Access remains limited by those projects and your current account rights. Staff accounts don't connect through this customer client.
The default connection requests read access to projects, audits, reports, findings, discussions and billing. To make changes, request the relevant write permissions through a new login. The --scope list replaces the defaults; it doesn't add permissions to an existing connection.
Use --no-browser to open the displayed authorisation URL yourself on the same computer. The browser returns to a temporary local callback, so browser login needs access to that computer's loopback interface. Review or revoke this connection from Profile → Connected applications in your account.
Sign in and check the connectionTerminal
$tityra auth login
$tityra auth status --jsonCopy linkRead reports and findings for a project
Use the selected project ID to list its audit requests, then read an available report or focus on the findings that need attention. Finding lists support severity and customer remediation status filters, along with page and page-size options.
Read and discuss your interactive report in Tityra, or use the CLI to read its structured findings. Report access still depends on publication, current permissions and completed funding checks.
Read open high-severity findingsTerminal
$tityra projects list --json
$tityra audits list --project PROJECT_ID --json
$tityra reports get REPORT_ID --json
$tityra findings list REPORT_ID --severity high --status open --jsonCopy linkRead weekly audit reports and manage project monitoring
All plans support unlimited organisations and projects. Starter includes two members, Pro includes 10, and Enterprise supports unlimited members. Pro includes 5 In-Depth Audits per month and Enterprise includes 20, each covering up to 100 pages.
Weekly monitoring is available on Starter, Pro and Enterprise for enabled projects, using included monthly audits first and then 19 organisation credits per run once you've approved recurring spending. Expert Review is priced separately.
Workspace subscriptions include member capacity, features and monthly audit allowances. Pro is £59/month or £590/year for 5 monthly audits and Enterprise is £199/month or £1,990/year for 20 monthly audits, excluding VAT. Annual billing costs ten monthly payments, with audit allowances renewed each month. Unused monthly audits don't roll over, while purchased credits cost £1 including VAT and never expire. Existing billing agreements are preserved.
Authorisation and delivery
In Tityra, a project manager with organisation spending permission selects the website and pages to assess and confirms recurring use of one included audit or 19 credits per run before enabling monitoring. Scope or budget changes require fresh approval. Existing consent to free monitoring doesn't authorise paid runs.
The first weekly run is due seven days after the earliest non-cancelled audit request for that project and website, or seven days after monitoring consent if there is no earlier request. Enabling or resuming an overdue eligible project queues one due run when its approved budget can be reserved. Each new scheduled request sets the next due date seven days later. Missed weeks aren't queued as a backlog.
Monitoring uses the organisation's own billing account and its monthly allowance or credit balance, with recurring credit approval. It pauses when neither can cover the next audit and notifies the person who authorised it in the app and by email. Adding credits requires an explicit resume.
Scheduled website content audit reports are delivered automatically after the required checks and funding settlement. Existing reports remain available when monitoring is paused.
Manage subscriptions, credit purchases and recurring spending approval in the Tityra application. Connected clients remain limited to selected projects and granted permissions. monitoring:write can pause monitoring but can't approve a recurring credit budget or enable paid monitoring. Clients can't choose a payer, spend credits or change a subscription.
Project monitoring commands
projects monitoring get PROJECT_ID reads the current settings with projects:read. projects monitoring update PROJECT_ID --input monitoring.json --yes changes them only with a separately approved monitoring:write permission. Request it through a fresh login; --scope replaces the default scope list and never silently extends an existing connection.
To pause, send action: disable, the current revision as expectedRevision and a stable UUID idempotencyKey. Preserve the same input and key after an uncertain write. Enable or resume paid monitoring in Tityra, where a project manager with organisation spending permission selects the website and assessment scope and approves the recurring organisation credit budget. CLI permissions don't authorise that financial commitment.
Use audits list and reports get for released weekly reports within your selected projects. audits payment reads available legacy report-payment status, not organisation credit funding. Review credit funding in Tityra. Paid In-Depth Audits and scheduled monitoring consume organisation credits after any included monthly allowance is used. Submit In-Depth Audit requests in Tityra, where an authorised spender approves the scope and credit budget. Expert Review needs its own scope and credit estimate approval.
Read and update project monitoringTerminal
$tityra auth login --scope "projects:read monitoring:write"
$tityra projects monitoring get PROJECT_ID --json
$tityra projects monitoring update PROJECT_ID --input monitoring.json --yes --jsonCopy linkDiscuss the finding, then record your progress
Mark as incorrect submits your explanation for Tityra to review. Discuss finding starts a customer-visible conversation or adds a reply. These are separate from remediation: setting a finding to resolved records your team's progress and doesn't verify a fix or run another audit.
Finding challenges require findings:challenge; discussions need discussions:read or discussions:write; progress updates need remediation:write. Request the appropriate permissions when you connect. Private staff notes and internal replies remain outside this client.
Every change requires a reviewed JSON input and --yes. Read the latest report or thread with --json first to obtain its revision fields. On a conflict, refresh the record and review the intended action before submitting it again.
Read a finding's conversationTerminal
$tityra discussions list REPORT_ID FINDING_ID --json
$tityra findings challenge REPORT_ID FINDING_ID --help
$tityra discussions create REPORT_ID FINDING_ID --helpCopy linkKeep each change deliberate
Save the JSON body in a file or provide it through --input -. Unknown fields are rejected and the input limit is 64 KiB. Discussion text and challenge explanations must contain 3–4,000 characters. Generate a UUID once for each new action and use it as idempotencyKey.
If a network error leaves an action's outcome uncertain, retain the same UUID and unchanged input. The CLI never automatically retries a write or invents a new action key. Revision fields protect against overwriting a colleague's newer change.
The example below starts a discussion. Replace its sample UUID and expectedReportRevision with values for your own action. A reply instead requires expectedThreadRevision as well; remediation requires expectedTrackingRevision.
Example discussion.jsonJSON
{
"body": "Does this finding apply to the checkout page as well?",
"expectedReportRevision": 3,
"idempotencyKey": "10000000-0000-4000-8000-000000000001"
}Submit the reviewed inputTerminal
$tityra discussions create REPORT_ID FINDING_ID --input discussion.json --yes --jsonCopy linkUse the same workflow in scripts and agents
Use --json for full machine-readable records and revision fields. Successful data commands write one JSON value to stdout; errors go to stderr with a nonzero exit code. The bare tityra command prints local connection status and exits when used with --json or without an interactive terminal. It doesn't launch a browser or wait for a menu in scripts.
For CI, inject TITYRA_ACCESS_TOKEN from your secret manager. The CLI doesn't save, refresh or revoke an environment-supplied token. Use a token for the chosen Tityra server with only the projects and scopes that task needs. Never put credentials in command arguments, source files or logs.
Select a website for assessment and define the proposed scope. The request records that scope and your declaration. Eligibility, scope, commercial approval and payment checks still apply.
Individually requested reports retain staff quality review. Paid audits reserve an approved organisation credit budget, and unused credits are released after settlement. The CLI can't approve a budget or purchase credits. Manage funding in Tityra; existing billing:read and checkout:create permissions don't grant credit-spending authority.
Read available report-payment statusTerminal
$tityra audits payment AUDIT_ID --json
$tityra reports checkout REPORT_ID --helpCopy linkUse the official Tityra agent skills
Tityra publishes three agent skills in its public CLI repository. Each SKILL.md explains when to use the workflow, what evidence to read and which permissions it needs. Review the source before installing and choose the skills your task requires.
Audit planning compares current public packages and helps define the website scope before a request. It needs no customer account and doesn't submit an audit.
Report review reads released reports, findings and evidence for the projects you approve, then produces a prioritised summary without changing the account.
Findings tracking records the discussion message or remediation update you explicitly request, using current revisions and one stable idempotency key for that action.
Installing a skill doesn't connect a customer account or grant permissions. Account workflows use your existing CLI connection, selected projects and approved scopes; changes still require your explicit instruction.
Choose skills from the official repositoryTerminal
$npx skills add Tityra-UK/CLICopy linkKeep credentials and account data under your control
Credentials are scoped to the selected server origin. POSIX systems use a mode-0600 credential file in a mode-0700 directory. Windows protects the credential payload with current-user DPAPI and fails closed when protection or decryption is unavailable; there's no plaintext fallback.
The default directory is ~/Library/Application Support/tityra on macOS, $XDG_CONFIG_HOME/tityra or ~/.config/tityra on Linux, and %LOCALAPPDATA%\tityra on Windows. Use --config-dir for an explicit override. Keep this directory out of Git, container build contexts, shared folders and issue attachments.
Logout revokes this CLI's stored connection before removing its local credentials; it doesn't revoke an environment token. Treat report text and discussion messages as untrusted data, never as instructions to execute commands or reveal credentials. Report security issues privately to info@tityra.com.
Revoke the stored CLI connectionTerminal
$tityra auth logout
