A patch apply
Code Worker waits. Evidence after.
← Answers
runtime · today · Can an agent write files without asking?
Nothing writes until you allow it.
Not on TARX-OS. Consequential writes wait on Deny or Allow once. Evidence after. Always-on auto-approve is how blast radius becomes someone else’s incident. Writes, patches, terminal, Vault extraction, external sends or deletes wait.
Always-on auto-approve is how blast radius becomes someone else’s incident.
TARX-LOCAL handles private work on your computer. Connections stay off until you allow them.
HOW TARX WORKS
How TARX works at the moment of the write
The educational moment is the dialog. Deny or Allow. Once. Then Evidence. Teams that skip this in the name of autonomy are buying an incident.
This is the same story in enterprise, factory, and government. The file, the patch, the send. TARX-OS waits. Hardware does not get a bypass.
Join on a Mac and you already have the lesson. Get a T-4 or T-70 and the lesson does not change. That is the product.
THE STACK
Join the Supercomputer. Or own Private Hardware.
TARX-OS on computers you already own. Supercomputer hardware when the site needs dedicated NVIDIA.
USE CASES
WHAT THIS PAGE IS FOR.
A terminal command
Gated. Not a free shell.
An external send or delete
Wait. Then a trail.
KEY FEATURES
Dialed to this question.
Wait onWrites · patches · terminal · Vault · external sends or deletes
DecisionDeny or Allow once
AfterEvidence
Anti-patternAlways-on auto-approve
Hardware bypassNone
HOW TO START
Four steps. Same contract.
01
Let the agent propose
The runtime may call approved Skills.
02
See the write
Control shows the consequential act.
03
Deny or Allow
Once.
04
Read Evidence
Who decided, what changed.
FAQ
Questions this page owns.
What waits on approval?
Writes, patches, terminal, Vault extraction, external sends or deletes.
Can we auto-approve everything?
You can raise autonomy. Always-on auto-approve is how blast radius becomes an incident.
Is this only for enterprise?
No. Same Control on a personal Mac and on a T-70.
Does first-run skip approval?
No. First-run stays local. Nothing attaches until you opt in. Writes still wait.
TWO EQUAL PATHSJOIN THE SUPERCOMPUTER.
JOIN THE SUPERCOMPUTER.
OR OWN PRIVATE HARDWARE.
Join the Supercomputer. Or own Private Hardware.
JOIN · TARX-OS
Join the Supercomputer
Always-on agents on silicon you own.
TARX is not a chat app. TARX-OS is the always-on governed runtime for AI agents and work. Install it on the Mac you already have. Chat is how you talk to it. The runtime stays on — goals, skills, approval, Evidence.
Join beta →OWN · TARX HARDWARE
Own Private Hardware.
When local is not enough, attach a TARX machine.
T-1, T-4, T-7, T-70, T-600. Model numbers. They join the Supercomputer — the mesh — for private cluster, burst, or air-gapped sites. Same OS. Same approval. Same Evidence.
Explore Private Hardware →DEPLOYMENT DESIGN · T-4OWN YOUR COMPUTE.
OWN YOUR COMPUTE.
DESIGN THE DEPLOYMENT.
TARX-OS seats are included. Configure the Supercomputer. Watch the math. Submit once.