Reference

lessly_deploy

Build and deploy a git ref to a Lessly environment.

Tool

lessly_deploy

Build and deploy a git ref to a Lessly environment.

Behavior

Returns: { deployment_id: string, status: 'queued' | 'building', build_logs_url: string }
Typical sequence: Call lessly_deploy.
Poll lessly_get_deployment until status is 'ready' or 'error'.
Fails when: ref is not pushed to the remote.
the environment is locked by another in-flight deploy.

Arguments

Name	Type	Required	Description
app	string	•	Slug of the Lessly app to deploy (matches the name in your workspace).
ref	string	—	Git ref — branch name, tag, or commit SHA. Defaults to the app's default branch. default: main
environment	"production" \| "staging" \| "preview"	—	Target environment. Preview deploys get a unique URL; production replaces the live URL after the health check passes. default: preview
wait	boolean	—	If true, the tool returns only after the deployment reaches a terminal state (ready or failed). If false, returns as soon as the build is queued. default: false

Try it

Deploy the main branch of acme-store to production and wait for it to go live.

When to use

Build and deploy a git ref to a Lessly environment. Returns: { deployment_id, status: 'queued'|'building', build_logs_url }. Typical sequence: lessly_deploy → poll lessly_get_deployment until status is 'ready' or 'error'. Fails when: ref is not pushed to the remote, or the environment is locked by another in-flight deploy. Irreversible for environment: production — use environment: preview-<slug> to dry-run.

Example

Ask your agent something like this:

Deploy the main branch of acme-store to production and wait for it to go live.

The agent will invoke lessly_deploy with these arguments:

json

{
  "app": "acme-store",
  "ref": "main",
  "environment": "production",
  "wait": true
}