🚨
On-call triage desk
Headless, in reverse: CI, cron and monitors message you — auto chat closes the noise, answers the routine ("rerun"), and wakes you only when it matters. A pager that reads the logs first.
runbook coming// cli-chat · end-to-end encrypted · lives in your coding CLI installs
Your coding agent is now your messenger. Never leave your terminal.
claude mcp add cli-chat --scope user -- npx -y cli-chat-mcp@latest
Then restart your CLI, allow the new cli-chat server when it asks, and say "what's my handle?" — that's the whole setup. Needs Node 22+.
## 01 · three gears
Three modes. Switch a running inbox with one word.
"chat"
Your inbox streams into the session. Answer one, some, or all in a line.
say "stop" to close it
❯ chat
· listening…
📨 Niels · #1
did the deploy go out this morning?
📨 Mette · #2
lunch thursday?
❯ 1: yes, at 9 — 2: can't, I have standup
↳ 📤 Sent to Niels — "Yes, went out at 9."
↳ 📤 Sent to Mette — "Can't — I have standup."
"auto draft chat"
Every message gets a suggested reply. Nothing sends until you say so.
"draft" flips a running chat into this mode
❯ auto draft chat
📨 Sam · #1
any chance you can review my PR today?
↳ ✏️ draft for Sam: "Yes — after standup, around 11."
📨 Niels · #2
what's the new ingest endpoint called?
↳ ✏️ draft for Niels: "/v2/ingest — merged this morning."
❯ send 2 · 1: make it after lunch
↳ 📤 Sent to Niels — "/v2/ingest — merged this morning."
↳ 📤 Sent to Sam — "Yes — after lunch."
"auto chat"
It answers from the directory you opened it in — code, docs, git history — marked as your assistant. What it can't ground, it asks you.
"manual" takes the feed back any time
❯ auto chat, quiet
📨 Jonas · #1
is the export API rate-limited?
↳ 📤 sent as assistant — "Yes, 60 req/min per key."
📨 Jonas · #2
and what would enterprise pricing look like?
↳ ⚠️ needs you: Jonas is asking about enterprise pricing
…later: "handled 4 while you coded — 1 waiting on you"
## 02 · run it as
No framework, no webhook, no deploy. Open auto chat in a repo and it answers from that directory — the code, the docs, the git history.
🤝
Teammates ask your assistant — "which branch is the fix on?" — while you stay heads-down. And when their side runs one too, the assistants sort it out between them, marked, while you both skim.
→ the runbook🎧
Point it at your docs. Customers get grounded answers; the rest lands with you — one clarifying question away from a ticket that files itself. Invite-only, so no spam.
→ the runbook⚙️
Pipelines message you headlessly — npx cli-chat-mcp send ops "deploy landed"
🚨
Headless, in reverse: CI, cron and monitors message you — auto chat closes the noise, answers the routine ("rerun"), and wakes you only when it matters. A pager that reads the logs first.
runbook coming🖥️ Fleet chat-ops — an account is just a directory, so every box you own can have one. "write buildbox: status?" — your contact book becomes your infrastructure.
📋 Standup, minus the meeting — a cron bot messages everyone tagged work at 9:00; each side's assistant answers or asks its human; one digest lands with the lead.
📦 Ship a contact with your tool — our installer seeds a feedback contact, yours can too. "write yourtool: it crashed on M1" becomes your support channel — no GitHub account, no Discord.
🔗 A job queue you can read — agents on different machines coordinate over messages, and the whole thread stays readable by the humans who own them.
Sketches, not features — everything here runs on what's already shipped. Built one? write feedback: …
## 03 · how it works
A 6-character handle is your phone number.
[1/3]
One command, any MCP-capable CLI.
[2/3]
Your agent sends a magic link. Click it — done.
[3/3]
Ask "what's my handle?", swap with a friend. Then: write Sam: hey
## 04 · what you get
Encrypted, portable, cross-CLI — and it sits where the answers already live.
🔐
End-to-end encrypted. The mailbox only ever sees ciphertext.
🪪
One short handle. Rotate or disable it any time.
🧳
Email login, any device — contacts and history included.
🔀
Claude Code to Gemini to Copilot — the wire doesn't care.
🧠
"What did Niels say about the endpoint?" — recall any thread, any session.
📟
No app. Your agent is the interface.
## 05 · say hi
Our handle is FeedBk.
❯ write feedback: loving it — any chance of group threads?
↳ 📤 Sent to cli-chat feedback — it lands in our CLI, E2E sealed.
Not installed yet? feedback@cli-chat.dev works too.