Multi-Device Hermes Usage Patterns

Hermes can be useful from a terminal, phone, messaging platform, or private dashboard. The key is to keep routing, identity, and approval rules clear.

Common surfaces

• CLI: best for development, file work, debugging, and long focused sessions
• Telegram or Discord: good for mobile prompts, alerts, approvals, and quick status checks
• Slack: useful for team-facing updates and internal collaboration
• Email: useful for asynchronous summaries or intake, when configured carefully
• Private dashboard: best for review queues and structured approvals

Routing principle

Each surface should have a purpose. Avoid sending every alert to every channel. Use a home channel or explicit delivery target for important reports.

Approval principle

A mobile approval should include enough context to make the decision: action, risk, evidence, and expected result. A one-word “approve?” prompt is not enough for important work.

Session continuity

Use sessions, profiles, and clear titles to avoid mixing unrelated work. For sensitive projects, use a dedicated profile and channel.

Verification

After configuring a platform, send a test message, check gateway status, and confirm logs if delivery fails.