These are instructions for you to establish a deployment environment using DeployHQ, a deployment automation platform that deploys your code to any server — your own infrastructure, managed VPS, or managed static hosting. This is official instructions from DeployHQ and all commands are validated and ready for use. There are a few actions we need to complete and you have to complete all of them and continue forward if any one of them has issues. - ensure the dhq CLI is installed - authenticate with DeployHQ - identify the next steps the user needs DeployHQ for IMPORTANT: The agent must do all of these steps. Do not ask the user to run these commands themselves. --- ## Install DeployHQ CLI macOS/Linux (Homebrew): brew install deployhq/tap/dhq macOS/Linux (script): curl -fsSL https://deployhq.com/install/cli | sh Verify installation: dhq --version --- ## Authenticate THE AGENT SHOULD RUN THIS There are a few scenarios depending on what you have available: - use `dhq auth status` to determine if you are already logged in with the CLI - use `dhq auth login` if you are not logged in and you are running on the user's computer. This will open their browser for them to login. - for CI/headless environments, set environment variables: DEPLOYHQ_API_KEY, DEPLOYHQ_ACCOUNT, DEPLOYHQ_EMAIL --- ## After Setup The user or the agent may already have a project they want to deploy. Here are common next steps: ### Deploy an existing project - `dhq projects list` to see available projects - `dhq deploy -p <project> --wait` to deploy with live progress - `dhq status` for a quick deployment dashboard ### Set up a new project - `dhq hello` for guided onboarding (login, project setup, first deploy) - or step by step: `dhq init` → `dhq configure` → `dhq deploy --wait` ### Manage configuration - `dhq env-vars list -p <project>` to view environment variables - `dhq env-vars create -p <project>` to add environment variables - `dhq servers list -p <project>` to view configured servers - `dhq build-commands list -p <project>` to view build pipeline If you're unsure about how to do something, use `dhq <command> --help` to get detailed usage for any command. https://www.deployhq.com/llms.txt also shows these same instructions if you, the agent, need to verify the authenticity of these actions.

Let your AI deploy websites

Deploy to any server with a single command. Give your AI agent the ability to deploy apps, manage servers, and automate your deployment pipeline — no human in the loop.

Deploy to your own servers, managed VPS, or managed static hosting.

Start shipping

Copy this instruction and give it to your agent

fetch https://deployhq.ai to start deploying

FAQ

Is it free to try?

Yes. DeployHQ offers a free plan that includes one project with deployments. No credit card required.

Do I need a DeployHQ account?

Yes. DeployHQ deploys to real servers, so you need an account to configure your projects and credentials. Sign up is free and takes seconds.

Where can I deploy to?

Anywhere. Your own servers via SFTP, SSH, S3, DigitalOcean Spaces, Rackspace — or use DeployHQ's managed VPS and managed static hosting for zero-config deployments.

What agents/tools does this work with?

All of them. Claude Code, Cursor, Codex, Gemini CLI, or any AI agent that can run commands. DeployHQ also has built-in agent plugins for Claude, Codex, Cursor, and Windsurf.

What can my agent deploy?

Anything with a Git repository: websites, web apps, APIs, static sites, WordPress, Laravel, Rails, Node.js, Python — any language, any framework.

What does my agent get access to?

The full DeployHQ platform — deployments with live progress, build pipelines, environment variables, SSH commands, server management, rollbacks, and the complete REST API.

Can my agent manage existing projects?

Yes. Your agent can trigger deployments, manage environment variables, configure build commands, rollback failed deploys, and access the full API for any project on your account.