takopi
🐙 he just wants to help-pi
telegram bridge for codex, claude code, opencode, pi. manage multiple projects and worktrees, stream progress, and resume sessions anywhere.
features
- projects and worktrees: work on multiple repos/branches simultaneously, branches are git worktrees
- stateless resume: continue in chat or copy the resume line to pick up in terminal
- progress streaming: commands, tools, file changes, elapsed time
- parallel runs across agent sessions, per-agent-session queue with Codex steering/cancel controls
- works with telegram features like voice notes and scheduled messages
- file transfer: send files to the repo or fetch files/dirs back
- group chats and topics: map group topics to repo/branch contexts
- works with existing anthropic and openai subscriptions
requirements
uv for installation (curl -LsSf https://astral.sh/uv/install.sh | sh)
python 3.14+ (uv python install 3.14)
at least one engine on PATH: codex, claude, opencode, or pi
install
uv tool install -U takopi
setup
run takopi and follow the setup wizard. it will help you:
- create a bot token via @BotFather
- pick a workflow (assistant, workspace, or handoff)
- connect your chat
- choose a default engine
workflows configure conversation mode, topics, and resume lines automatically:
- assistant: ongoing chat with auto-resume (recommended)
- workspace: forum topics bound to repos/branches
- handoff: reply-to-continue with terminal resume lines
usage
cd ~/dev/happy-gadgets
takopi
send a message to your bot. prefix with /codex, /claude, /opencode, or /pi to pick an engine. reply to continue a thread.
register a project with takopi init happy-gadgets, then target it from anywhere with /happy-gadgets hard reset the timeline.
mention a branch to run an agent in a dedicated worktree /happy-gadgets @feat/memory-box freeze artifacts forever.
inspect or update settings with takopi config list, takopi config get, and takopi config set.
see takopi.dev for configuration, worktrees, topics, file transfer, and more.
plugins
takopi supports entrypoint-based plugins for engines, transports, and commands.
see docs/how-to/write-a-plugin.md and docs/reference/plugin-api.md.
development
1 maintainer
Metadata
1 maintainer
Release files for takopi 0.23.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| takopi-0.23.4.tar.gz | 129.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| takopi-0.23.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 304.1 kB
Release files / takopi-0.23.4.tar.gz
| Download URL | takopi-0.23.4.tar.gz |
|---|---|
| Size | 129.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b27955aacb6497f959a6edaeb1c92788b483fcb7f03f30904dc9ccea10fe63d
|
|
BLAKE2b-256 checksum How to use checksums |
8f6ad648b09dd668f2d513f9b9d37faac8bffa1a65fd12445c9885b4eeebe5b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 25, 2026.
Transparency logRelease files / takopi-0.23.4-py3-none-any.whl
| Download URL | takopi-0.23.4-py3-none-any.whl |
|---|---|
| Size | 174.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
605922397c038c09d5d6e22f83623f0e900d9101aa47e6794edb2fb16f26b6dc
|
|
BLAKE2b-256 checksum How to use checksums |
ceedce72ae5a347f0327d527dadbe648898154146a21d4223a50fec3989b4b19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 25, 2026.
Transparency log
