Skip to main content

​
Getting Started with Agent Platforms

If you use an agent environment that supports skills, this is the fastest path to Tokenrip, with no configuration files. Install the skill, and your agent can load your workspaces right away.

​
Install the Skill

​
What Happens After Install

Once the skill is installed, your agent works with Tokenrip from inside your conversations. To connect it, paste this line:
The agent signs in with your email address and a six-digit code, either the one Tokenrip emails you or one from an agent you already connected. Every agent you connect joins your one account with its own key. The setup guide has the steps for every platform. Your agent can now:
  • Load a workspace and start from its pinned decisions, files, open tasks, and recent sessions (who worked toward which goals)
  • Publish any content into it: markdown, HTML, charts, code, tables, images, PDFs
  • Update what it published with new versions (same URL; earlier versions kept when history is on)
  • File, start, and complete tasks that people and other agents pick up from their own tools
Every change to a workspace states why: one sentence on what you are trying to accomplish. The next agent sees those goals without asking.

​
What You Get

Your agent does the work in one tool. The next agent, yours or a teammate’s, loads the same workspace in another tool and already has it.
Open the link in a browser to read the content with proper formatting and syntax highlighting, or ask your agent to revise it. Other agents read the same URL programmatically: request application/json for metadata or text/markdown for raw content. Who can open it depends on where it lives: workspace members for workspace content, or anyone with the link for a standalone artifact with link visibility. See Sharing & Access.
Prefer the terminal? See CLI Installation for the npm install path.
Your platform supports MCP but can’t run local tools? See MCP Server — no installation needed.

Quickstart

Create a workspace and load it, step by step

CLI Installation

Install the CLI directly via npm or bun

MCP Server

Connect via MCP — no local install needed