What people ask before they plug in.

A shared workspace your team and every agent you run plug into. It holds your files, the decisions you’ve settled, and the tasks that need doing. An agent connects over MCP or the CLI, reads what it needs, and writes back what it did — so work done in one tool is there for the next person, in theirs.

Teams whose work already runs through agents in more than one tool. If one person’s agent works something out in Codex and nobody else’s agent can see it, that’s the problem this solves. It works with Claude Code, Codex, Claude Cowork, ChatGPT, Cursor, and any MCP client.

Solo, in one tool, yes. The folder stops at the first boundary: a second person, a second tool, an agent that needs its own view. Tokenrip is what the folder becomes when it has to be shared.

A company brain is a memory. It reads what you’ve written so your assistant can answer questions about it. Tokenrip is an office: where your team and your agents do the work, and what one does is there for the next. It has a memory the way an office has a filing cabinet.

Notion is a workspace for people. This one your agents plug into, from the tool they’re in, and it holds decisions as well as pages.

Paste "Connect me to Tokenrip. Fetch https://tokenrip.com/setup and follow it." into your AI assistant. It reads the setup guide and picks the way in that fits it. All you give it is your email address and the six-digit code Tokenrip sends you.

Ask the first one for a line to paste. It makes a sign-in code for the next agent, so no second email is needed. Every agent you connect joins your one account with its own key, and connecting one never disconnects another.

Yes. npm install -g @tokenrip/cli installs the rip command; rip auth login --email <your email> signs in. The setup guide at https://tokenrip.com/setup has the full steps, and the docs are at https://docs.tokenrip.com.

ChatGPT can add Tokenrip as a custom connector on plans that allow custom connectors (Developer Mode). We haven’t finished our own end-to-end run in ChatGPT yet, so the setup guide gives the general connector steps.

No. You paste one line into your AI tool, and give it your email and a six-digit code. A chat app may ask you to add a connector URL in its settings instead; the setup guide says how.

That is the point. One person can work in Codex and another in Claude Cowork, and both are reading and writing the same workspace. The workspace does not care which tool wrote what.

Three things. Files — transcripts, metrics, research, drafts, published work, versioned with history and a diff. Decisions — the things you have settled, written once as markdown and pinned, so every agent reads them every session. Tasks — requests, issues and follow-ups that teammates and agents file from whatever tool they are in. Any editor can claim one, and open tasks are part of what an agent loads when it connects.

Markdown, HTML, code with syntax highlighting, JSON as an interactive tree, charts, CSV, plain text, images, and PDFs, plus living tables that agents add rows to over time. Each type gets its own viewer on the web, and agents can fetch the same URL as raw content or as JSON metadata instead.

Yes. Writing to a file again creates a new version at the same URL. The URL always resolves to the latest, with a dropdown for earlier versions and a diff between them. Nothing overwrites anything.

Every file has a URL like tokenrip.com/s/abc-123. A file in a workspace opens for that workspace’s members. A file outside a workspace can be shared with a team, or left at link visibility (the default) so anyone with the URL can read the rendered page, no login. The page is server-rendered, so an agent fetching it gets the whole thing without running JavaScript. Send an Accept header of application/json for metadata, or text/markdown for the raw content.

A job you set up once: instructions pinned in the workspace, plus the connections it needs. After that anyone on the team can run it from any tool. Their agent follows the instructions, and whatever it produces lands in the workspace for everyone: a call turned into commitments and tasks, a week of numbers filed with a note on what moved, a post drafted in your voice.

Yes. The REST API is at https://api.tokenrip.com/v0, with an OpenAPI spec at https://api.tokenrip.com/v0/openapi.json. The CLI and the MCP server are both built on it, so anything a tool can do, your own code can do.

Each of your agents connects with its own key, and you can disconnect any one of them from the Agents page. People outside your account see only what you share with them.

No. Your tools and your keys do the thinking. We store, search, and route.

Files and an API. Export everything, any time.

We have not published pricing, and there is no pricing page to send you to yet. Connecting and using the workspace today does not cost anything.

The CLI is open source at https://github.com/tokenrip/cli. Full documentation is at https://docs.tokenrip.com.