mosaicstack/stack

Fork 0

Files

History

Jason Woltje 19127fa67b

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

chore: bump all packages to 0.0.1-alpha.2

- Bumps all @mosaic/* packages from alpha.1 to alpha.2
- Excludes test/spec files from CLI build output (tsconfig fix)
- Triggers CI publish to Gitea npm registry with latest changes:
  - @mosaic/types: new AbortPayload type
  - @mosaic/mosaic: update-checker module
  - @mosaic/cli: web search, file edit, MCP mgmt, file refs, /stop

2026-04-02 13:20:38 -05:00

src

feat(plugins): add Telegram channel plugin

2026-03-13 12:05:42 -05:00

package.json

chore: bump all packages to 0.0.1-alpha.2

2026-04-02 13:20:38 -05:00

README.md

feat(plugins): add Telegram channel plugin

2026-03-13 12:05:42 -05:00

tsconfig.json

feat(P0-001): scaffold monorepo structure (#60 )

2026-03-13 01:11:46 +00:00

vitest.config.ts

feat(P0-001): scaffold monorepo structure (#60 )

2026-03-13 01:11:46 +00:00

README.md

@mosaic/telegram-plugin

@mosaic/telegram-plugin connects a Telegram bot to the Mosaic gateway chat namespace so Telegram chats can participate in the same conversation flow as the web, TUI, and Discord channels.

Required Environment Variables

TELEGRAM_BOT_TOKEN: Bot token issued by BotFather
TELEGRAM_GATEWAY_URL: Base URL for the Mosaic gateway, for example http://localhost:3000

What It Does

Launches a Telegram bot with telegraf
Connects to ${TELEGRAM_GATEWAY_URL}/chat with socket.io-client
Maps Telegram chat.id values to Mosaic conversationId values
Forwards inbound Telegram text messages to the gateway as user messages
Buffers agent:start / agent:text / agent:end socket events and sends the completed response back to the Telegram chat

Getting a Bot Token

Open Telegram and start a chat with @BotFather
Run /newbot
Follow the prompts to name the bot and choose a username
Copy the generated token and assign it to TELEGRAM_BOT_TOKEN