paperclip-plugin-telegram 0.1.0 → 0.2.0

package/README.md

@@ -1,5 +1,7 @@
 # paperclip-plugin-telegram
 
+[![npm](https://img.shields.io/npm/v/paperclip-plugin-telegram)](https://www.npmjs.com/package/paperclip-plugin-telegram)
+
 Bidirectional Telegram integration for [Paperclip](https://github.com/paperclipai/paperclip). Push agent notifications to Telegram, receive bot commands, approve requests with inline buttons, and route forum topics to projects.
 
 Built on the Paperclip plugin SDK and the domain event bridge ([PR #909](https://github.com/paperclipai/paperclip/pull/909)).
@@ -14,6 +16,7 @@ Built on the Paperclip plugin SDK and the domain event bridge ([PR #909](https:/
 - **Forum topic routing**: map Telegram topics to Paperclip projects
 - **Daily digest**: scheduled summary of agent activity
 - **MarkdownV2 formatting** with automatic plain text fallback
+- **HITL escalation**: agents that get stuck can escalate to a dedicated channel with full conversation context, suggested replies, and approve/reject/override buttons. Configurable timeouts with automatic default actions.
 
 ## Setup
 
@@ -36,8 +39,15 @@ Find the `chat.id` field in the response. For groups, the ID is a negative numbe
 ### 3. Install the plugin
 
 ```bash
-# From your Paperclip directory
-pnpm paperclipai plugin install /path/to/paperclip-plugin-telegram
+npm install paperclip-plugin-telegram
+```
+
+Or register with your Paperclip instance directly:
+
+```bash
+curl -X POST http://127.0.0.1:3100/api/plugins/install \
+  -H "Content-Type: application/json" \
+  -d '{"packageName":"paperclip-plugin-telegram"}'
 ```
 
 ### 4. Configure
@@ -54,6 +64,10 @@ In your Paperclip instance settings, configure:
 | `enableInbound` | No | Route Telegram replies to issues (default: true) |
 | `dailyDigestEnabled` | No | Send daily activity summary |
 | `topicRouting` | No | Map forum topics to projects |
+| `escalationChatId` | No | Dedicated chat/topic for agent escalations |
+| `escalationTimeoutMs` | No | Timeout before default action fires (default: 900000 / 15 min) |
+| `escalationDefaultAction` | No | Action on timeout: `defer`, `close`, `retry`, `escalate_further` (default: `defer`) |
+| `escalationHoldMessage` | No | Message sent to customer while waiting (default: "Let me check on that - I'll get back to you shortly.") |
 
 ### 5. Add bot to group (optional)
 
@@ -111,6 +125,8 @@ MIT
 
 ## Credits
 
-This contribution was developed with AI assistance (Claude Code).
+[@MatB57](https://github.com/MatB57) - Escalation channel concept, "Chat OS" vision for turning chat plugins into bidirectional agent command centers, and the HITL suggested-reply flow.
+
+[@leeknowsai](https://github.com/leeknowsai) - Worker bootstrap patterns adapted from the Discord plugin.
 
 Inspired by [OpenClaw's Telegram integration](https://github.com/openclaw/openclaw) (grammY, bidirectional messaging, inline buttons) and adapted for the Paperclip plugin SDK.

package/package.json

@@ -1,15 +1,8 @@
 {
   "name": "paperclip-plugin-telegram",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "type": "module",
   "main": "./dist/index.js",
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/mvanhorn/paperclip-plugin-telegram.git"
-  },
-  "keywords": ["paperclip", "plugin", "telegram", "bot", "notifications", "acp"],
-  "files": ["dist", "README.md"],
   "paperclipPlugin": {
     "manifest": "./dist/manifest.js",
     "worker": "./dist/worker.js"
@@ -21,8 +14,8 @@
     "test": "vitest run"
   },
   "peerDependencies": {
-    "@paperclipai/plugin-sdk": "^1.0.0",
-    "@paperclipai/shared": "^0.3.0"
+    "@paperclipai/plugin-sdk": ">=2026.0.0",
+    "@paperclipai/shared": ">=2026.0.0"
   },
   "devDependencies": {
     "@paperclipai/plugin-sdk": "^2026.318.0",