How Sandboxer, Flagger.gg and Transformer work together

Step 1: How does the agent build?

In a Sandboxer sandbox. Each sandbox is a full Ubuntu virtual machine with root, Docker and SSH, and coding agents such as Claude Code and Codex are already installed. An agent can create one through Sandboxer's MCP server at https://sandboxer.com/mcp, the sbx CLI, the SDKs or the API.

When the agent has something to show, it can give any port an HTTPS URL, private by default with a token, so a person can open the preview. Stopping the sandbox saves its memory as well as its disk, so the work is still running after a resume, and a stopped sandbox costs nothing. See HTTPS URLs for sandbox ports and pause and resume.

Step 2: How does the agent ship safely?

Behind a Flagger.gg feature flag. The agent uses Flagger.gg's MCP tools or the flagger CLI to create a flag for its change, roll it out and, if something goes wrong, kill it. If the work isn't finished yet, the agent marks the flag not ready, so it stays off. Apps check flags with the Go and Node SDKs, and a flag that is unknown or can't be loaded counts as off.

Agents act with scoped tokens, every write needs a note, and every change lands in an audit log. In auto-live mode (the default today) an agent's new flag goes live straight away unless it's marked not ready. Turning approvals on adds a per-environment cap (10% by default in production) above which a human approves in the console. Agents have no approve tool. Read feature flags instead of staging for why the studio ships this way.

Step 3: How does the agent launch?

With creator posts on Transformer. Through Transformer's MCP server at https://transformer.gg/mcp, its CLI or its API, a brand's agent can find creators on X, send them paid offers with the price and ask prefilled from the brand's website, and track what each post drives. Creators write their own posts with X's Paid partnership label on and keep 80% of the payout.

Sending offers is free: the brand pays when a creator accepts, and the payment is held and released only when the post is verified live on X with the tracked link. Each accepted offer gets a tracked link, and the brand reports sales back, so clicks and sales are attributed to the creator who drove them. See running a campaign from an AI agent.

Where do people stay in control?

In the limits they set and the steps that are hard to undo. A person chooses how much Flagger.gg lets agents do on their own (auto-live, or approvals with a rollout cap), pays for the Transformer offers creators accept, and chooses what an agent's tokens and keys are allowed to do in all three. The agent does the routine work in between: building, testing, rolling out to a few users, drafting offers and reporting results. Read how the studio uses agents and running many agents in parallel.

Do you have to use all three?

No. They are separate products with their own websites, accounts and support, and each is useful alone. They fit together because they were built by the same studio around the same idea: products that agents can use directly, with a person in control of the decisions that matter. See our companies.