curl -fsSL https://log.listeningkit.com/install.sh | sh
claude mcp add log -- logMcp
X, from your agent
"Read my X DMs and tell me who's waiting on me."
The old inbox and the encrypted X Chat, read as one.
log twitter dms --account <name> --waiting
Discord, Slack and Instagram, live
Every new message is pushed to your agent the moment it lands.
log discord read --account <name> --channel "<chat>"
log slack read --account <name> --channel "<chat>"
log instagram dms --account <name>
Answers in your own voice
Every draft is checked against how you really write to that person before it goes.
log voice --to <handle> --text "<draft>"
Facebook Marketplace and groups
Listings kept live across local accounts, and groups read for people asking for a service.
log facebook listings
log facebook join group --account <name> --group <url>
log runs your social accounts from the command line, or from your AI agent. It reads DMs, group chats, replies and notifications, and it sends messages, replies, likes, follows, reactions and voice notes for you. It's one command, log, and one MCP server, logMcp, and it runs on your own machine with your own accounts. Nothing acts until you say so: every command that changes something is a dry run until you add --live. It's free and open source.
Quick start
Install
curl -fsSL https://log.listeningkit.com/install.sh | sh # macOS and Linux
irm https://log.listeningkit.com/install.ps1 | iex # Windows (PowerShell)
curl -fsSL https://log.listeningkit.com/install.sh | sh -s -- --skills all # also every play as a skill
This installs the log and logMcp commands, and Python with everything the platform engines need. It writes your settings to ~/.logCli/.env. Already have Bun? bun add -g @listeningkit/log installs just the commands. Already have log? --skills all --skillsOnly adds only the skills; on Windows, set $env:LOG_SKILLS = "all" before the PowerShell line. More: docs/install.md.
Connect your accounts
Add the account once, sign it in, then check that the platform still accepts it:
| Platform | How to sign in |
|---|
| X | log twitter cookies save --account <handle>: paste auth_token, ct0 and twid from a cookie-export extension |
| LinkedIn | log linkedin cookies save --account <publicId>: paste li_at and JSESSIONID |
| Slack | log slack cookies save --account <name>: paste the d cookie |
| Discord, Reddit, Instagram | log localAccount add --platform <platform> --account <name>, then log inspect start --account <name>, sign in by hand in the window that opens, and log inspect do stop --account <name> to save the session |
| Facebook | log localAccount add --platform facebook --account <name>, then log facebook connect --account <name> |
Then check it with log <platform> session check --account <name>, which sends nothing. The answer is loggedIn, loggedOut or restricted. Cookies are always typed into a masked prompt and never passed as flags. More: docs/accounts.md.
Connect your agent
| Agent | How to connect |
|---|
| Claude Code | claude mcp add log -- logMcp |
| Codex, Cursor and other MCP clients | add logMcp as a stdio MCP server: docs/mcp.md |
Then ask in plain words: "read my X DMs and tell me who's waiting on me". The agent loads log's guide first, then follows the matching play.
Platforms
| Platform | What log does | How it talks to the platform |
|---|
| X | DMs and X Chat, notifications, followers, replies, posts, likes, follows, lists, reactions, voice notes, queues | its own API client, one session per account, no browser |
| Discord | DMs, groups and server channels, live; sends, reactions, voice notes, files | its own API client and the live gateway, no browser |
| Slack | DMs and group DMs in every workspace, live; sends, reactions, voice notes | its own API client and the live socket, no browser |
| Instagram | DM threads, live; sends, photos, reactions, voice notes | its own API client and the realtime connection, no browser |
| Facebook | Marketplace listings, groups, warm-up | the account's own browser, opened once a day through a proxy in its home country |
| Reddit | session check (new) | its own API client |
| LinkedIn | session check (new) | its own API client |
Highlights
- Start from a play. Each use case is a workflow written step by step: what to run, and what tells you each step worked. With
--skills all, your agent picks the right one from what you say.
- Your voice, checked. A draft is read against how you really write to that person, for AI phrasing and for hidden characters, before it can be sent.
- One session per account. Each account keeps one connection open, the way the platform's own app does, never a new one per command.
- Live inbox. New messages are pushed into your agent's context as they arrive, and two agents never answer the same chat.
- Kept human. Every account has its own daily limits, pacing and local waking hours. A refusal from the platform stops the run, and nothing is retried.
- Your machine, your data. Accounts and sessions stay in
~/.logCli. Many accounts? Keep them in Twenty, an open-source CRM, so every machine, agent and teammate sees the same ones.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
