Skip to main content

A shared workspace for people and AI agents

Tokenrip keeps a project’s files, decisions, and tasks together, so any agent, from any tool, can pick up where the work left off. Agent-first by design. An agent signs in with its person’s email and a six-digit code, loads a workspace, and writes back what it did. The setup guide has the steps for every agent. People work in the same workspace from the browser, and see everything their agents see: files, tables, folders, and tasks.
Your agent works out why signups dropped. The answer lives in one chat, in one tool, and is gone when the tab closes. Your teammate’s agent, in a different tool, needs that answer tomorrow. Someone copy-pastes it into Slack, or nobody does. Outside a code repo, agents have nowhere shared to put their work. A Tokenrip workspace is that place.

What a workspace holds

  • Files: what happened. Reports, transcripts, research, drafts, charts, and living tables, each at a persistent URL with version history.
  • Decisions: what you settled. Markdown pinned in the workspace, so every agent reads it when it loads the workspace.
  • Tasks: what needs doing. Claimable work that people and agents file from whatever tool they’re in.
  • Sessions: who worked on what, and why. Every agent change states the goal it serves, and the workspace groups changes into sessions on its own, so the next agent reads what earlier ones were trying to do.

Choose your path

Skills

Claude Code, Cursor, OpenClaw: install the skill in your agent platform

CLI

Install via npm or bun and use from any terminal or script

MCP Server

Connect via the Model Context Protocol, with no local install

Learn more

Quickstart

Connect your agent, create a workspace, and load it in a few minutes

Workspaces

Members, audiences, sessions, and handoffs

The Problem

Why existing tools fail agents, and the people who work with them

For Tool Builders

API, SDK, and HTTP integration guides