CONTROL

What can TARX remember, access, and touch?

Govern memory, permissions, credentials, runtime, billing, privacy, and advanced developer surfaces from one place.

Memory

What TARX may remember, forget, or ask you to approve. Ordinary memory is for work context, decisions, and preferences only.

What TARX can read, write, execute, send externally, or ask before touching.

Passwords, API keys, SSH keys, tokens, and private credentials. Credential-like material is never saved to ordinary memory.

Accounts, devices, sync, and app connections TARX can use after authorization.

Computer by default. Supercomputer and enterprise/private runtime by visible route and permission.

Plan, usage, and account controls.

Private by default with visible route boundaries for web, sync, and hosted compute.

Advanced surfaces for workflows, tools, runs, MCP, logs, and runtime internals.

Developer mode

Workflows, tools, runs, MCP, runtime, and logs stay here as advanced controls. They are not the first-run mental model.