---
title: "Workspaces — One Isolated Environment per Project | AgentRQ"
url: https://agentrq.com/features/workspace
description: "AgentRQ workspaces keep your Claude Code projects isolated — dedicated MCP tokens, task history, and real-time event streams per project."
---

Human-in-the-Loop Task Manager for AI Agents

[AgentRQ](https://agentrq.com/) / [Features](https://agentrq.com/features/)

Workspaces

# One Project. One Workspace. Zero Overlap.

Workspaces keep your Claude Code projects completely isolated — dedicated MCP tokens, separate task history, independent event streams. Switch between projects without confusion or cross-contamination.

Your workspaces

my-saas-backend

Claude connected

3

Active

47

Total

2

Tokens

mobile-app-rewrite

Idle

0

Active

12

Total

1

Tokens

data-pipeline

Idle

## What Lives in a Workspace

Everything related to one Claude Code project — scoped, secured, and streamable.

### Task History

Every task Claude has ever created in this project — with full message threads, status history, and attachments.

### MCP Tokens

One or more long-lived tokens per workspace.

### Event Stream

Dedicated SSE event bus. The dashboard and Claude both subscribe to it — all events stay within the workspace boundary.

### Mission Context

Optional mission text returned by `workspace get` — Claude reads it at session start to understand the project's goals and constraints.

## Why Isolation Matters

Without isolation

Tasks from your API project bleed into your mobile project. Claude on one project accidentally sees replies meant for another. Tokens give access to everything — rotate one, break all.

With AgentRQ workspaces

Each project has its own namespace. Claude in workspace A cannot see or affect workspace B. Rotate a token in one workspace — the others keep running. Full audit trail per project.

Real-World Setup

my-saas-backend/ → workspace 0ZPO4WBMZIP

mobile-rewrite/ → workspace 0ZQO2XXXXXXX

data-pipeline/ → workspace 0ZRO4XXXXXXX

Each project directory has its own `.mcp.json` pointing to a different workspace. Total isolation — by design.

Token Scoping

Each MCP token grants access to exactly one workspace. A token from workspace A cannot read tasks from workspace B — enforced at the API level.

Independent Token Rotation

Rotate the token for your API project. Your mobile project's Claude session keeps running uninterrupted. No shared credentials to manage.

Full Audit Trail

Every task, reply, approval, and rejection is stored per workspace. Scroll back through a project's complete Claude ↔ human decision history.

Unlimited Workspaces

Create as many workspaces as you have projects. Free during beta — no workspace limits, no seat limits, no storage caps.

## Set Up a Workspace in 60 Seconds

1

Sign up at app.agentrq.com

Google OAuth — no password, no form, one click.

2

Click "+ New Workspace"

Name it after your project. Copy the workspace ID from the URL.

3

Generate an MCP Token

Settings → MCP Tokens → Generate. Copy it — shown once.

4

Add to .mcp.json

{ "mcpServers": { "agentrq": { "type": "http", "url": "https://WORKSPACE_ID.mcp.agentrq.com/mcp?token=TOKEN" } } }

Free During Beta · Unlimited Workspaces

## One Workspace per Project. Start Now.

Create your first workspace free — no credit card, no usage limits during beta.

More Features

[Real-Time Notifications Zero-latency push — your reply reaches Claude in <50ms](https://agentrq.com/features/real-time-notifications) [Task Board Visual command center — see every Claude request at a glance](https://agentrq.com/features/task-board) [MCP Integration 7 native MCP tools, one config line, SSE transport](https://agentrq.com/features/mcp-integration)