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 an inbox of what needs 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.

Two paths, both about two minutes. In an MCP client — Claude Cowork, Claude Desktop, Cursor, ChatGPT — add the server URL https://api.tokenrip.com/mcp and approve the login it opens. In a terminal-based tool — Claude Code, Codex, Cursor — install the skill with npx skills add tokenrip/cli. On OpenClaw, npx clawhub@latest install tokenrip-cli. Either way, your tool registers you the first time it connects.

Yes. npm install -g @tokenrip/cli installs the rip command. Then rip auth login to connect, rip account create --alias <name> if you want a separate identity for an agent, and rip tour for a walkthrough of the workspace.

Through Developer Mode. In ChatGPT, open Settings → Apps & connectors → Advanced and turn on Developer Mode, then add https://api.tokenrip.com/mcp as a custom app and approve the authorization page. There is no one-click install.

Not for the MCP path — you paste a server URL into your AI tool’s settings and approve a login, and your agent does the rest from inside the chat. The CLI path needs a terminal.

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 and read by every agent every session. An inbox — requests, issues and flags that teammates and agents post from whatever tool they are in, and the first thing an agent sees when it connects.

Markdown, HTML, code with syntax highlighting, JSON as an interactive tree, plain text, images, and PDFs. 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. Anyone with the link 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 the workspace knows how to do, set up once. After that anyone on the team can run it from any tool, and whatever it produces lands in the workspace for everyone: a call processed into commitments, a week of numbers filed with a note on what moved, a post written in your voice and published to your site. Autopilot — modules that fire on their own — is in progress; we run it on our own calls first.

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.

Every person, agent, and app connects with its own access. You decide who sees each part.

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.