Skynet Chrome CDP
Attach to the Chrome you are already signed into. Structural page perception, explicit tab ownership, and a benchmark that states its fixture.
- 85 tests, zero dependencies
- 0.33 ms median round trip, n=200
Local-first autonomous operations
Skynet runs and verifies browser workflows before declaring them complete.
Built for teams that need AI to operate real tools while preserving the executor, artifact, and receipt behind every completion claim.
Verified The run shown here is documented in a published production field note.
Production publishing canary
Request-to-receipt trace
Verified
- RequestPublish a source-backed field note
- RiskPublic claim; review required
- ExecutorRegistered publishing lane
- ActionWordPress canary published
- ArtifactLive page and preview image
- ReceiptURL, archive, image, and signature checked
Open source
Three tools you can run today.
All three are MIT licensed. The two tools have zero dependencies and ship a numbered specification whose every requirement maps to evidence â clone them, or take the single file and run it on a machine you cannot install anything on. The desktop app ships as a Windows installer.
Skynet AI File Blast Radius
Before you edit a file: what else breaks, how far it cascades, and which of it no test reaches. Eleven direct importers can hide 366 transitive dependents.
- 98 tests, zero dependencies
- Risk score ships its own formula
Skynet Desktop
One window for the Claude, Codex and Gemini command-line agents, on Windows. Run them side by side instead of juggling terminals.
- MIT licensed, v0.1.1
- Signed-in agents in one window, no API keys
Chrome ships breaking changes monthly and these keep pace with it. If they save you an afternoon: sponsor the work — sponsorship, not equity or investment.
Verified evidence
A completion claim has a fixed evidence shape.
These are operating requirements, not article-volume or engagement claims.
- Risk classifiedThe reason for review is visible.
- Executor namedThe acting lane is recorded.
- Artifact persistedThe output exists beyond the tool call.
- Receipt checkedAn independent signal closes the run.
One live workflow
The proof boundary is part of the product.
A real publishing canary shows how Skynet separates intent, execution, and verification instead of treating a successful tool response as the finish line.
RequestSource-backed articleIntent frozen
Risk classPublic claimReview branch opened
ExecutorPublishing laneRole recorded
Browser actionCanary publishedAction receipt saved
OutputLive articlePreview and archive visible
ReceiptIndependent checks passCompletion allowed
Verified
Live today
Source-backed web publishing, browser workflows, viewport audits, and evidence receipts.
Review
Experimental
Broader self-improving routing across changing provider and application surfaces.
Blocked
Not accepted
Proof-free completion claims, silent provider substitution, or missing live artifacts.
Proof-backed case studies
Three systems. Each one opens to evidence.
The strongest demonstrations replace a catalogue of claims: local machine learning, visual desktop control, and verified publishing.
Placement verified
Unsupported-GPU machine learning with a truth gate
The run verified model placement on the local AMD device, compared the measured path with the CPU, and withheld forecasts when validation was incomplete.
- Claim
- Device placement was observed
- Evidence
- Benchmark and withheld-output record
Measured
ScreenMemory perception-to-action
The visual control stack combines targeted screen capture, structural automation, semantic navigation, and compressed accessibility context.
- Claim
- Visual control improved through layered perception
- Evidence
- Published methodology and measurements
Live output
Publishing that verifies after publish
AI WP Manager is one implementation inside Skynet: the workflow checks the live URL, archive membership, preview image, and signature after WordPress returns success.
- Claim
- A tool response is not completion
- Evidence
- Live page and independent receipt
Economics and investment case
Move review effort from reconstruction to inspection.
Skynet is designed to make the operational record a by-product of the run. The economic wedge is a reusable control plane, not an unsupported promise about price or speed.
Evidence is reconstructed later.
- Tool success becomes an assumption
- Context fragments across reviewers
- Failures are expensive to reproduce
- Accountability lives in chat history
Evidence travels with the work.
- Risk and executor are explicit
- Artifacts persist outside the model
- Receipts make failures inspectable
- Recovery becomes reusable memory
Latest proof dispatches
Read the operating record, not a trend feed.
One current Platform dispatch leads the briefing, with two direct paths into the newest source-backed work.
Why Accessibility-Tree Node Counts Are Not Machine-Comparable
Two hosts on the same Chrome build read one byte-identical page as 1,684 and 1,244 accessibility nodes. Why that figure is not portable.
What to expect
Read the featured dispatch
- The operating problem and its real boundary
- The evidence used to evaluate the result
- The limitation or next action left visible
