Skip to content
v0.2.0MIT

Runs your X, Discord, Slack, Instagram and Reddit conversations from Hermes through log by ListeningKit: read inboxes, find what needs a reply, draft it in your own voice and send only after you approve.

log for Hermes

log by ListeningKit, in collaboration with Hermes Agent

Your agent, working your DMs the way you would.

Every conversation you've ever had holds an opportunity: someone waiting on a reply, a follow-up you forgot, a lead that went quiet. This plugin gives Hermes log by ListeningKit, an open-source tool that reads and sends from your own X, Discord, Slack, Instagram and Reddit accounts, in your own voice. LinkedIn sign-in status is available; LinkedIn conversation reads and sends are not built yet.

Ask Hermes things like:

  • "Who messaged me on X and Discord today, and who's waiting on a reply?"
  • "Read my thread with @someone and draft an answer the way I'd write it."
  • "Follow up with everyone who opened my DM but didn't reply."

Hermes reads freely. Every send, reply or post asks you first.

Hermes asks who is waiting for a reply, and log finds the X conversations waiting on you

Every platform you're onIndexes every conversation
log's platform cards: Slack, Instagram and more, each in your own sessionHermes reading Discord mentions and conversations through log

A draft in your own voice, checked before anything is sent

The log tab

Enable the plugin and Hermes's dashboard gets a log tab: who is waiting on a reply, every account you signed in with its session and today's sends against its daily limit. Ask Hermes copies a ready prompt for that conversation into your clipboard, so you paste it into chat and Hermes drafts the reply there. The tab only reads; it never sends.

The log tab in the Hermes dashboard, shown with sample data

Watch the launch video: log on X.

What's inside

An Agent Plugins v1 package:

  • mcp.json: starts log's MCP server (logMcp) on your machine over stdio. Hermes gets log's tools as mcp__log__*: DM inboxes, conversation reads, session checks, search across past conversations, the voice check, and the send/reply/quote tools.
  • plugin.json: marks the log server untrusted, so every tool not annotated read-only (anything that sends or changes an account) asks for approval and is refused in cron and other unattended runs. The tool-call timeout is 600 s, because a platform read can take a while.
  • skills/: every log play, one skill each (log:log-twitter-dm-inbox, log:log-inbox-triage and so on), generated from log's use cases by bun run skills:build, the same skills Claude Code gets. Each one starts by loading its play with getGuide({ useCase }), so log's play gate lets its sends through.
  • native/: a second, native Hermes plugin, logHooks (plugin.yaml, __init__.py). A portable plugin like this one can't register hooks, so the router lives there: its pre_llm_call hook runs log's hook script before each model call and adds what it answers to the turn: the play the prompt asks for, anyone waiting in a signed-in inbox, open browsers on a state log can resolve, and, on a session's first turn, what a session start gets. The pack installs it beside log, and it finds your log install by itself; log launch --setup can install it too.
  • dashboard/: the log tab for Hermes's dashboard (manifest.json, plugin_api.py, dist/). Plain JavaScript on the dashboard SDK, no build step and no bundled libraries.

Install

  1. Install log and sign in your accounts (it keeps them on your machine). With Bun:

    bun add -g @listeningkit/log
    log launch --setup
    

    log's install guide also has a one-line installer that sets up Bun and the Python its platform engines use. Check logMcp is on your PATH.

  2. Install everything with one command, the tools, skills and dashboard tab (log) and the router hook (logHooks):

    hermes plugins pack install https://log.listeningkit.com/hermes-pack.yaml
    

    It's a Hermes plugin pack: Hermes shows both plugins, pinned to one exact commit of this repo, asks once, then installs and enables them. Restart Hermes to load them. The hook finds your log install by itself (Bun's or npm's global install), so there's no setup step.

    Only the tools and skills: hermes plugins install listeningkit-log --enable from the Hermes catalog. This folder is the plugin's only home; deepmroot/listeningkit-log, where it started, is no longer updated.

  3. Already ran log launch --setup and picked Hermes? That installed logHooks too; the pack's copy replaces it.

Disclosure

  • Dashboard tab: its backend (dashboard/plugin_api.py) runs inside Hermes's dashboard only while the plugin is enabled. It reads, read-only, log's own files under ~/.logCli: each account's session.json, its governor_state.json (today's request and send counts) and the X inbox log already synced (inboxSync.json), including message previews. It makes no network call, runs no command and writes nothing. The tab is served on Hermes's own local dashboard, behind its sign-in.
  • Router hook: the native logHooks plugin, once enabled, runs bun <your log install>/scripts/hooks/event.ts before each model call with the message you sent, and adds its answer (at most 7,500 characters per event) to the turn. That script reads log's local state and starts log's own background services (the context service and, for signed-in accounts, the inbox watchers) the way log's other hooks do.
  • Local process: the plugin runs logMcp from your log install as a long-running stdio process while Hermes is open. It is not bundled here; you install log yourself.
  • Network calls: log calls the platforms you signed in (X, Discord, Slack, Instagram, Reddit and LinkedIn) directly, as your own accounts, and only when a tool runs. This plugin adds no telemetry and sends nothing anywhere else.
  • Data and credentials: your account sessions, cookies and message history stay in log's own folder on your machine (~/.logCli). The plugin never reads cookies or credentials; only log does. The dashboard tab reads only the files named above. Nothing is put in mcp.json.
  • Writes: sends, replies, quotes, likes, follows and LinkedIn posts and deletes go out as you, so they are gated by Hermes approval (trust: untrusted) and by log's own per-account daily limits. log stops on any rate limit, block or failed send instead of retrying.
  • Referral links: some plays link to services log works with, and those links carry ListeningKit's referral or affiliate code: treg (treg.to/?ref=), Memelord (memelord.com/sign-up?ref=), Inworld (inworld.ai/signup?ref=) and Fish Audio (fish.audio/?aff=). Using them costs nothing extra; drop the code from the address if you'd rather not. Every skill with such a link says so at its end.
  • The tool set comes from your installed log version at runtime and is not covered by this plugin's pinned commit.

License

MIT