The Qyra CLI is how you build and ship your semantic layer. It runs against your dbt project on your own machine, so you can write metrics and dimensions, see them working, and promote them to production without leaving your editor.

Start by installing the CLI and authenticating against your instance.

The development loop

Most work follows the same cycle.

Write your semantic layer. qyra generate writes a starting schema.yml for each model with an entry per column, so you edit rather than author from scratch. qyra compile builds your project locally to confirm the YAML resolves.

Check your work before it ships. qyra preview spins up a temporary project from your local changes so you can query real data without touching production. qyra validate reports content that your changes would break — a chart referencing a field you renamed, for instance — and qyra lint checks your Qyra Code files against their schemas.

Ship it. qyra deploy pushes the compiled project to production. In CI, the same commands run on every pull request — see setting up CI/CD.

Managing content as code

Charts, dashboards, agents, and data apps can round-trip through the CLI as well as the UI. qyra download pulls them into your repository as files and qyra upload sends them back, which is how you version content, review it in a pull request, or copy it between projects. See content as code.

Every command and flag

The CLI reference documents every command, flag, and environment variable.