helix logs

​

Usage

helix logs [INSTANCE] [--follow]
helix logs [CLOUD_INSTANCE] [--start <RFC3339>] [--end <RFC3339>]

​

Arguments

​

Options

​

Behavior

• Local logs are plain text from Docker/Podman and may follow. --start, --end, and --json are rejected for local instances.
• Cloud logs use the WorkOS session and the linked database’s recent query-error endpoint on the Helix Cloud API; they never contact the database gateway that applications use.
• Cloud errors print as a table with TIME, QUERY, and ERROR columns. An empty window prints a message naming the instance and time range.
• --start must be before --end. Without either, the window is the last hour.
• Cloud follow is not supported.

​

Examples

# Print the logs of the local 'dev' instance
helix logs dev

# Follow local logs
helix logs dev --follow

# Recent query errors for a Cloud instance (last hour)
helix logs production

# Query errors in an explicit window, as JSON
helix logs production --start 2026-01-01T00:00:00Z --end 2026-01-01T06:00:00Z --json

​

Related

• helix status — check whether an instance is running.
• helix start — start with --foreground to stream startup logs.
• Local workflow — run and debug a local instance.
• Helix Cloud workflow — end-to-end Cloud usage.