Skip to content

feat(tingly): add real platform service with WS protocol - #871

Open
0x0079 wants to merge 1 commit into
tingly-dev:mainfrom
0x0079:claude/implement-tingly-platform-mGtGf
Open

feat(tingly): add real platform service with WS protocol#871
0x0079 wants to merge 1 commit into
tingly-dev:mainfrom
0x0079:claude/implement-tingly-platform-mGtGf

Conversation

@0x0079

@0x0079 0x0079 commented May 7, 2026

Copy link
Copy Markdown
Collaborator

The existing imbot/platform/tingly was an in-process test harness. This adds a genuine tingly platform service that bots and chat clients connect to over WebSocket, sitting alongside telegram/wechat/etc. as a peer IM backend — but intentionally minimal because tingly typically deploys next to the bot.

  • imbot/platform/tingly/wire: shared JSON-over-WS protocol (Frame envelope, Hello/Welcome handshake, bot.send/edit/delete/react and chat.send/callback payloads)
  • imbot/platform/tingly/ws_transport.go: WSTransport implementing the existing Transport seam, with reconnect + ack tracking; the InProcessTransport keeps working unchanged for tests
  • tingly/server: WebSocket router with per-(bot,chat) jsonstore-backed message log and history replay on chat connect
  • tingly/chatclient: small SDK for chat-side participants
  • E2E test covering chat→bot, bot→chat, edit propagation, and history replay across bot restart

The existing imbot/platform/tingly was an in-process test harness. This
adds a genuine tingly platform service that bots and chat clients connect
to over WebSocket, sitting alongside telegram/wechat/etc. as a peer IM
backend — but intentionally minimal because tingly typically deploys
next to the bot.

- imbot/platform/tingly/wire: shared JSON-over-WS protocol (Frame
  envelope, Hello/Welcome handshake, bot.send/edit/delete/react and
  chat.send/callback payloads)
- imbot/platform/tingly/ws_transport.go: WSTransport implementing the
  existing Transport seam, with reconnect + ack tracking; the
  InProcessTransport keeps working unchanged for tests
- tingly/server: WebSocket router with per-(bot,chat) jsonstore-backed
  message log and history replay on chat connect
- tingly/chatclient: small SDK for chat-side participants
- E2E test covering chat→bot, bot→chat, edit propagation, and history
  replay across bot restart
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants