Skill

omni-events

Queries and analyzes Omni events via CLI: list/search/timeline, metrics/analytics, replay sessions/messages, journey tracing for event debugging and backfilling.

Bash

cli-tools

monitoring

npx claudepluginhub automagik-dev/omni --plugin omni

Tool Access

This skill is limited to using the following tools:

Bash(omni *)Bash(jq *)

Preview

Use `omni events` for event streams and `omni journey` for per-message tracing.

SKILL.md

Similar Skills

omni

Routes messaging tasks across WhatsApp, Telegram, Discord, Slack via Omni CLI: send/receive messages, instance/config management, events/analytics, automations.

2 tools

omni

log-inspection

Inspects and queries Claude Code hook event logs from .claude/logs JSONL files. Subcommands list sessions, timelines, tool traces, agent lifecycles, team activity, stats, coverage, and daily summaries.

4 tools

claude-code-observability

tma1

Queries local TMA1 observability data for costs, token usage, agent activity, traces, events, errors, model comparisons, and tool usage via Bash curl and SQL on GreptimeDB.

1 tool

tma1

Stats

Parent Repo Stars14

Parent Repo Forks1

Last CommitMar 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Omni Events

Use omni events for event streams and omni journey for per-message tracing.

Query events

omni events list --since 24h --limit 100 --json
omni events list --instance <id> --type message.received --json
omni events list --chat-id <chatId> --since 24h --json
omni events list --since 24h --until "2026-02-25" --json
omni events search "error" --since 7d --limit 100 --json
omni events timeline <personId> --limit 100 --json

Metrics and analytics

omni events metrics --json
omni events analytics --since 7d --json
omni events analytics --instance <id> --all-time --json

Replay sessions (event replay)

Re-process historical events through the event pipeline. Useful for rerunning automations or backfilling analytics.

# Start
omni events replay --start --since 7d --json
omni events replay --start --since 24h --types message.received,message.sent --speed 2 --json
omni events replay --start --since 7d --dry-run --json
omni events replay --start --since 7d --until "2026-02-20" --json
omni events replay --start --since 24h --instance <id> --json

# Check / cancel
omni events replay --status <sessionId> --json
omni events replay --cancel <sessionId> --json

Message replay (standalone command)

omni replay is a separate, standalone command (not under omni events). It replays missed inbound messages for a specific agent instance — useful when an agent was offline and needs to catch up.

# Replay missed messages since instance's lastSeenAt (default, max 24h)
omni replay <instanceId>

# Replay messages received after a specific timestamp
omni replay wa-main --since 2026-02-27T10:00:00Z

Flags: --since <timestamp> (ISO 8601; default: instance's lastSeenAt, max 24h ago)

Key difference: omni events replay re-processes events through the event bus (analytics, automations). omni replay re-delivers missed inbound messages to an agent instance.

Journey tracing

omni journey show <correlationId> --json
omni journey summary --since 24h --json

Notes

events list supports --chat-id <id> and --until <time> for precise time-range filtering.
events replay --start supports --until <time> and --instance <id>.
events search supports --since and --limit (no --type flag there).
Event replay management is all through omni events replay flags.
For replaying missed agent messages, use omni replay <instanceId> (standalone command).