Skip to main content
For the complete documentation index optimized for AI agents, see llms.txt.
View logs for a local or Helix Cloud instance.
  • For local instances, logs come from docker logs / podman logs.
  • For Helix Cloud instances, logs are fetched over a time range from Helix Cloud and require helix auth login.

​
Usage

helix logs [INSTANCE] [OPTIONS]

​
Arguments

ArgumentDescription
INSTANCEInstance name. If omitted in a TTY with multiple instances, the CLI prompts. Defaults to dev when present and no prompt is needed.

​
Available flags

FlagTypeDescriptionDefault
-f, --followBooleanStream live logs. Local only — rejected for Helix Cloud instances.false
-r, --rangeBooleanQuery historical logs from Helix Cloud over a time range. Helix Cloud only.false
--startRFC 3339 timestampStart of the range. Requires --range.--end minus 1 hour
--endRFC 3339 timestampEnd of the range. Requires --range.Now (UTC)
--range, --start, and --end are rejected for local instances with: 
--range, --start, and --end are only supported for Enterprise logs;
local logs use docker/podman logs
--follow against a Helix Cloud instance is rejected with: 
live Enterprise logs are not supported yet; use --range instead

​
Examples

# Dump local container logs once
helix logs dev

# Stream local logs
helix logs dev --follow

# Last hour of Helix Cloud logs (defaults: end=now, start=end-1h)
helix logs production --range

# Fixed Helix Cloud log range
helix logs production \
  --range \
  --start 2026-05-12T10:00:00Z \
  --end   2026-05-12T11:00:00Z