The verification log

A capability counts as verified only with a dated row on this page. A checkmark anywhere on the site links to its row; a row with no run says so.

Verified
1
Registered, unverified
49
Not run here (kiro-cli)
5

Rows

Verified rows first, then the registry order. Each row's anchor is #<harness>-<feature>; the homepage matrix and the registry link here.

Harness Feature Machine Date Evidence Status
claude Claude Code Chat Linux x86_64 container one-shot chat returned a reply via the ACP project's claude-agent-acp adapter (the same adapter the registry now fetches with npx on first run) The adapter was installed by hand for this run; the npx fetch on first run landed the day after and has not been re-recorded. The container has no user namespaces, so the OS sandbox was opted out with its loud warning. Verified
cursor Chat — — no run recorded Unverified
cursor Schedules — — no run recorded Unverified
cursor Channels — — no run recorded Unverified
cursor Approvals — — no run recorded Unverified
cursor Overnight — — no run recorded Unverified
claude Claude Code Schedules — — no run recorded Unverified
claude Claude Code Channels — — no run recorded Unverified
claude Claude Code Approvals — — no run recorded Unverified
claude Claude Code Overnight — — no run recorded Unverified
codex Chat — — no run recorded Unverified
codex Schedules — — no run recorded Unverified
codex Channels — — no run recorded Unverified
codex Approvals — — no run recorded Unverified
codex Overnight — — no run recorded Unverified
kimi Chat — — no run recorded Unverified
kimi Schedules — — no run recorded Unverified
kimi Channels — — no run recorded Unverified
kimi Approvals — — no run recorded Unverified
kimi Overnight — — no run recorded Unverified
dsh DeepSeek Harness Chat — — no run recorded Unverified
dsh DeepSeek Harness Schedules — — no run recorded Unverified
dsh DeepSeek Harness Channels — — no run recorded Unverified
dsh DeepSeek Harness Approvals — — no run recorded Unverified
dsh DeepSeek Harness Overnight — — no run recorded Unverified
goose Chat — — no run recorded Unverified
goose Schedules — — no run recorded Unverified
goose Channels — — no run recorded Unverified
goose Approvals — — no run recorded Unverified
goose Overnight — — no run recorded Unverified
grok Chat — — no run recorded Unverified
grok Schedules — — no run recorded Unverified
grok Channels — — no run recorded Unverified
grok Approvals — — no run recorded Unverified
grok Overnight — — no run recorded Unverified
opencode Chat — — no run recorded Unverified
opencode Schedules — — no run recorded Unverified
opencode Channels — — no run recorded Unverified
opencode Approvals — — no run recorded Unverified
opencode Overnight — — no run recorded Unverified
pi Chat — — no run recorded Unverified
pi Schedules — — no run recorded Unverified
pi Channels — — no run recorded Unverified
pi Approvals — — no run recorded Unverified
pi Overnight — — no run recorded Unverified
droid Chat — — no run recorded Unverified
droid Schedules — — no run recorded Unverified
droid Channels — — no run recorded Unverified
droid Approvals — — no run recorded Unverified
droid Overnight — — no run recorded Unverified
kiro-cli Chat — — no run recorded upstream's mature path · not run here Not run here
kiro-cli Schedules — — no run recorded upstream's mature path · not run here Not run here
kiro-cli Channels — — no run recorded upstream's mature path · not run here Not run here
kiro-cli Approvals — — no run recorded upstream's mature path · not run here Not run here
kiro-cli Overnight — — no run recorded upstream's mature path · not run here Not run here

Not verified yet

Stated here so nobody has to infer it from the gaps above.

  • Overnight runs on any harness

    Planned

    The service mode, cron and the task runner ship; no night has been recorded on any harness. Three dated Claude Code nights are the gate for the site's stronger copy.

  • Channels, schedules and approvals on a non-Kiro harness

    Planned

    The gateway and channel code is shared across harnesses, though each harness has its own capability flags (session sharing, steering, its own sandbox), and nobody has run a channel round-trip, a scheduled job or an in-chat approval on Claude Code, Codex or the others at runtime.

  • The harness router: a subagent sent to another harness

    Planned

    Registered · unverified. Chat sessions run the one harness you choose; the router can send a spawned subagent to another installed harness (flat-rate quota before metered, task kind, a cooldown after a usage limit or a failed login), and it never forwards provider traffic. It is covered by unit tests; no routed run on a live harness has been recorded, and neither has an OpenCode session.

  • The Telegram round-trip on Claude Code

    Planned

    The homepage shows it as a simulation and says so in the caption.

  • “The default build contacts no server of ours”, checked with lsof

    Planned

    Upstream's update feed, app catalog and telemetry are off in the default build; the run that lists every outbound connection during a session has not been done. The embedding model is still fetched on first embedding use from a CDN address inherited from the upstream codebase.

How a row gets added

Rows come from one dated log in the repository, docs/business/verified.md, written by the person who runs the product: the harness, the feature, the machine, the date, the command and what came back. This page updates from that data after a reviewed export and manifest update; nothing here is written from memory.

That file does not exist yet. The one verified row above is recorded in the research notes behind this site and is the first entry the log will carry.

The rule that makes the page useful: a checkmark elsewhere on the site links to a row here, and a capability with no row is written as unverified even when we expect it to work. Public issue reporting is pending with source publication.

Review the local beta.

Apache-2.0 source publication is pending. Read the setup notes and verification limits.

Source publication pending

Public source, install commands and downloads are not available yet. A clean install and live workflow are not yet verified.

Source status Read beta notes