Skip to Content
CLI referencelogs

hiveloom logs and hiveloom tail

Two related commands that read the same agent log stream:

  • hiveloom logs prints the last N entries and exits.
  • hiveloom tail streams new entries until you Ctrl-C.

Both filter to a single tenant and optionally a single agent.

Synopsis

hiveloom logs [OPTIONS]
hiveloom tail [OPTIONS]

Options

FlagApplies toDefaultDescription
--tenant <TENANT>bothdefaultTenant slug.
--agent <AGENT>both—Filter by agent ID. Omit to see all agents in the tenant.
--limit <N>logs only50Maximum entries to show.
--endpoint <URL>both—API endpoint for a remote instance.
--token <TOKEN>both—Bearer token for remote access.
--jsonboth—One JSON object per line.

Examples

Last 50 entries across all agents in the default tenant:

hiveloom logs

Last 200 entries for a specific agent, JSON for jq:

hiveloom logs --agent agt_abc123 --limit 200 --json | jq 'select(.level=="error")'

Live-stream a remote instance:

hiveloom tail \
  --endpoint https://hiveloom.example.com \
  --token "$ADMIN_TOKEN" \
  --agent agt_abc123

Where these logs come from

These are the agent runtime logs — tool invocations, model calls, compaction events. For the HTTP service’s stdout/stderr (request lines, panics), use journalctl -u hiveloom instead.

Credentials never appear in this stream by design; if you ever spot one, treat it as a bug and report it.

doctortop