Quick start

Prompt for Claude Code or Codex

Sets up an environment for this repository

Copy promptView prompt

Set up an Ellipsis environment for this repository. An environment is a YAML file that defines the cloud environment Ellipsis agents run in: the repositories checked out, the scripts that install dependencies and build, the environment variables, and the machine size. The `el` CLI is installed and logged in. 1. Learn how this repository installs dependencies, builds, and runs its tests. Read the README, AGENTS.md, CLAUDE.md, package manifests, lockfiles, Dockerfiles, Makefiles, and CI workflows. 2. Run `el environment init .ellipsis/environments/<repo>.yaml`, where <repo> is this repository's GitHub name, then edit the file. Read https://www.ellipsis.dev/docs/environments and https://www.ellipsis.dev/docs/environments/schema first. Follow these rules: - Set `ellipsis.name` to <repo> and list <repo> under `repositories`. - The repository is checked out at /sandbox/<repo>. Scripts run in /sandbox as the sandbox user, and each must exit 0. - Install dependencies in `hooks.build_base`. List every file the install reads in `build_base.inputs`, each path starting with <repo>/ (for example <repo>/package-lock.json). Only listed files exist while build_base runs. Globs fail. - Build in `hooks.after_checkout`, written so it is safe to run again on a workspace that already has its output. Start services in the background and wait until they are ready. - Remove the starter's example variables and MCP servers unless this repository needs them. List required secrets under `variables` by name only. Never write a secret value into the file. 3. For each secret the tests need, ask me for the value or tell me to run `el variable set NAME=value` myself. Do not continue until they are set. 4. Create the environment: `el environment create -f .ellipsis/environments/<repo>.yaml` 5. Test it: `el session start -e <repo> --model claude-opus-5-5 --budget 2 --watch "Run this repository's tests and report the result. Do not change any files."` 6. If the session fails or the tests do not run, read the output (`el session export <session-id>` prints the full log), fix the file, apply it with `el environment edit <repo> -f .ellipsis/environments/<repo>.yaml`, and test again. Repeat until the tests run. If a session fails because the account has no credits, stop and tell me to add credits under Billing > Credits in the Ellipsis dashboard. 7. Once the tests run, delete the test copy with `el environment delete <repo>` and open a pull request that adds .ellipsis/environments/<repo>.yaml to the default branch. Ellipsis syncs the environment from the default branch when the pull request merges. 8. Reply with the pull request link, the test result, and any secrets I still need to set.