01
Working context
Memory can help AI work with project preferences, user context, and prior decisions.
FREE TO THINK
● PRIVATE PREVIEW UTC
● PRIVATE AI MEMORY
Private memory
without loose secrets.
TARX Memory gives AI useful private context while keeping credentials, keys, tokens, and sensitive secrets in Vault-grade workflows.
Memory is contextVault is secretsApproved skillsMCP boundaries
Trust wedge
Memory and secrets
are not the same.
AI needs context to be useful, but treating every private fact like ordinary chat history creates risk. TARX keeps working context in Memory and keeps credentials, keys, tokens, and secrets in harder Vault-grade workflows.
TARX Memory
Context that helps
the runtime work.
Memory is for useful working context. It should help the runtime understand preferences, project state, and approved context without turning secrets into casual recall.
02
Private by default
Memory should stay scoped to the user's runtime and approved workflows.
03
Not secrets storage
Passwords, API keys, SSH keys, private keys, and credentials do not belong in ordinary memory.
Vault boundary
Secrets need
a harder wall.
Vault-grade workflows are for credentials and sensitive secrets. The distinction matters for security teams and for any AI runtime that can use tools.
01
Credentials
Secrets should be handled through controlled workflows, not blended into general memory.
02
Approved actions
Tool use and private context should be scoped, visible, and user-approved.
03
MCP context
MCP can expose useful tool surfaces, but private context still needs boundaries and clear source truth.
Proof status
Boundaries stay visible.
This page explains the Memory and Vault distinction that security and product teams can review.
Current proof
Docs for Memory and Vault, approval flows, and MCP context boundaries.
Security note
Ordinary memory is not where credentials, keys, tokens, passwords, or private secrets belong.
FAQ
Questions
answered plainly.
What is TARX Memory?
TARX Memory is private working context that helps the runtime understand useful project and user context.
What is TARX Vault?
TARX Vault is the harder boundary for credentials, keys, tokens, passwords, and sensitive secrets.
Does TARX store passwords or API keys in memory?
No. Those belong in Vault-grade workflows, not ordinary memory.
How is private memory different from chat history?
Private memory is runtime context for work. It should be scoped, reviewable, and separated from secrets.
How does MCP fit into private context?
MCP can provide tool surfaces and context sources, while TARX keeps memory, approvals, and secrets boundaries explicit.
Private preview
Start with
TARX runtime.
Tell us what you are building and where local-first execution should fit.