tokenrip/cli

The shared workspace for people and AI agents, from the command line. A Tokenrip workspace keeps a project's artifacts (markdown, HTML, charts, code, JSON, CSV, PDFs, images, living tables), folders, and tasks together so any agent can pick up where the work left off. The CLI also calls external APIs through stored connections, deploys static sites, and shares work with teams — every artifact gets a shareable link.

For AI Agents

(Claude Code, OpenClaw, Hermes Agent, Cursor, etc.)

Skill: rip | tokenrip.com

# Claude Code / Codex / Cursor / generic — full skill installation (recommended)
npx skills add tokenrip/cli

# OpenClaw skill
clawhub install tokenrip-cli

# CLI only — no skill
npm install -g @tokenrip/cli

See SKILL.md for the agent skill manifest and AGENTS.md for agent-specific usage.

Remote MCP server

Tokenrip also runs as a remote MCP server, so Claude, ChatGPT, Codex, Grok, Cursor and any other MCP client can use the same workspace with nothing to install.

• Endpoint: https://api.tokenrip.com/mcp (Streamable HTTP)
• Auth: OAuth 2.1 with PKCE (sign in with your email; Tokenrip sends a six-digit code), or an API key as a Bearer token
• Tool list: tokenrip.com/mcp

# Claude Code
claude mcp add --transport http tokenrip https://api.tokenrip.com/mcp

# Gemini CLI
gemini extensions install https://github.com/tokenrip/cli

For Cursor, VS Code and other clients, add https://api.tokenrip.com/mcp as a remote server (see .mcp.json and llms-install.md). After connecting, call workspace_list, then workspace_load.

Install

npm install -g @tokenrip/cli

Quick start

# 1. Sign in with your email (Tokenrip emails a six-digit code), then with the code
rip auth login --email [email protected]
rip auth login --email [email protected] --code 123456

# 2. Find a workspace (or create one) and load it: pins, recent sessions, tasks, recent changes
rip workspace list
rip workspace create q1-report --name "Q1 Report" --why "Get the Q1 report to the board by Friday"
rip workspace load <workspace-id>

# 3. Publish an artifact into it — or omit --workspace-id for a standalone artifact.
#    Every workspace write says why: the person's goal, not a description of the edit.
rip artifact publish report.md --type markdown --title "Q1 Report" --workspace-id <workspace-id> \
  --why "Get the Q1 report to the board by Friday"

# 4. See who worked here: each goal with the changes made for it, versions and diffs
#    (sessions record themselves; nothing to end)
rip workspace sessions <workspace-id>

Every command outputs formatted human-readable output by default:

ID: abc-123
URL: https://...
Title: Q1 Report

Pass --json or set TOKENRIP_OUTPUT=json for machine-readable JSON output.

Several agents, one account

Every agent you connect (this CLI, a chat app through a connector, a hosted agent) joins your one Tokenrip account with its own key, so they all see the same workspaces. Connecting one never disconnects another.

• Next agent, no email: run rip auth code and paste the line it prints into the next agent. The setup guide for every kind of assistant is at tokenrip.com/setup.
• A host that takes a pasted key (a key vault or settings field): rip auth keys create --name "<host>". Paste the key there, never into a chat.
• See or remove agents: rip auth keys, rip auth keys revoke <id>, or the dashboard's Agents page.

Library usage

@tokenrip/cli also works as a Node.js/Bun library for programmatic artifact creation.

import { loadConfig, getApiUrl, getApiKey, createHttpClient } from '@tokenrip/cli';

const config = loadConfig();
const client = createHttpClient({
  baseUrl: getApiUrl(config),
  apiKey: getApiKey(config),
});

const { data } = await client.post('/v0/artifacts', {
  type: 'markdown',
  content: '# Hello\n\nGenerated by my agent.',
  title: 'Agent Output',
});

console.log(data.data.id); // artifact UUID

See CLI.md for the full exports table.

Full command reference

See CLI.md for every command, every flag, configuration, environment variables, and error codes.

Security

See SECURITY.md.

License

MIT

HTTP client and transport failures

The library's createHttpClient() returns a configurable Axios instance with a 30,000 ms default. Factory timeout: 0 retains that default; per-request timeout: 0 disables the timeout. In native environment-proxy mode, client-owned agents coordinate the effective connection timeout with existing Axios response/transfer semantics. This is not a whole-command deadline. Caller agents, adapters, transports and explicit proxy choices retain their policy. Compatible requests reuse finitely idle, unreferenced sockets; overrides and cancellation own resources until completion or stream closure.

Available local TIMEOUT / NETWORK_ERROR details distinguish measured elapsedMs from configured timeoutMs, include an allowlisted transportCode when known, and report responseReceived plus httpStatus for observed replies. No response does not prove a write failed to commit. The CLI never retries sign-in automatically; a committed lost response can consume a code without saving its key. See transport troubleshooting before repeating a write.