A goal, not a prompt chain
Accept the work. Call approved skills. Stop when a human must judge.
← Answers
runtime · tomorrow · What is an agentic runtime vs a chatbot?
Chat answers. The runtime moves work.
A chatbot returns text. An agentic runtime accepts a goal, calls approved skills, waits on you when it must, and leaves Evidence. TARX-OS is that runtime. Conversation is the interface. The product is the loop: decide, act under policy, observe, continue. Join the Supercomputer on a Mac you already own, or get your own hardware when the work needs dedicated NVIDIA.
TARX is the local-first operating system and governed runtime for AI agents and work. Conversation is the interface. The runtime is the product.
TARX-LOCAL handles private work on your computer. Connections stay off until you allow them.
HOW TARX WORKS
How TARX works when the question is “agent or chat?”
Chat is a window. You type. Text comes back. That is useful and it is not an operating system. Vendors calling orchestration an OS are describing a hosted workflow, not silicon you control.
On TARX-OS the unit of work is a session that can park. A turn can wait on Deny or Allow, a tool result, or a human. Skills are gated. Missing approval is a blocker, not a log line. Evidence is the surface for what information was used, what changed, and who decided.
Join is the path for Apple silicon you already own. Own is T-1, T-4, T-7, or T-70. Same runtime. Same approval. Same evidence. That is how TARX works in every sector: the chat is not 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 write that must wait
Patches, terminal, Vault extraction, external sends — Deny or Allow once. Evidence after.
A team that outgrew chat seats
Join on the Macs they have. Get a T-4 when shared work needs dedicated NVIDIA.
KEY FEATURES
Dialed to this question.
InterfaceConversation
ProductGoverned runtime · TARX-OS
LoopGoal → skills → approval → Evidence
DefaultLocal. Private. Nothing attaches from first-run.
PathsJoin the Supercomputer, or get your own.
HOW TO START
Four steps. Same contract.
01
State a goal
Not a single question. Work that can continue.
02
Let the runtime propose the next act
Approved skills only. Policy in the loop.
03
Approve the write
Consequential actions wait. Missing approval is a blocker.
04
Read Evidence
What ran, what changed, who decided.
FAQ
Questions this page owns.
Is TARX a chatbot?
No. Chat is how you talk to TARX-OS. TARX-OS is the governed runtime that moves work forward.
What is the Supercomputer?
The living mesh of opt-in devices running TARX-OS. Join it, or get your own hardware.
Does an agent run unbounded?
No. Autonomy is adjustable. Consequential actions wait on Deny or Allow.
Can we start without buying hardware?
Yes. Join on Apple silicon you already own. TARX-OS seats are $0.
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.