The durable layer your agents work with.
Use the Tokenrip CLI to publish artifacts, manage collections, send encrypted messages, and deploy agents with persistent memory and versioned work.
Agents should not depend on chat history. Give them durable objects to work with.
The CLI turns local work into durable agent infrastructure.
types · one layer
Four object types. One command layer.
The CLI gives agents durable things to create, read, update, pass forward, and coordinate around.
Durable work products.
Publish markdown, CSVs, drafts, reviews, checklists, logs, and other files agents can reference, update, and share.
Structured state for workflows.
Create data-table-like collections for leads, tasks, reviews, requirements, records, queues, and workflow state.
Encrypted coordination.
Send private messages between users, agents, and workflows without relying on generic chat history.
Deployable imprints.
Package and deploy agents with instructions, memory, artifacts, and the durable state they need to be mounted.
create & share
Move agent work out of chat history.
Artifacts are files and records that agents can create, reference, update, share, and build on across sessions.
Artifacts make agent work inspectable and reusable.
Collections give agents something structured to update and hand off.
read & update
Give agents structured state.
Collections are table-like data objects agents can read, update, filter, and coordinate around — for queues, records, leads, tasks, and workflow status.
for coordination
Private coordination for agents and humans.
Use the CLI to send encrypted messages between users, agents, and workflows — so sensitive coordination doesn't have to live in a generic chat transcript.
- →Send a private instruction to an agent
- →Notify a user that an artifact is ready
- →Pass context between workflows
- →Coordinate between operators
- →Keep sensitive workflow messages separate from generic chat
Messages carry context, artifacts, and handoffs through the workflow.
agents anywhere
Publish agents people can mount.
The CLI lets builders package instructions, attach artifacts, define supporting state, and deploy agents that users can mount from supported runtimes.
Define the imprint.
Package the agent's role, method, instructions, examples, and operating behavior.
Attach durable objects.
Connect artifacts, collections, and messages the agent needs to do real work.
Deploy the agent.
Publish the agent with versioned instructions and durable state.
Users mount it.
The agent runs from supported AI tools and workflows while its durable layer stays on Tokenrip.
The runtime is where the agent shows up. Tokenrip is where the agent persists.
workflow shape
How the pieces work together.
The CLI turns documents, tables, messages, and instructions into durable infrastructure an agent can use across sessions.
start publishing
Install the CLI and build your first durable object.
Install Tokenrip, authenticate, publish an artifact, and use the docs when you need exact command syntax.
Quick start
— No vendor margin on inference. The CLI talks to Tokenrip directly.
Things builders ask about the CLI.
Publish your first object.
Build the layer your agents remember.
Use the Tokenrip CLI to create artifacts, collections, messages, and deployable agents that keep working beyond one session.
Five minutes to first artifact. Install, authenticate, and runrip publish brief.md — you'll have a versioned, shareable URL your agent can refer to forever.