hermes logs Command — Complete Reference & Examples

Overview

hermes logs views, tails, and filters Hermes Agent log files — agent.log, errors.log, gateway.log, gui.log, and desktop.log. You can choose which log to read, limit the number of lines, follow in real time, and filter by level, session ID, time, or component.

Usage

hermes logs [-h] [-n LINES] [-f] [--level LEVEL] [--session ID] [--since TIME] [--component NAME] [log_name]

Log Names

log_name is optional and selects which log to view:

Name	Log file
`agent` (default)	`agent.log` — agent activity
`errors`	`errors.log` — error entries
`gateway`	`gateway.log` — gateway/platform activity
`gui`	`gui.log` — GUI activity
`desktop`	`desktop.log` — Electron app boot/backend
`list`	Lists available log files with sizes

Options

Option	Description
`-n LINES, --lines LINES`	Number of lines to show (default: 50)
`-f, --follow`	Follow the log in real time (like `tail -f`)
`--level LEVEL`	Minimum log level to show (DEBUG, INFO, WARNING, ERROR)
`--session ID`	Filter lines containing this session ID substring
`--since TIME`	Show lines since TIME ago (e.g. 1h, 30m, 2d)
`--component NAME`	Filter by component: gateway, agent, tools, cli, cron, gui

Examples

# Show the last 50 lines of agent.log
hermes logs

# Follow agent.log in real time
hermes logs -f

# Show the last 50 lines of errors.log
hermes logs errors

# Show the last 100 lines of gateway.log
hermes logs gateway -n 100

# Follow gui.log in real time
hermes logs gui -f

# Follow desktop.log (Electron app boot/backend)
hermes logs desktop -f

# Only show WARNING and above
hermes logs --level WARNING

# Filter by session ID
hermes logs --session abc123

# Only show tool-related lines
hermes logs --component tools

# Lines from the last hour
hermes logs --since 1h

# Follow, starting from 30 min ago
hermes logs --since 30m -f

# List available log files with sizes
hermes logs list

Tips

Combine filters: e.g. hermes logs gateway --level ERROR --since 2h to see recent gateway errors.
Use hermes logs list to see which log files exist and how large they are.
--follow is ideal for live debugging — run it in a separate terminal window while you reproduce the issue.
--session is handy for tracing a single conversation across logs.
Log files live under ~/.hermes/logs/, so you can also inspect them directly.