extension_workspace_create

Create an extension.dev workspace that does not exist yet, without opening the console.

Quick start

Create a workspace called acme on extension.dev

How the agent uses it

Use it before extension_project_create when the project's workspace is not there: project creation can only target an existing workspace, and this tool is what brings one into existence. Two-phase, like login: the first call returns a code and a URL where a signed-in GitHub user approves creating exactly this workspace and becomes its owner; call again with the returned deviceCode to finish. Check ownerGithubLogin in the answer: whoever approved the code owns the workspace. The approval mints a grant that lives minutes, can only create the one named workspace, names no project, and is kept on this machine only while a create's outcome is unknown: then it sits in a file only this user can read, beside the stored logins, so calling again with the same deviceCode reads that outcome with no second approval. Then run extension_project_create against '<workspace>/<project>'.

Reference

Group	platform, on with --features=local,platform (private alpha)
Tier	Platform
Needs	the server started with --features=local,platform
Read only	no
Destructive	no
Idempotent	no
Reaches the open web	yes

Inputs

Input	Type	Required	Default	What it does
workspace	string	yes		Slug of the new workspace, lowercase letters, digits and hyphens, no slash. It must not exist yet; a personal workspace (the GitHub login) already exists for every signed-in user, so this is for a shared or organization-style workspace.
displayName	string	no		Human name for the workspace. Defaults to the slug.
description	string	no		Short workspace description. Optional.
developerUrl	string	no		Public URL for the workspace. Optional.
deviceCode	string	no		Resume token from the prior call's deviceCode; omit on the first call.
api	string	no		Platform base URL (default EXTENSION_DEV_API_URL, else https://www.extension.dev)

When it fails

• The tool is missing from the client's list. Start the server with --features=local,platform; see Platform tools.
• The answer reads status: "platform-held". extension.dev is not open to the public yet, so nothing ran on its machines. Creating, running and building an extension still work on your machine; see Use the platform from your agent.
• The answer depends on the network. This tool reaches the open web, so a refusal can be the network, not the project.

Next

• MCP server: install, the two groups and the session gates
• Install in your client
• extension_auth: Sign this machine in to extension.dev, report that login, or clear it.
• extension_builds: Read, rebuild and configure the platform's builds of the logged-in project on extension.dev.
• extension_preview_web: Preview an in-progress extension in the web emulator, with no real browser.
• extension_project_create: Create an extension.dev project for an extension that does not have one yet, without opening the console.
• extension_publish: Publish the project your stored token is scoped to (extension_auth, or EXTENSION_DEV_TOKEN) to extension.dev, and return its shareable URL.
• extension_release_promote: Promote a built extension to a release channel (stable, preview, beta, …) on extension.dev, headless.
• extension_release_status: Read where a project stands on extension.dev, from the public registry (registry.extension.land).
• extension_shares: List, create and revoke the public preview links this token has shared, which is what extension_preview_web share:true hands out.
• extension_submit: Submit a built extension for store REVIEW through extension.dev, which holds your store credentials and dispatches from your project's mirror CI: the Chrome Web Store, Firefox A...
• extension_workspace: Read the extension.dev workspace a stored login belongs to: its plan and limits, its projects, and its usage.