Stateless Resume: No database required—sessions are resumed via resume: <uuid> lines embedded in messages
Progress Updates: Real-time progress edits showing commands, tools, and elapsed time
Markdown Rendering: Full Telegram-compatible markdown with entity support
Concurrency: Handles multiple conversations with per-session serialization
Token Redaction: Automatically redacts Telegram tokens from logs

Quick Start

# Clone and enter the directory
cd takopi

# Run directly with uv (installs deps automatically)
uv run takopi --help

Create ~/.codex/takopi.toml (or ./codex/takopi.toml for a repo-local config):

bot_token = "123456789:ABCdefGHIjklMNOpqrsTUVwxyz"
chat_id = 123456789

Key	Description
`bot_token`	Telegram Bot API token from @BotFather
`chat_id`	Allowed chat ID (also used for startup notifications)

The bridge only accepts messages where the chat ID equals the sender ID and both match chat_id (i.e., private chat with that user).

uv run takopi

Flag	Default	Description
`--final-notify` / `--no-final-notify`	`--final-notify`	Send final response as new message (vs. edit)
`--debug` / `--no-debug`	`--no-debug`	Enable verbose logging
`--cd PATH`	cwd	Working directory for Codex
`--model NAME`	(codex default)	Model to use

Usage

Send any message to your bot. The bridge will:

Reply to a bot message (containing resume: <uuid>), or include the resume line in your message:

resume: `019b66fc-64c2-7a71-81cd-081c504cfeb2`

Startup: Pending updates are drained (ignored) on startup
Progress: Updates are throttled to ~2s intervals, sent silently
Notifications: Codex's built-in notify is disabled (bridge handles it)
Filtering: Only accepts messages where chat ID equals sender ID and matches chat_id

See developing.md for architecture details.

# Run tests
uv run pytest

# Run with debug logging
uv run takopi --debug 2>&1 | tee debug.log

MIT