Corgi is how you run your project
locally — every day, with one command. You describe your stack once in a
corgi-compose.yml and corgi run brings the whole thing up: repos cloned,
databases seeded, .env files wired, every service started (it even starts
Docker for you). Run the whole thing locally, just the databases (corgi db -u),
or only the frontend against staging (corgi run --tier staging --services web).
This extension makes that nicer right inside the editor. It:
- highlights syntax and autocompletes
corgi-compose.yml files
- adds commands in the activity bar, status bar, and editor to run corgi and its
helpers (run, doctor, status, db, tunnel, …)
- lets you browse and run the showcase examples
- ships an AI assistant (see below)
🤖 AI assistant
@corgi in Copilot Chat — knows the corgi-compose.yml schema and the CLI:
@corgi /new a go api with a postgres db — scaffold a corgi-compose.yml@corgi /explain — explain the current compose file (what starts, env wiring)@corgi /debug — runs corgi doctor + corgi status and diagnoses issues@corgi how do I add a redis cache? — grounded Q&A
Each reply offers one-click corgi doctor / corgi run buttons.
Copilot agent-mode tools — in agent mode Copilot can call corgi directly:
corgi-status, corgi-doctor, corgi-validate, corgi-list (read-only) and
corgi-run (asks before starting your stack). So "get my stack running and fix
issues" just works. Reference them explicitly with #corgiStatus, #corgiDoctor,
etc.
The CLI must be installed (the assistant shells out to it).
Requirements (only needed for running corgi directly in vscode)
You can install corgi in any of these ways:
brew install andriiklymiuk/homebrew-tools/corgi
Try it with expo + hono server example
corgi run -t https://github.com/Andriiklymiuk/corgi_examples/blob/main/honoExpoTodo/hono-bun-expo.corgi-compose.yml
In order to update corgi run
corgi update
Attribution
Credits:
