Skip to content

extension_builds_act ​

Run a build act on the platform: rebuild, recheck, configure the build settings or a channel; read builds with extension_builds.

Quick start ​

Rebuild the last commit for Stable

How the agent uses it ​

A rebuild spends allowance; a push, only on the build branch when it changes the root directory ([skip build] pushes, docs-only, other branches spend nothing).

Page text in the answer ​

Part of this tool's answer is text a web page or the extension wrote. The server fences it between <untrusted-data-ID> and </untrusted-data-ID> with a fresh random ID per call, named in untrusted.boundary. A fence is a signal to the model, not a gate: pair it with --no-ship when the agent reads pages you do not trust. See Server flags and telemetry.

Reference ​

Groupplatform, on with --features=local,platform (private alpha)
TierPlatform
Needsthe server started with --features=local,platform, and a login; a public channel audience needs a workspace owner's approval; delete-channel stays in the console
Read onlyno
Destructiveyes
Idempotentno
Reaches the open webyes

Inputs ​

InputTypeRequiredDefaultWhat it does
action"rebuild" | "recheck" | "configure" | "create-channel" | "configure-channel" | "delete-channel"yesrebuild; recheck: rerun integrity; configure: buildSettings; create-, configure-channel; delete-channel: console only.
buildIdstringnoCommit sha, never the build number. rebuild: the commit to build (default the branch head); required for recheck.
buildEnv"staging" | "production"norebuild: staging (default, Preview) or production (Stable, stores).
buildSettingsobjectnoconfigure: per-browser changes, e.g. { firefox: { buildCommand: 'pnpm build' } }.
approvalIdstringnoApproved approval id.
channelstringnoChannel name, max 40 chars.
descriptionstringnoChannel description, max 200 chars.
colorstringnoChannel color, #rrggbb.
audience"public" | "private"noprivate, or public (owner approval); default the project's visibility.
browserstringnorecheck: chrome, edge, firefox or safari (default all).
projectPathstringnoProject directory; picks its login.
projectstringnoStored login '<workspace>/<project>' when several exist.
waitSecondsnumbernoSeconds to wait for the result (with approvalId, the approval), 0 to 600 (omitted: 180, no wait for the approval); the hosted lane waits at most 45 and names a cut in warnings.
apistringnoPlatform URL; default from env.

When it fails ​

  • The tool is missing from the client's list. Start the server with --features=local,platform; see Platform tools.
  • The platform refuses the call. Log in first with extension_auth.
  • The answer reads status: "platform-held". extension.dev is not open to the public yet and this workspace was not let in early, 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 reads status: "approval-required". The act needs a person's approval. Open the approval URL in the answer, approve it, then call again with the same arguments and the approvalId.
  • The approval is refused as ApprovalExpired. A release, submit or store approval lasts 12 hours; a share link or build settings approval lasts 2 hours, and approving does not extend the clock. Call again with no approvalId to ask for a fresh one.
  • The approval is refused as ApprovalConsumed. An approval runs its act once, and the call that spent it may already have run. Read the current state first, then ask again only if the act did not happen.
  • The approval is refused as ApprovalScopeMismatch. It covers a different act, or the arguments changed since it was approved. Call again with no approvalId.
  • 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 three groups and the session gates
  • Install in your client
  • extension_approvals: List the open approvals this login asked for, read one, or revoke one approved by mistake (owner token) on extension.dev.
  • extension_auth: Sign in to an existing extension.dev project (a code for extension.dev/device, then deviceCode and waitSeconds), list stored logins, or clear them.
  • extension_builds: Read and download platform builds.
  • extension_preview_web: Preview a build in the web emulator; share:true returns a link anyone opens with no install (the preview://build default is for developing extension.dev itself).
  • extension_project_create: Create an extension.dev project from a folder (projectPath, uploaded, no push; again: re-seed and rebuild) or a GitHub repo, BEFORE extension_auth.
  • extension_publish: Publish a build on extension.dev: the link for testers, with a download and a run command for each browser; use it first to share or ship (no project yet: extension_project_crea...
  • extension_release_promote: Release a build to a channel on extension.dev.
  • extension_release_status: Read where a project stands on extension.dev: channels, builds, store submissions and reviews, history, rollout, listings.
  • extension_shares: List, create and revoke emulator preview links for a tester, and list and revoke build links (a build link or channel link comes from extension_publish).
  • extension_submit: Submit a platform build to the Chrome, Firefox, Edge and Safari stores through extension.dev.
  • extension_submit_check: Read a store's state or ask for an approval, with extension_submit's inputs: preflight, status and a dry-run submit answer here; any other action only asks the owner's approval...
  • extension_workspace: Read the workspace; change a project's settings.
  • extension_workspace_create: Create a missing extension.dev workspace, before extension_project_create.