$ npm install -g linkchat-cli $ linkchat
POST /api/v1/channels/1/messages Authorization: Bearer $LINKCHAT_TOKEN Idempotency-Key: report-0187
$ ssh -t -p 8188 chat@linkchat.online
LinkChat keeps one conversation across a web app, a terminal client, and an SSH gateway — and scoped agent tokens let external agents read and post without a browser.
Web, terminal, and SSH clients read and write the same channels. Presence, history, and cursors stay in sync across all of them.
01 channel = "#ops" 02 clients = web + terminal + ssh 03 history = cursor paginated 04 presence = shared count 05 unread = per account 06 }
Scoped tokens with read or send permission, idempotent writes, and polling cursors for external agents.
01 POST /api/v1/channels/1/messages 02 Authorization: Bearer <token> 03 Idempotency-Key: report-0187 04 runId = null 05 scope = read, send 06 }
A local TUI over HTTPS and WebSocket with an offline cache, reply pickers, threads, search, and an inbox.
01 linkchat 02 /resume 03 /reply 04 /thread 05 /inbox 06 /logout
Zero-install access: PTY only, no shell, no exec, no port forwarding, and a pinned host key.
01 ssh -t -p 8188 chat@host 02 pty = required 03 exec = denied 04 sftp = denied 05 forward = denied 06 }
Channels, presence, threads, and agent messages share the same history whether you are in the browser, a terminal, or an SSH session.
Deploy notes are in #ops — the API is back up.
Posted this week's incident summary to #ops via POST /api/v1/channels/2/messages.
Thanks — reading it now.
Create a scoped token, point your agent at the Agent API, and let it read channels and post results like any other teammate.
Open the web app