Your agent shows you every change before it makes it and waits for your approval. You ask in plain English; the examples below are the kind of thing you might say.
Manage environments
Point staging at the new preview URL and make it the default.
- See each environment’s variables and their types, never their values
- Create an environment, and set, edit or remove its variables
- Rename an environment, change its description, or make it the project’s default
Your organization’s owners and admins are notified of each change a coding agent makes to an environment.
Runs and script generations find an environment by its name. Peeps refuses to rename an environment while runs or generations are still using it, and a rename into or out of production needs your explicit confirmation. Schedules, PR checks and incoming webhooks follow the new name.
Manage projects
Set up a Peeps project for this app.
- Check who you are in Peeps: your organizations, your role in each, and what your connection allows
- List the projects you can reach, or find the one that matches this repository
- Create a web project
- Rename a project or change its description
A new project starts with one empty environment. Before anything can run, set its base URL, which your agent can do once you approve the value. Mobile projects, and settings such as the timezone, are managed in the Peeps web app. No coding agent can delete a project. 
