After deploying one of the environments and getting to know Zerops, you have two paths forward. 1 Clone our GitHub repositories and use the whole recipe as a template, or if you already have an existing application on a similar stack, 2 integrate the recipe setup with your application.
AI agent environment provides a development space for AI agents to build and version the app.
It includes dev + stage pairs for the Wasp SPA (appdev, appstage) and API (apidev, apistage), plus a low-resource PostgreSQL database.
Taking ownership of the AI Agent environment
content_copy Clone the template repositories
Fork or clone the following to your local machine or GitHub account:
# Prerequisite: check authorization
After you deploy the AI Agent environment, an authorization dialog should appear.
Complete the Claude Code authorization before continuing. This is separate from your Zerops access token and uses your own Claude Code subscription or API credentials.
# 1. Open your ZCP workspace
The deployment creates your app services and a zcp@1 workspace.
The agent, terminal, and browser IDE run inside the ZCP service. Your app still runs in the app services, not in the ZCP workspace.
# 2. Start in the browser IDE
The fastest way to work with the agent is to open the browser IDE from the ZCP service.
- No local setup is required.
- The agent runs close to your Zerops project.
- It can inspect project context and use available MCP tools.
- After the agent makes a change, open the app URL and verify the result.
# 3. Connect from your local IDE or terminal
If you prefer local tooling, connect your machine to the Zerops project network.
Install zCLI and log in:
npm i -g @zerops/zcli
zcli login <personal-access-token>
Start the VPN:
zcli vpn up
Connect to the remote service:
ssh -A <service-name>.zerops
# 4. Work with the dev/stage flow
Use the development environment for fast iteration with the agent. Use staging to verify the result before moving toward production.
Typical flow:
- Ask the agent for a focused change.
- Review and test the result.
- Push the change to your repository or deploy with
zcli push. - Verify the result in staging.
- Continue with the production guide when ready.
# 5. Move toward production
When the staging version is ready, finish the production setup:
- configure the deployment pipeline
- set up your domain
- check logs and runtime behavior
- configure backups if the recipe includes a database
- review scaling settings before real traffic arrives
These services were wired into Zerops with per-service integration guides. Open the Integrate flow to follow the same steps for your own application.
lan Deploy more environments
One environment rarely tells the full story — deploy environments for other stages of development to see how they work on Zerops.
Related platform & services docs
Related Recipes
More recipes with similar technologies and categories.
TanStack Start Hello World
A server-rendered TanStack Start application with Nitro Node output, deployed on Zerops. Includes ready-made environment configurations for the full development lifecycle.

React (Vite) Static Hello World
A complete React + Vite hello world recipe for Zerops, demonstrating static site deployment with build-time environment variable injection — compiled by Node.js, served by Nginx, ready-made for every stage of the development lifecycle.

React Router Static Hello World
A complete React Router v7 hello world recipe for Zerops — deploying a React Router v7 SPA (static mode, no SSR) as a static site built by Node.js and served by Nginx, with ready-made environment configurations demonstrating build-time environment variable injection via Vite.

React Router SSR Hello World
A minimal server-side rendered application built with React Router v7 on Zerops, connecting to a PostgreSQL database. Includes ready-made environment configurations for every stage of the development lifecycle - from AI agent workspaces through local development to highly-available production.