megobari 0.1.0

Telegram bot bridging to Claude Code — use as CLI or embed as a library

Megobari (მეგობარი)

Megobari means "friend" in Georgian. The name was chosen by the author while living in Georgia and learning the language — a nod to the idea of having a helpful coding companion always at hand, right from your phone.

A personal Telegram bot that bridges to Claude Code, giving you a mobile interface to Claude's coding capabilities.

Features

• Session management — multiple named conversations with independent context
• Streaming responses — real-time message updates as Claude thinks
• Per-session working directory — /cd to switch, /dirs to add extra folders
• Permission modes — default, acceptEdits, bypassPermissions per session
• Rich Telegram formatting — HTML-formatted tool summaries, session info, help
• Client-agnostic formatting — Formatter abstraction for future non-Telegram frontends
• Library API — embed Megobari in your own Python project
• Plugin marketplace — curated collection of Claude Code skills and MCP integrations

Installation

pip install megobari

Or from source:

git clone https://github.com/emakarov/megobari
cd megobari
uv sync

Prerequisites

• Python 3.10+
• Claude Code CLI installed and authenticated (claude auth login)
• A Telegram bot token from @BotFather

Quick start

Option 1: Environment variables

export BOT_TOKEN="your-bot-token"
export ALLOWED_USER="your-telegram-id"   # or @username
megobari

Or use a .env file:

cp .env.example .env   # edit with your values
megobari

Option 2: CLI arguments

megobari --bot-token="your-bot-token" --allowed-user="12345"
megobari --bot-token="your-bot-token" --allowed-user="@username" --cwd /path/to/project

Option 3: Library API

from megobari import MegobariBot

bot = MegobariBot(
    bot_token="your-bot-token",
    allowed_user="12345",           # user ID or @username
    working_dir="/path/to/project", # optional
)
bot.run()

Configuration priority

Arguments override environment variables, which override .env file values.

To find your Telegram user ID, start the bot without ALLOWED_USER set — it will reply with your ID.

Usage

# Run once
./run.sh once

# Auto-restart on .py file changes (dev mode)
./run.sh watch

# Auto-restart on git commit (set up hook first)
./run.sh install-hook
./run.sh hook

# Stop the running bot
./run.sh stop

Run modes

Mode	Command	Restarts on	Best for
watch	./run.sh watch	Any .py file change	Active development
hook	./run.sh hook	git commit	Stable dev / staging
once	./run.sh once	—	Production / manual runs

Watch mode uses watchfiles to monitor src/ for Python file changes and restarts the bot instantly on save.

Hook mode runs the bot in a restart loop. A git post-commit hook (installed via ./run.sh install-hook) sends SIGTERM to the running bot after each commit, and the loop automatically restarts it with the new code.

Both modes write a PID file to .megobari/bot.pid for lifecycle management. Use ./run.sh stop to stop the bot from either mode.

Commands

Command	Description
/new <name>	Create a new session
/sessions	List all sessions
/switch <name>	Switch to a session
/rename <old> <new>	Rename a session
/delete <name>	Delete a session
/current	Show active session info
/cd <path>	Change working directory
/dirs [add|rm] <path>	Manage extra directories
/stream on|off	Toggle streaming responses
/permissions <mode>	Set permission mode
/help	Show all commands

Permission modes

The /permissions command controls how Claude handles tool approvals:

Mode	Behavior
default	Requires interactive approval for file writes and commands. Not usable via Telegram — prompts have nowhere to go and the agent will hang.
acceptEdits	Auto-approves file reads, writes, and edits. Still prompts for bash commands. Recommended for normal use.
bypassPermissions	Approves everything automatically. Use when you need the agent to run commands freely.

Set it per session:

/permissions acceptEdits

Sessions

Each session maintains its own:

• Claude conversation context (resumable)
• Working directory (cwd)
• Extra accessible directories
• Streaming toggle
• Permission mode

Session data is persisted to .megobari/sessions/sessions.json.

Plugin Marketplace

Megobari doubles as a Claude Code plugin marketplace with a curated collection of skills and MCP integrations.

Install the marketplace

/plugin marketplace add https://github.com/<user>/megobari

Available plugins

No plugins yet — the collection is being curated.

Install a plugin

/plugin install <plugin-name>

Structure

.claude-plugin/
  marketplace.json         # Marketplace index
plugins/                   # Curated skills and MCP configs

See REQ-002 for the full design.

Development

# Install with dev dependencies
uv sync --group dev

# Run tests
uv run pytest

# Run linting
uv run flake8 src/ tests/
uv run isort --check src/ tests/
uv run pydocstyle --config=pyproject.toml src/

# Install pre-commit hooks
uv run pre-commit install

Project structure

run.sh                     # Bot launcher (watch / hook / once / stop)
.claude-plugin/
  marketplace.json         # Plugin marketplace index
plugins/                   # Curated skills and MCP configs
src/megobari/
  __main__.py              # Entry point
  config.py                # Environment configuration
  bot.py                   # Telegram handlers
  claude_bridge.py         # Agent SDK integration
  session.py               # Session dataclass + manager
  formatting.py            # Formatter ABC (Telegram HTML, plain text)
  message_utils.py         # Message splitting, formatting helpers
tests/

Architecture

Telegram  <-->  bot.py  <-->  claude_bridge.py  <-->  Claude Code CLI
                  |                                        |
             formatting.py                           Agent SDK
                  |
           message_utils.py
                  |
             session.py  <-->  .megobari/sessions/sessions.json

The Formatter abstraction decouples presentation from logic. Swap TelegramFormatter for another implementation to support Discord, Slack, CLI, etc.