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?
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
Sign in at app.agentrq.comUse Google OAuth2 — no passwords required.
-
2
Click "+ New Workspace" in the sidebarName it after your project — e.g.,
my-saas-backend. Names are for your reference only. -
3
Note your Workspace IDThe workspace ID is shown in the URL (e.g.,
/workspace/0ZPO4WBMZIP) and in settings. You'll need this for your.mcp.json. -
4
Generate an MCP TokenGo to Workspace Settings → MCP Tokens → Generate Token. Copy it immediately — it's shown once.
MCP Tokens
MCP tokens are valid for 30 days. Claude Code sessions using an expired token will receive a 401 error and disconnect.
Generate a new token anytime. The old token is immediately invalidated. Update your .mcp.json and restart Claude Code.
Tokens grant full access to create tasks, reply, and read workspace data. Treat them like API keys. Don't commit them to git.
You can have multiple active tokens per workspace — useful if multiple Claude Code sessions are running on the same project simultaneously.
Workspace Settings
Multi-Project Pattern
The recommended pattern is one workspace per Claude Code project:
Each project has its own .mcp.json pointing to its workspace. Claude Code sessions are always scoped — there's no cross-project task leakage.