# Telegram Codex Bridge (Codex)

Route Telegram replies back into Codex sessions using non-interactive
`codex exec` + `codex exec resume`.

The bridge stores a mapping from `(chat_id, bot_message_id)` to a route so
replies can be routed correctly.

## Install

1. Ensure `uv` is installed.
2. From this folder, run the entrypoints with `uv run` (uses `pyproject.toml` deps).
3. Put your Telegram credentials in `~/.codex/telegram.toml`.

Example `~/.codex/telegram.toml`:

```toml
bot_token = "123:abc"
chat_id = 123456789
```

`chat_id` is used both for allowed messages and startup notifications.

Optional keys:

- common: `bridge_db`, `allowed_chat_ids`, `startup_chat_ids`
- exec/resume: `startup_message`, `codex_cmd`, `codex_workspace`, `codex_exec_args`, `max_workers`, `codex_io_mode`, `codex_command_timeout_s`, `codex_no_child_timeout_s`

## Option 1: exec/resume

Run:

```bash
uv run exec-bridge
```

Optional flags:

- `--progress-edit-every FLOAT` (default `2.0`)
- `--progress-silent/--no-progress-silent` (default silent)
- `--final-notify/--no-final-notify` (default notify via new message)
- `--ignore-backlog/--process-backlog` (default ignore pending updates)
- `--codex-io-mode [threads|selectors|asyncio]` (default `threads`)
- `--codex-command-timeout FLOAT` (default: disabled, debug defaults to 60s)
- `--codex-no-child-timeout FLOAT` (default `15.0`, set `0` to disable)
- `--workdir PATH` (override `codex_workspace`)
- `--model NAME` (pass through to `codex exec`)

## Files
- `src/codex_telegram_bridge/constants.py`: limits and config path constants
- `src/codex_telegram_bridge/config.py`: config loading and chat-id parsing helpers
- `src/codex_telegram_bridge/exec_render.py`: renderers for codex exec JSONL events
- `src/codex_telegram_bridge/rendering.py`: markdown rendering
- `src/codex_telegram_bridge/routes.py`: sqlite routing store
- `src/codex_telegram_bridge/telegram_client.py`: Telegram Bot API client
- `src/codex_telegram_bridge/exec_bridge.py`: codex exec + resume bridge