TORQ dashboard in action — September 17, 2026

Watch TORQ's dashboard in action: plan a task, inspect the diff and structural checks, request a correction, accept the reviewed candidate, explicitly apply it, and continue from the updated project.

Watch / download the 92-second demo (MP4)

Recorded on Windows on September 17, 2026, using the dashboard code merged in PR #82, main commit c1c6948472d1ab542550e9a8759d89abbca8e9ec.

This is a real browser recording of the application, launched through a local test harness with an offline deterministic provider. No live AI service is called. The provider subprocess, structural checker, signed receipts, and file application are real. The video is silent, with a persistent provider disclosure; only the opening idle time was trimmed.

What was verified

• 15 focused regression tests passed, with zero failures or skips: candidate review, signed decisions, native file transactions, history, task HTTP, and dashboard JavaScript behavior.
• The project still contained the original subtraction implementation after Accept.
• Apply wrote the exact reviewed addition implementation and docstring.
• Both candidate chains, both decision chains, and the application chain verified and were sealed.
• Continue opened a fresh draft based on the updated project.
• Four real subprocess launches: two fixture-provider runs and two structural-check runs.

The in-app checks validate file structure; they do not run the generated project's unit tests. The separate 15-test regression suite tests TORQ itself. This fixture demo does not establish live-provider compatibility.

This page contains demonstration assets, not a new software version. It does not replace the latest stable release.

TORQ CLI v0.2.0

TORQ CLI 0.2.0

TORQ 0.2.0 is a governed agent runner: every run is attested, dry-run by default,
and backed by a verifiable receipt chain.

What is new since 0.1.0

• Governed orchestration boundary. torq run executes the full
  G1D → G1R → Builder → G2A pipeline. HIGH defects route through a bound
  repair lane, and a targeted G2A re-audit runs before a run returns
  awaiting_approval. Invalid config, credentials, regional routing, or
  missing transport binaries fail before a run directory is created.
• Evidence-backed Fleet chat. torq fleet --serve exposes an attended
  chat surface over verified run evidence. Provider processes run under
  OS-enforced containment — production-enabled on Windows; Linux and macOS
  fail closed.
• Native credential storage. torq auth store keeps provider secrets in
  the Windows Credential Manager, macOS Keychain, or Linux Secret Service as
  opaque credref_ handles; an attended, passphrase-protected encrypted-file
  vault is available for headless machines. auth verify-access confirms
  access without printing or transmitting the value.
• One-command trial. torq demo --run scaffolds a valid identity and
  attestation, executes a real dry-run, and leaves a run directory that
  torq evidence verify confirms — no provider calls, no hand-written JSON.
• Platform honesty. Commands report exactly what is production-grade and
  what is not; torq trust readiness names the signing and anchoring gaps
  still open.

Install

pip install torq-cli        # Python 3.11–3.13

Try it in one command

torq demo --goal "Add input validation to the login form" --run
torq evidence verify --run-root ./torq-demo-runs/<run-id>

Verification

Release evidence — signed tag, artifact hashes, multi-OS CI, clean-machine
installs, and live provider smokes — is attached to the release. Security
guarantees and limits: SECURITY.md. Internal gate detail:
docs/releases/torq-cli-v0.2.0.md.

TORQ CLI v0.1.0

TORQ CLI 0.1.0 release notes

Release tag: v0.1.0 in the standalone repository, per the repository-home
decision. Do not create the tag until every release gate is green.

Security guarantees and limits are in SECURITY.md. The dated
production-readiness audit is
docs/security/production-readiness-audit-2026-07-23.md; installation is in
docs/install.md.

Non-goals

• The tool never commits, pushes, or merges.
• The v0.2 UI is not included.
• Formal V6 contract publication, MMH consensus, remote receipt anchoring, and
  provider pricing tables are deferred.
• Recorded/mock provider conformance is not proof of live provider access.

Required release evidence

• Signed tag and artifact hashes match the tagged build.
• Protected main requires the Windows, macOS, Linux, and headless CI checks.
• Clean-machine installation and credential-backend access pass on all three OSes.
• All six manual live provider smokes pass with resolved-model attestation.