---
title: "Workspaces | AgentRQ Docs"
url: https://agentrq.com/docs/workspaces
description: "Create and manage AgentRQ workspaces — isolated collaboration environments for each Claude Code project."
---

[Docs](https://agentrq.com/docs/) / Workspaces

Guide

# Workspaces

A workspace is an isolated collaboration environment — one per project. It holds your tasks, your MCP tokens, and your agent's context.

## What Is a Workspace?

Isolated

Tasks, tokens, and messages are scoped to a single workspace. No cross-contamination between projects.

Token-Gated

Each workspace has its own MCP tokens.

Real-Time

SSE event bus per workspace. All tasks, replies, and status changes are streamed live to the dashboard and to Claude.

Think of a workspace like a Slack channel per project — everything related to that Claude Code session lives in one place, and your agent connects to exactly one workspace at a time via its MCP token.

## Creating a Workspace

1. 1
   Sign in at [app.agentrq.com](https://app.agentrq.com)
   Use Google OAuth2 — no passwords required.
2. 2
   Click "+ New Workspace" in the sidebar
   Name it after your project — e.g., `my-saas-backend`. Names are for your reference only.
3. 3
   Note your Workspace ID
   The workspace ID is shown in the URL (e.g., `/workspace/0ZPO4WBMZIP`) and in settings. You'll need this for your `.mcp.json`.
4. 4
   Copy your Workspace MCP Token
   Go to Workspace Settings → Setup Guide / MCP Token. Copy the MCP connection URL or token.

## MCP Tokens

Expiry

MCP tokens are valid for 1 year. Sessions using an expired token will receive a 401 error and disconnect.

Rotation

Generate a new token anytime. The old token is immediately invalidated. Update your `.mcp.json` and restart Claude Code.

Security

Tokens grant full access to create tasks, reply, and read workspace data. Treat them like API keys. Don't commit them to git.

Multiple Tokens

You can have multiple active tokens per workspace — useful if multiple Claude Code sessions are running on the same project simultaneously.

## Workspace Settings

Rename Workspace

Change the workspace name at any time. The workspace ID and tokens remain unchanged.

Manage MCP Tokens

Generate new tokens, see when existing ones expires.

Delete Workspace

Permanently deletes the workspace, all tasks, replies, and tokens. This action cannot be undone.

## Multi-Project Pattern

The recommended pattern is one workspace per Claude Code project:

// AgentRQ dashboard — your workspaces

● my-saas-backend ID: 0ZPO4WBMZIP

● mobile-app-rewrite ID: 0ZQO2XXXXXXX

○ data-pipeline ID: 0ZRO4XXXXXXX

Each project has its own `.mcp.json` pointing to its workspace. Claude Code sessions are always scoped — there's no cross-project task leakage.

Workspace ready?

Learn how tasks flow between Claude and you.