People
Manage sites, content, and publishing without leaving the terminal.
MOVE YOUR SITE TO PLOY
Open your existing repo in Claude Code or Codex. Give your agent a prompt to inspect it and plan the move. Import a compatible Astro repo on Ploy's Free plan.
Free initial import for compatible Astro repositories. No card required.
Your repo. Your agent. A clear plan.
Copy this into Claude Code or Codex while your existing repository is open. Your agent will check what can move before it creates anything.
Help me move this existing website repository to Ploy. Work from this source repo and keep it unchanged.
First inspect its framework, routes, assets, forms, server behavior, and deployment dependencies. Read the public ploy-site skill at https://raw.githubusercontent.com/Ploy-AI/ploy-tools/main/skills/ploy-site/SKILL.md and its migration procedure at https://raw.githubusercontent.com/Ploy-AI/ploy-tools/main/skills/ploy-site/references/migration.md. Check the installed Ploy CLI help before choosing commands; if a documented command is missing, report the release blocker instead of guessing a substitute. Tell me whether a direct import of the committed Astro repo is supported, or whether we need to port selected pages or the whole site to Ploy's Astro runtime. Identify anything that cannot move as-is, any paid features, and what you will test.
Show me the migration scope and plan before creating a site or changing files. Once I approve it, use only currently supported CLI commands, preserve the original repository, verify the destination preview, and ask separately before publishing or changing my domain.A compatible Astro repo can be imported on the Free plan. Other frameworks need a port to Ploy's Astro runtime. GitHub Code Sync for ongoing changes is a paid feature. Check the repo requirements.
ONE CLI. THREE WAYS TO WORK.
Automations
Turn repeatable Ploy workflows into commands your team can run again and again.
AI agents
Give Claude Code, Codex, and remote agents the context to work inside your Ploy site.
Standalone by design.
One installer gives you the Ploy CLI on macOS and Linux, with no Bun, Node.js, or npm required.
See installation optionsA website CLI for real marketing work.
The Ploy CLI gives growth teams and developers one command-line interface for workspaces, sites, content, structured data, publishing, repeatable automations, and AI agent workflows. Use it interactively in your terminal or run explicit commands in scripts and CI.
Manage websites and publishing
Choose a workspace and site, inspect its status, connect Code Sync, and publish when a reviewed change is ready. Interactive selectors make everyday use quick, while workspace and site IDs support reliable non-interactive commands.
Run content and automations
Work with Documents, Ploybooks, databases, tables, queries, and CSV imports from the same website CLI. Marketing teams can manage site content and structured data without piecing together a separate command-line tool for every workflow.
Give AI agents site context
Use Ploy as an AI agent CLI for Claude Code, Codex, and remote agents. Agents can inspect a site's theme, pages, and reusable components, then work with the same Ploy context as your team. API tokens support remote agents and CI without an interactive browser login.
Ploy CLI FAQ
Does the Ploy CLI require Node.js?
No. The installed Ploy CLI is a standalone binary and does not require Bun, Node.js, or npm. A few local inspection commands may use Node.js or Bun when the documentation notes it.
Can I use the Ploy CLI in CI?
Yes. Use a Ploy API token and explicit workspace or site IDs for remote agents, deployment scripts, and other non-interactive environments.
Which operating systems are supported?
The standalone installer supports macOS and Linux on arm64 and x64. The built-in help stays aligned with the exact CLI version installed on your machine.