polygram 0.33.2 → 0.33.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
3
3
  "name": "polygram",
4
- "version": "0.33.2",
4
+ "version": "0.33.4",
5
5
  "description": "Telegram integration for Claude Code that preserves the OpenClaw per-chat session model. Migration target for OpenClaw users. Multi-bot, multi-chat, per-topic isolation; SQLite transcripts; inline-keyboard approvals. Bundles /polygram:status|logs|pair-code|approvals admin commands plus history (transcript queries) and polygram-send (out-of-turn IPC sends with file-upload validation) skills.",
6
6
  "keywords": [
7
7
  "telegram",
@@ -1,6 +1,8 @@
1
1
  /**
2
- * The trailing line a still-growing preview bubble carries: "⏳ пишу дальше…".
2
+ * The trailing line a still-growing preview bubble carries: "🤖💬".
3
3
  *
4
+ * Symbols only, no words: the bot answers in whatever language the user
5
+ * writes, so any wording would be wrong in every chat but one.
4
6
  * Mid-stream the reader cannot tell "more is coming" from "the bot stalled",
5
7
  * and the bubble itself is the only place that can answer. Polygram appends
6
8
  * the line deterministically rather than asking the agent to write one: a
@@ -15,7 +17,7 @@
15
17
 
16
18
  'use strict';
17
19
 
18
- const COMPOSING_MARKER_TEXT = '⏳ пишу дальше…';
20
+ const COMPOSING_MARKER_TEXT = '🤖💬';
19
21
 
20
22
  // The plain path's form. A blank line so it reads as its own line, and
21
23
  // markdown emphasis because tg()'s formatter renders `em` as <i> — the same
@@ -73,7 +73,7 @@ const INLINE_MEDIA_PARAGRAPHS = [
73
73
  '',
74
74
  '**Inline media or `files:`, not both.** A file you embed inline is already delivered; listing that same path in `files:` too sends it a second time as a separate message. Use inline media when the image belongs in the reply, and `files:` when you are handing over a document.',
75
75
  '',
76
- '**Media and live streaming do not mix.** A message that streams grows by editing, and an edited bubble can never gain media — images degrade to their caption text. When your answer includes media, keep the media OUT of the streamed report: stream the prose, and deliver the media in its own separate reply (with at least a sentence of text). Do not put media in a message you are streaming.',
76
+ '**Media and live streaming do not mix.** A message that streams grows by editing, and an edited bubble can never gain media — images degrade to their caption text. When your answer includes media (inline images, a collage, a slideshow), skip streaming for that answer entirely: compose it and send ONE reply, with the media rendering inline in the rich document, pictures in place. Do not stream the prose first, and do not split the media into a separate message.',
77
77
  '',
78
78
  ];
79
79
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "polygram",
3
- "version": "0.33.2",
3
+ "version": "0.33.4",
4
4
  "description": "Telegram daemon for Claude Code that preserves the OpenClaw per-chat session model. Migration path for OpenClaw users moving to Claude Code.",
5
5
  "main": "lib/ipc/client.js",
6
6
  "bin": {
@@ -63,7 +63,7 @@
63
63
  "dependencies": {
64
64
  "@anthropic-ai/claude-agent-sdk": "0.2.123",
65
65
  "@modelcontextprotocol/sdk": "^1.29.0",
66
- "@shumkov/orchestra": "0.10.9",
66
+ "@shumkov/orchestra": "0.10.10",
67
67
  "better-sqlite3": "^12.9.0",
68
68
  "grammy": "^1.42.0",
69
69
  "markdown-it": "^14.1.1",