Telegram-based remote AI coding automation server
Project description
Remote AI Coder
Run Claude Code, Codex, Gemini, or Ollama on your local development machine by sending a Telegram message. Remote AI Coder isolates each request in a Git worktree, commits the result on a separate branch, and reports the outcome back to Telegram.
English: this document · 한국어: README.ko.md
[!WARNING] This is a local automation tool with access to AI CLIs, Git, and your filesystem. Keep it private, use Telegram allowlists, and do not expose the server or admin UI to the public internet.
What You Get
- Telegram as a lightweight remote control for local coding agents.
- One Telegram bot per registered project, with project-scoped allowlists and settings.
- Request-specific Git worktrees, branch creation, commit, push, and result notifications.
- Claude, Codex, Gemini, and Ollama runners behind the same job flow.
- Reply-linked jobs continue the same AI CLI session, so follow-ups build on prior context.
- Local admin UI for project setup, advanced settings, logs, and conversation memory.
- Read-only
plan:,ask:, andresearch:modes when you want analysis without commits. PLAN mode asks open decisions through inline buttons first, then finalizes the plan from your answers; RESEARCH mode asks the selected AI CLI to use internet search when useful. - Declarative mode addons: drop a YAML file under
~/.remote-coder/addons/to add your own read-only prompt-preset mode without code changes. See docs/mode-addons.md.
Quick Start
Install the CLI:
pip install remote-coder
Or install the latest development version from source:
pip install git+https://github.com/maroomir/remote-coder.git
Check your local tools, then start everything:
remote-coder doctor
remote-coder up
Open http://127.0.0.1:8000/, add your first project, and message the project bot in Telegram. remote-coder up runs the server, starts the ngrok tunnel, registers webhooks, and refreshes the Telegram command menu. Use remote-coder up --no-tunnel when you only want the local server.
Requirements
- Python 3.11+
ngrokor another HTTPS tunnel for Telegram webhooks- One Telegram bot token per project
- Allowed Telegram Chat IDs, and optionally User IDs
- At least one local AI CLI/provider:
claude,codex,gemini, orollama - A local Git repository to automate
- GitHub CLI (
gh) authenticated withgh auth loginwhen using/pr
How It Works
Telegram message
-> FastAPI webhook /telegram/webhook/{sha256-prefix16}
-> project-bound bot instance and allowlist check
-> command parser or natural-language confirmation
-> JobManager
-> Git worktree
-> Claude / Codex / Gemini / Ollama runner
-> branch, commit, push, and Telegram result
Each project uses its own bot. The webhook path contains the first 16 hex characters of SHA-256(bot token), never the raw token. Natural-language jobs show the target project, branch, model, and mode before running, then wait for confirmation.
Everyday Commands
| Command | Purpose |
|---|---|
/start, /help |
Open the menu or command help |
/model |
View or change the chat's default model |
/status [job_id] |
Inspect recent or specific jobs; running jobs show the latest captured AI output when available |
/log [job_id] |
Pick a recent job or show captured AI stdout for a specific job |
/branch [name] |
Show or switch the bound project's local branch |
/pull |
Fetch remotes and pull the current branch |
/rebase [branch] |
Rebase and fast-forward a completed branch into main or master |
/pr [branch] |
Create a GitHub PR from a succeeded Job branch with gh |
/fix ... |
Rework a previous job's commit message or source |
/monitor ... |
Inspect model, memory, branch, worktree, code, or project status |
/clear ... |
Clean managed branches, worktrees, or conversation memory |
/stop [job_id] |
Cancel a queued or running job |
/init |
Reset chat-local model and pending confirmations |
Calling /pr without a branch lists only remote branches produced by succeeded Jobs in the current project and Telegram chat. Direct /pr <branch> calls enforce the same ownership check and verify that the branch still exists on the configured Git remote. Install the GitHub CLI and run gh auth login before using this command.
Natural-language examples:
Fix the login validation bug with model: codex
ask: model: ollama explain the parser flow
plan: outline the migration before changing code
/ask what test command does this repo use?
/research compare current Telegram webhook security guidance
수정: 방금 작업에서 README 문구만 더 간결하게 바꿔줘
Configuration
Day-to-day setup happens in the local admin UI. Files live under REMOTE_CODER_HOME, defaulting to ~/.remote-coder:
projects.jsonstores project records, bot tokens, allowlists, root paths, and default models.advanced_settings.jsonstores global behavior such as timeouts, sandbox mode, language, worktree retention, and memory limits.worktrees/<project>/contains managed job worktrees and logs.ollama_sessions/stores local Ollama reply-chain transcripts for session continuity.- On server startup, queued Jobs stored in SQLite are rerun; Jobs that were running when the server stopped are marked failed with
server_restartfor/statusreview.
Useful overrides: REMOTE_CODER_HOME, PROJECTS_CONFIG_PATH, CONVERSATION_DB_PATH, JOB_DB_PATH, OLLAMA_HOST, and REMOTE_CODER_OLLAMA_DEFAULT_MODEL.
Security Notes
- Treat
~/.remote-coder/projects.jsonas a secret; bot tokens are stored in plain text. - Keep the admin UI on localhost.
- Do not paste secrets or sensitive code into Telegram messages.
- Dangerous runner modes such as Claude
--dangerously-skip-permissions, Gemini--approval-mode yolo, Codexdanger-full-access, and Ollama-generated patches can modify local files. - See
SECURITY.mdbefore publishing, exposing, or sharing a deployment.
More Docs
- Multi-bot setup and migration:
docs/multi-bot-setup.md - AI runners:
docs/ai-runners.md - Read-only worktree troubleshooting:
docs/read-only-workspace.md - Contributing:
CONTRIBUTING.md
Development
conda env create -f environment.yml
conda activate remote-coder
python -m pip install -e ".[dev]"
remote-coder up --no-tunnel --reload
Run the test suite:
PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 conda run -n remote-coder pytest -q -p pytest_asyncio.plugin -p respx.fixtures
License: Apache License 2.0
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file remote_coder-0.6.0.tar.gz.
File metadata
- Download URL: remote_coder-0.6.0.tar.gz
- Upload date:
- Size: 297.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6de664d686b50abc88600ba18d5eb9d8b26e4924a350086ff80e307620df7823
|
|
| MD5 |
82249d7b17a11d54974a49b82bc8a7cb
|
|
| BLAKE2b-256 |
1ce205d6062cb03ecbbb346ccb9b6d98bd471ca86b960ee792e026c099b0075d
|
Provenance
The following attestation bundles were made for remote_coder-0.6.0.tar.gz:
Publisher:
release.yml on maroomir/remote-coder
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
remote_coder-0.6.0.tar.gz -
Subject digest:
6de664d686b50abc88600ba18d5eb9d8b26e4924a350086ff80e307620df7823 - Sigstore transparency entry: 1909141969
- Sigstore integration time:
-
Permalink:
maroomir/remote-coder@dce5996da69f5f9b883914820c3c08ef198e9e17 -
Branch / Tag:
refs/tags/v0.6.0 - Owner: https://github.com/maroomir
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@dce5996da69f5f9b883914820c3c08ef198e9e17 -
Trigger Event:
push
-
Statement type:
File details
Details for the file remote_coder-0.6.0-py3-none-any.whl.
File metadata
- Download URL: remote_coder-0.6.0-py3-none-any.whl
- Upload date:
- Size: 240.5 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
195d5de512b675591902c9e3230f901cbd84ec4e1dac00cb5b5136770f7a757c
|
|
| MD5 |
a7f98ab92971a66e266a9b4b55f5661c
|
|
| BLAKE2b-256 |
103d204a7be5c4df2904f792800c00cb643922f346c3508b267256e88c06def1
|
Provenance
The following attestation bundles were made for remote_coder-0.6.0-py3-none-any.whl:
Publisher:
release.yml on maroomir/remote-coder
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
remote_coder-0.6.0-py3-none-any.whl -
Subject digest:
195d5de512b675591902c9e3230f901cbd84ec4e1dac00cb5b5136770f7a757c - Sigstore transparency entry: 1909142156
- Sigstore integration time:
-
Permalink:
maroomir/remote-coder@dce5996da69f5f9b883914820c3c08ef198e9e17 -
Branch / Tag:
refs/tags/v0.6.0 - Owner: https://github.com/maroomir
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@dce5996da69f5f9b883914820c3c08ef198e9e17 -
Trigger Event:
push
-
Statement type: