Public beta. This walkthrough may change. The checks on this page use saved runs, and what you type stays in your browser.
Check your AI's claims against the evidence.
TrustShell checks the kinds of claims it can read, such as whether a GitHub Actions run passed. It does not see everything your AI did. Try it on a saved example, test it on your own work, then read the report. No account and no key.
Watch an agent get caught
An agent reports that a CI run passed. We wrote two example reports about a real GitHub Actions run, one with the wrong commit. TrustShell read GitHub's own record of the run and marked each one.
The agent said
“The check workflow succeeded on commit 5d1c5e3f57e1, run 39619591025.”
CONTRADICTEDThe claim cites commit 5d1c5e3f57e1; the inspected run is on 392797a69b6a.
Then a true report
“The check workflow succeeded, run 39619591025.”
SUPPORTEDGitHub reports conclusion "success" for run 39619591025 (attempt 1, commit 392797a69b6a); 1 of 1 job concluded success. The line cites this run.
The command ended with exit 1: at least one claim was contradicted. Supported is narrow: a green run supports “this run succeeded”, not “all tests pass”.
See the whole recorded output
Recorded with @hyperdag/trustshell 1.9.3. Observed 2026-11-16T06:18:36.342Z from api.github.com (LIVE at that time). This page shows the recording and sends nothing.
## TrustShell · claims checked against a GitHub Actions run - **Run** `DealAppSeo/trustshell` · run 39619591025 · attempt 1 · commit `392797a69b6a3e57406cef210a8471585667e3af` - **Workflow** `check` · `.github/workflows/check.yml` - **GitHub reports** status `completed` · conclusion `success` · check verdict **COMPLETE** - **Jobs** 1 of 1 read (HTTP 200): 1 success - **Observed** 2026-11-16T06:18:36.342Z from api.github.com (LIVE at that time) - **Evidence class** PLATFORM_REPORTED: GitHub describing its own run. A platform record, not an independent grade. ### Claims: 3 supported · 1 contradicted · 1 not checked - **CONTRADICTED** `commit 5d1c5e3f57e1` - **In** `The check workflow succeeded on commit 5d1c5e3f57e1, run 39619591025.` - **Template** `git.head_sha` - **Why** The claim cites commit 5d1c5e3f57e1; the inspected run is on 392797a69b6a. - **Scope** Commit identity only: whether the commit this claim cites is the one the inspected run ran on. A SHA is matched as a prefix, and a match supports only at 12 or more hex characters. Not what the commit changes or fixes. - **Fields** `/observation/head_sha` - **SUPPORTED** `The check workflow succeeded` - **In** `The check workflow succeeded, run 39619591025.` - **Template** `gha.run_succeeded` - **Why** GitHub reports conclusion "success" for run 39619591025 (attempt 1, commit 392797a69b6a); 1 of 1 job concluded success. The line cites this run. - **Scope** Whether workflow run 39619591025 (attempt 1, commit 392797a69b6a) concluded success with every job read. Not which tests it ran, not any other workflow or check on the commit, and not whether the change works. - **Fields** `/observation/status`, `/observation/conclusion`, `/observation/check/verdict`, `/observation/jobs` - **SUPPORTED** `run 39619591025` - **In** `The check workflow succeeded, run 39619591025.` - **Template** `gha.run_id` - **Why** The cited run is the inspected run, 39619591025. - **Scope** Run identity only: whether the run this claim cites is the inspected run. Not what the run shows. - **Fields** `/observation/owner`, `/observation/repo`, `/observation/run_id` - **SUPPORTED** `run 39619591025` - **In** `The check workflow succeeded on commit 5d1c5e3f57e1, run 39619591025.` - **Template** `gha.run_id` - **Why** The cited run is the inspected run, 39619591025. - **Scope** Run identity only: whether the run this claim cites is the inspected run. Not what the run shows. - **Fields** `/observation/owner`, `/observation/repo`, `/observation/run_id` ### Not checked: 1 claim, and cryptographic integrity (none of these is a pass) - **This workflow run succeeding: not checked.** `The check workflow succeeded` This sentence cites a commit, run or attempt that is not, or could not be matched to, the inspected run, so its outcome claims are not compared with this run. In: `The check workflow succeeded on commit 5d1c5e3f57e1, run 39619591025.` - **Cryptographic integrity: not checked.** No signed attestation was present or verified. This version does not read attestations. ### What this does not prove - This is what GitHub can confirm. It is not a judgement about whether the code is correct. - It cannot show work done outside this repository, or on a branch that was never pushed. - A passing test suite proves the tests that exist passed — not that the right tests exist. - It does not establish who or what authored the change. - SUPPORTED means the platform record matches the narrow scope written next to the claim. It is not a finding that the claim is true in any broader sense. - A successful workflow run shows that run succeeded. It does not show which tests ran, that all tests or all checks passed, or that a change works. - Only this one workflow run was read. Other workflows, check suites and status checks on the same commit were not. - Every observed fact is GitHub reporting on its own run (PLATFORM_REPORTED). Nothing was re-run or independently observed. - Broader security: not checked. A CI conclusion is not a security review. - The record is not signed. Its SHA-256 shows whether the record changed after it was made, not who made it. --- Record `dev.trustshell.action-evidence/0.1-draft` · sha-256 `e81f75af8e2830027002e67cc5fc6ba0eef91150fe3ca2bdc369e3da12f7c5f1` over RFC 8785 canonical JSON · built by trustshell check --claims from api.github.com only; nothing uploaded exit 1
The whole loop, and what works today
Five steps, about three minutes. Each one says whether it works today, and where.
1Watch a catchLive
An agent says its CI run passed on a commit the run never used. TrustShell reads GitHub’s own record of the run and marks that claim contradicted.
See the catchHow we know
Real output of the published 1.9.3 package, recorded on 16 Nov 2026.
2Check yoursLive
Paste one sentence an AI told you. You get Checks out, Caught or Not checked. A GitHub Actions run can be checked from a terminal too.
Check a sentenceHow we know
A scheduled browser test ran this check against the live site on 16 Nov 2026 and passed.
3Name your PAILive
Answer three questions and your personal AI is registered, with its own key kept in this browser. It holds no keys of yours.
Not built yetOne passkey tap that also makes your wallet, with test USDC sent to it for you, so you never visit a faucet.
Build your PAIHow we know
The registration call it makes answered on the live engine on 16 Nov 2026.
4Budget (testnet)Testnet
Connect a wallet and set a cap on what your agent may spend in test USDC. Anything over the cap is refused before it is signed.
Built, switched offGasless deposit: you sign once and pay no gas.
Built, switched offA verified human, not only a builder, holding a budget for their agents.
Set a capHow we know
Base Sepolia only. Today it needs a browser wallet that holds test funds. An owner’s budget shared by two agents also ran on Base Sepolia on 16 Nov 2026; its receipt is on TrustMarket.
5RevokeTestnet
Take your agent back with one wallet signature, or set its cap to 0. Its next spend is refused.
Manage ownershipHow we know
Revoke ownership is on /bind, and a cap of 0 is set on /spend. Base Sepolia only.
What the labels mean (checked on 16 Nov 2026)
- Live
- Works today, for anyone.
- Testnet
- Works today on Base Sepolia, a test network. Test USDC only, so no real money moves.
- Shadow
- Runs and is measured, but changes nothing yet.
- Built, switched off
- The code exists and is off by default. Nothing it does reaches you yet.
- Not built yet
- Designed, not built. The step says what it will do.
- Status not confirmed
- We could not confirm it today, so we do not call it working.
Which sounds like you?
You can change this at any time. Every path goes Try, Test, Report.