helix deploy ships your project to Tray’s cloud in one command, and prints the URL where it’s running. There’s no separate build step to run first: deploy builds what it needs. helix deployment get looks up what happened on a given deploy.
helix deploy
helix deployDeploys the project in the current directory. What happens depends on whether the project has been deployed before.
The first deploy provisions the project. Helix creates the project on the platform, generates a name for it, writes an AI-generated description of what the app does, and records the project ID. If no workspace is set yet, the command asks you to pick one.
Later deploys upload a new artifact to the project that already exists. The AI description is regenerated on each deploy, so it tracks what your app currently does.
| Flag | What it does |
|---|---|
--name <name> | Name to provision the project under, used on the first deploy only. Defaults to name in helix.config.ts |
--config <path> | Config file to use instead of ./helix.config.ts. The file names the deploy target, so this is how you deploy a target other than your development default. The HELIX_CONFIG environment variable has the same effect; the flag wins |
Because --name only applies at provisioning time, passing it to a later deploy won’t rename an existing project.
helix deploy --config helix.production.config.tsA deploy always lands in the workspace and project the selected file names, and a first deploy with --config writes the provisioned project ID into that file. See the configuration model for the one-config-file-per-target workflow.
What you get back
A successful deploy prints three things:
| Output | What it’s for |
|---|---|
| Project ID | The project’s identifier, also written into helix.config.ts |
| App URL | Where the app runs: https://{project-id}.helix-app.ai |
| Dashboard link | The project in the Helix dashboard at https://app.helix.tray.ai |
To roll back, deploy again from an earlier commit of your project. There’s no rollback command yet.
helix deployment get
helix deployment get <deploymentId>Shows the status of one deployment: whether it succeeded, any warnings raised during the build, and the build errors if it failed. Use it when a deploy doesn’t come back clean, or when you want to confirm which deployment is live.
helix deployment get 4f2b8c1e-9d3a-4e77-b5c0-6a1f8e2d4b90Like helix deploy, it accepts --config <path> to look up a deployment against a config file other than ./helix.config.ts.
Deployments are retained for 30 days, apart from the live deployment and the one before it, which are always kept. A deployment past that window is deleted and no longer returned. See how long previous deployments are kept.
The Helix dashboard shows the same deployment history per project, alongside execution logs.