Skip to main content

CLI / Terminal

Use the Midcore CLI in your terminal or in scripts and CI. Install once, then run agent, plan, debug, ask, and gates from any directory. No IDE required—ideal for servers, CI/CD, and automation.

Install

Choose your method:

macOS, Linux, WSL:

bash
curl -fsSL https://get.midcore.dev/install.sh | bash

Windows PowerShell:

powershell
irm https://get.midcore.dev/install.ps1 | iex

Updates

Native installs can update in the background. Check release notes for your version.

Verify install

  • Run midcore --version — you should see a version number.
  • Optionally run midcore init in a test directory and confirm .maestro/ is created.

When to use CLI

Use the CLI for CI/CD (run gates in pipelines), scripting and automation, headless servers, and power users who prefer the terminal. No IDE required.

First run

Confirm installation:

bash
midcore --version

Initialize a project (creates .maestro/ and optional intent):

bash
cd your-project\nmidcore init

Run your first task:

bash
midcore agent "list the main entry points of this project"

You may be prompted to sign in or configure an API key on first use, depending on your setup.

Use in CI

Install the CLI in your pipeline, then run gates or automated tasks:

yaml
# Example: run gates in GitHub Actions
- run: curl -fsSL https://get.midcore.dev/install.sh | bash
- run: midcore gates run

Set any required environment variables (e.g. API URL, auth) as pipeline secrets. See Environment variables.

Troubleshooting

  • Command not found — Ensure the install script added the binary to your PATH. Restart the terminal or log out and back in.
  • Permission denied — Use a user-level install or fix permissions on the install directory.
  • Connection or auth errors — Check env vars and your account or API key.

Related documentation

CLI reference · CI/CD · VS Code extension · Quickstart