aipager
Telegram remote control for Claude Code
sessions. Claude runs on your computer inside a detached terminal
(dtach), and you use it from your phone: read Claude's answers, send it
messages, answer its permission prompts and questions, and switch between
sessions, with no SSH connection kept open.
aipager.run · Docs · Changelog · Issues
Read this in: Español · Русский · Português (Brasil) · 简体中文 · Français · Deutsch · 한국어 · العربية · Bahasa Indonesia · Українська · Italiano · Türkçe · فارسی · Tiếng Việt
Install
Have a coding agent (Claude Code, or any agent with a shell)? Create a bot with @BotFather, press Start in it, and make sure you are logged in to Claude Code on this machine. Save the bot token to a file your agent never has to read (paste the token, press Enter, then Ctrl-D):
mkdir -p ~/.config/aipager
rm -f ~/.config/aipager/bot-token
(umask 077 && cat > ~/.config/aipager/bot-token)
chmod 600 ~/.config/aipager/bot-token
Then give your agent this prompt:
Install aipager for me by following https://aipager.run/agent.md. My Telegram bot token is in ~/.config/aipager/bot-token and my Telegram user id is <your id>.
If you do not know your Telegram user id, say so instead; the agent can find it.
The guide it follows, including how to hand over the token safely, is docs/install-with-an-agent.md. To install it yourself, read on.
Linux or macOS, any architecture. dtach is installed automatically
via the dtach-bin dependency -
no separate system package needed.
One-line install (recommended)
curl -fsSL https://raw.githubusercontent.com/dev-aly3n/aipager/main/install.sh | sh
It uses uv if present, else pipx, else (on macOS only) Homebrew. If
none is found, it bootstraps uv (Astral's Python tool manager) and
installs through it.
uv (recommended on macOS)
uv tool install aipager # if uv is already installed
Or, to install uv first:
curl -LsSf https://astral.sh/uv/install.sh | sh
uv tool install aipager
uv bundles its own Python interpreter, so this works on any macOS / Linux version regardless of what system Python is doing - it sidesteps the Homebrew-Python-vs-Xcode breakage described under the Homebrew section below.
pipx
pipx install aipager
Homebrew tap (macOS, Linuxbrew)
Note:
uv tool install aipageris the recommended path on macOS. The brew formula works when Homebrew'spython@3.12bottle and your Xcode / Command Line Tools are in sync, but they periodically drift apart - most recently on macOS Tahoe (26.x), where install fails with apyexpat _XML_SetAllocTrackerActivationThresholdsymbol error (upstream issue). Updating Xcode + Command Line Tools usually fixes it, but it's easier to just use uv.
brew install dev-aly3n/tap/aipager
Pulls dtach from Homebrew's standard formula and installs aipager into
a Homebrew-managed Python venv.
Docker
Self-contained image with python, node, claude and dtach baked in,
good for VPS / NAS / Pi deployments where you don't want a Python
or Node toolchain on the host. Multi-arch (amd64, arm64).
# 1. Run the setup wizard once (interactive)
docker run --rm -it \
-v "$HOME/.claude:/home/aipager/.claude" \
-v aipager-config:/home/aipager/.config/aipager \
ghcr.io/dev-aly3n/aipager:latest config
# 2. Start the daemon (background, auto-restart)
docker run -d --restart=unless-stopped --name aipager \
-v "$HOME/.claude:/home/aipager/.claude" \
-v aipager-config:/home/aipager/.config/aipager \
-v "$PWD:/workspace" \
ghcr.io/dev-aly3n/aipager:latest
Mount the directories you want claude to edit under /workspace. The
~/.claude mount carries over your claude credentials and
conversation history - run claude on the host once to authenticate,
or docker exec -it aipager claude for an interactive login in the
container.
Tags: latest, 1.2, 1.2.0 (semver track + minor track).
Nix flake
nix run github:dev-aly3n/aipager -- --version
nix profile install github:dev-aly3n/aipager
Builds aipager from source against pinned nixpkgs deps. dtach is
provided by Nix; claude is not - install it separately
(nix profile install nixpkgs#nodejs && npm install -g @anthropic-ai/claude-code, or follow Anthropic's docs).
For declarative NixOS / Home Manager configs, add aipager as a flake
input and pick its package up from environment.systemPackages:
{
inputs.aipager.url = "github:dev-aly3n/aipager";
outputs = { self, nixpkgs, aipager, ... }: {
nixosConfigurations.myhost = nixpkgs.lib.nixosSystem {
modules = [({ pkgs, ... }: {
environment.systemPackages = [
aipager.packages.${pkgs.system}.default
];
})];
};
};
}
aipager service install will then wire up a systemd-user unit.
Snap
snap install aipager
Strict-confinement snap that bundles python + node + claude +
dtach + aipager. Because of snap's sandbox model, workspaces must
live under ~/ (e.g. ~/projects/foo). Manifest at
packaging/snap/.
Configure
aipager config
Interactive wizard - asks for your Telegram bot token (from
@BotFather) and chat ID, validates them, then
patches ~/.claude/settings.json to wire the necessary hooks
automatically. You never edit any file by hand.
Setting aipager up for someone from a script or a coding agent?
aipager setup --token-file FILE --chat-id ID does the same with no
prompts (see the setup command
and the guide for agents).
Run
aipager start
The daemon stays in the foreground. Launch a Claude session in another terminal:
aipager session dev
This creates (or reattaches to) a dtach session named claude-dev
running Claude Code. The aipager daemon finds it within seconds and
Telegram starts showing it. You can also start a session from Telegram:
send /new dev to the bot. Re-run the same command to reattach
later; to leave without stopping Claude, close the terminal or tmux
pane (the session keeps running).
If the dtach session was killed (machine reboot, etc.) but you want
to pick up the Claude conversation from disk, add --continue:
aipager session dev --continue # the last claude conversation in this folder
You can also pass --resume <session-id> (or any other claude flag)
through as trailing args:
aipager session dev -- --resume abc1234
Run as a service (survives logout)
aipager service install
On Linux this writes a systemd-user unit at
~/.config/systemd/user/aipager.service and starts it. On macOS it
writes a launchd plist at ~/Library/LaunchAgents/com.aipager.daemon.plist
and bootstraps it. Subcommands: start, stop, status, logs,
uninstall.
Team mode (groups and other people)
aipager is a private bot by default: you and the bot in one private
chat. To share it, add a Telegram group, other people's own private
chats with the bot, or both. For a group, add the bot to the group (as
an admin, so it can pin the group's status bar), run aipager config
again and pick Add a group scope. The wizard offers you (the owner
of your own private chat) as the group's owner, adds each member with a
role (owner, admin, user or read_only), asks for the members'
root folder, and reloads the running daemon. In the group the bot acts
only on commands, replies to its messages and mentions
(@aipagerbot fix the tests, /jim run the tests), and each message
runs with its sender's role. A user or read_only member starts and
keeps sessions only inside their chat's root folder (by default
~/aipager-users/<label>). Adding a member gives them the right to
run code on your computer: see docs/groups.md for
the full trust model.
What it does
- Shows what each Claude Code session is doing in Telegram: working or idle, its tool calls, context %, cost and changed lines, on one card per turn, then Claude's answer
- Sends your messages to Claude at once, even while it works: send several and Claude queues them itself, exactly like typing in the terminal. 👀 means sent, 👍 means Claude took it
- Holds a message while a permission prompt or a question is open, so it is never read as the answer to it, and sends it once you have answered
- Shows Claude's permission prompts and questions with buttons (Allow, Deny, Allow always, one per option); a button left over from a finished task refuses instead of acting on the work running now
- Three permission modes per session, switched with
/mode: 💬 Ask mode (Claude asks before each action), 🤖 Auto mode, the default (Claude Code's own safety check runs safe actions and stops risky ones for you to decide) and 🔓 Full access mode (everything runs with no checks; for admins, and for you in your own private chat) - Starts sessions from the chat:
/new x1starts one at once (/new x1 fix the testsalso sends its first message), with the mode, model and folder set in/settings, and buttons to change them - Takes photos, files and voice messages (voice is turned into text on your computer, with the optional voice extra)
- Tells you about context warnings, compaction, a session that ended and one that went quiet
- Runs several sessions at once with one bot; optional team mode with roles and per-tool rules (docs/groups.md)
- Speaks English, Español, Русский, Português (Brasil), 简体中文, Français, Deutsch, 한국어, العربية, Bahasa Indonesia, Українська, Italiano, Türkçe, فارسی and Tiếng Việt: only aipager's own text, never your sessions or Claude's answers (docs/commands.md). This README and the docs are translated too (see Read this in above)
Mini App
/app opens a dashboard inside Telegram: your sessions with Stop, End,
Restart, Rename and the mode switch, a diff viewer for Write/Edit
changes, the settings and, for the owner, Report a problem. It is
served by the daemon itself and is on by default; every request is
checked against Telegram's initData signature. If you belong to more
than one chat (your DM and a group), a row of chat names at the top
switches between them. Manage it with aipager miniapp enable|disable|status, or point it at your own URL instead of the
managed tunnel - see
docs/security.md.
Note on model buttons (Bedrock / Vertex users)
The persistent keyboard's Model submenu (and the Mini App's model
pickers) offers Claude Code's family aliases, sonnet, opus, haiku,
fable and opusplan, and pinned models such as claude-opus-5-5 and
claude-sonnet-5-5 (the full list is in
docs/commands.md). On the
Anthropic API an alias resolves to the latest model in its family. On
Bedrock and Vertex the same aliases may resolve to older
snapshots depending on your provider's available versions. If you
target those backends and want a specific model, send /model <full-id> from chat.
Developing locally
git clone https://github.com/dev-aly3n/aipager.git && cd aipager
python3 -m venv .venv && source .venv/bin/activate
pip install -e '.[dev]'
systemd-run --user --scope -q -p MemoryMax=2G -p MemorySwapMax=0 \
.venv/bin/python -m pytest -q -p no:cacheprovider
ruff check aipager tests
dtach comes with the dtach-bin dependency, so nothing else is
needed. Run the tests under a memory cap as above (on macOS, without
systemd-run): a runaway test can otherwise take the machine's memory.
Release process is in CONTRIBUTING.md.
License
MIT - see LICENSE.
Metadata
Release files for aipager 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aipager-1.2.0.tar.gz | 7.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aipager-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.0 MB
Release files / aipager-1.2.0.tar.gz
| Download URL | aipager-1.2.0.tar.gz |
|---|---|
| Size | 7.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
227ecc62705a03c7593f46a299e97be3065d393b4348e2187f6ba9464e4c14b8
|
|
BLAKE2b-256 checksum How to use checksums |
52f05fc1f83a03628a4d5770bf01ed462ca1354881d0ad6e2c3767b69f1e158f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logRelease files / aipager-1.2.0-py3-none-any.whl
| Download URL | aipager-1.2.0-py3-none-any.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d570b98f29f18b9c24b278f0a8f6a280b157b00eb65c2bcf3f27b5629039d04
|
|
BLAKE2b-256 checksum How to use checksums |
5c411d1715ce21f13a1f17e37bd7ded9743257e302b213702e1a4f130646db5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency log