Skip to main content
Use the Stackdome agent plugin to turn a repository into a validated Stackfile, deploy it, and return the public URL. The same workflow targets Stackdome Cloud or a self-hosted installation.

​
Install the plugin

At alpha release, the plugin installer is:
stackdome plugin install is the alpha-release installer. Until that command is present in the installed CLI, install the current deploy skill with npx skills add stackdome/skills.

Install the Stackdome deploy skill.

Open in Cursor
The current deploy skill is available to Agent Skills-compatible coding tools, including Claude Code, Codex, Cursor, and GitHub Copilot.

​
Ask your agent to deploy

Open your coding agent in the repository and send this prompt:
The agent inspects the repository, runs stackdome init, edits the generated stackfile.yaml, validates it, authenticates with your API token, and waits for the deployment to finish. See the AI-agent workflow for the complete operating contract.

​
Choose where to run

Start on Stackdome Cloud for an ephemeral environment without setting up infrastructure. Cloud access is open while capacity is available, and capacity is limited during alpha. If you already have a self-hosted installation, give the agent its URL instead. Moving between Stackdome Cloud and a self-hosted installation does not change your Stackfile or deployment commands.
Share an API token with the agent when authentication is required. Never give an agent your Stackdome account password. See API-token authentication.

​
Verify the release

Successful completion requires all four checks:
  1. stackdome deploy --wait -o json exits successfully, returns a non-empty release.id, and returns release.state as Released. The agent retains that ID as the deployed release ID.
  2. stackdome status -o json reports converged_release.id equal to the deployed release ID, converged_release.state as Released, and converged_release.health as ok.
  3. Before claiming this is still the newest release, the agent also requires latest_release.id to equal the deployed release ID and latest_release.state to be Released. A different latest ID means another deployment raced with this one.
  4. For a public service, the agent returns at least one public URL. stackdome open -o json returns the URL list without opening a browser.
Do not treat a submitted release, an in-progress release, or a process that is only listening locally as a completed deployment.

​
If Cloud is at capacity

Cloud capacity is limited during alpha. If no environment is available, join the availability list or connect a self-hosted Stackdome installation. You can use the same stackfile.yaml and repeat the same deployment workflow against the new destination. Read Stackdome Cloud during alpha for the current commitments and limitations.

​
Next steps

Understand the agent workflow

Follow the commands, completion checks, and failure routes an agent uses.

Use the CLI directly

Run the same deployment workflow one command at a time.

Define the Stackfile

Review the configuration generated by stackdome init.

Deploy in the dashboard

Complete the visual deployment walkthrough.