mosaicstack/stack

Fork 0

Files

History

Jarvis 31008ef7ff

ci/woodpecker/push/ci Pipeline was successful

Details

ci/woodpecker/pr/ci Pipeline was successful

Details

fix: update Gitea org references from mosaic/ to mosaicstack/

- Update all package.json repo URLs (mosaic/mosaic-stack → mosaicstack/mosaic-stack)
- Update npm registry URLs (/api/packages/mosaic/npm → /api/packages/mosaicstack/npm)
- Update woodpecker publish destinations
- Update tools/install.sh registry and repo base URLs

2026-04-04 22:31:20 -05:00

src

feat(plugins): add Telegram channel plugin

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

package.json

fix: update Gitea org references from mosaic/ to mosaicstack/

2026-04-04 22:31:20 -05:00

README.md

fix: rename all packages from @mosaic/* to @mosaicstack/*

2026-04-04 21:43:23 -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

@mosaicstack/telegram-plugin

@mosaicstack/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