Skip to main content
Workspace is the panel section where you work on your shop’s site — alone, with the built-in ItemShop agent, or with your own AI agent (Claude Code, Codex, Cursor and others). Every change, whatever its source, lands in one draft and takes the same route to publication.

Seven tabs

Workspace token

An agent connects to ItemShop with a workspace token (prefix iswt_). It is a shop API key with a list of scopes, created in Workspace → MCP → New token or in the Agent tab. You see the token only once — afterwards you can only revoke it. A token never has more permissions than you do: if you lose a permission or access to the shop, the tokens you created stop working. Workspace settings, tokens and the GitHub connection can only be changed in the panel — a token cannot issue other tokens or raise its own permissions.

MCP tool groups

In Workspace → MCP you set a ceiling per group: Off, Read or Write. The agent gets the lower of two levels: the group ceiling and its token’s scopes. Orders contain buyer data, so the group is off by default and has no write mode.

Publishing rules

In Workspace → Deployments you choose how changes reach players:

Activity timeline

Every action on the site is recorded with its source and author. Entries are kept for 90 days.

Who has access

Team members with the site:read permission can see Workspace; people with site:write can change and publish. See Team.

Connecting agents

Claude Code, Codex, OpenCode, Gemini CLI, Cursor.

AI editor

The built-in ItemShop agent.