- Home
- Skills
- Workflow Automation
- opencode telegram gateway
Works with the AI Agents you already use
opencode telegram gateway
Control and prompt your OpenCode sessions directly from Telegram
$20
opencode telegram gateway
Example session with this skill installed
Set up the OpenCode Telegram gateway on this machine. Connect it to my running OpenCode service, run doctor to verify the setup, and configure it to run as a background service.
- Read your context and instructions
- Compiled the opencode telegram gateway
Summary
The opencode-telegram-gateway has been detected, verified, and configured to run as a persistent background service connected to your local OpenCode instance.
Execution & Verification Log
| Step | Action | Status | Notes |
|---|---|---|---|
| 0. Environment | Node v22.18.0, OpenCode 0.1.x | PASS | Node >= 20 verified |
| 1. Endpoint | Discovered 127.0.0.1:45278 from service.json | PASS | Loopback bind confirmed |
| 2. Auth & Config | Telegram getMe token validation | PASS | User ID allowlisted; permissions locked |
| 3. Health Check | node dist/index.js doctor | PASS | All 6 pre-flight diagnostics passed |
| 4. Daemon | Registered background service | ACTIVE | Auto-starts at logon / boot |
Telegram Command Quick Reference
You can now open Telegram and interact with your bot:
/ping– Check bridge uptime, OpenCode connection, and queue depth./sessions– View active coding sessions with inline buttons to switch or delete./use <id>– Switch your active workspace./diff– View pending uncommitted changes directly in Telegram./lock– Emergency freeze to pause all turns and deny pending tool requests.
Next Steps
- Open Telegram and send
/pingto verify round-trip latency. - Send a simple prompt such as
what files are in this project?to test turn execution.
Connects securely to your tools. The creator never sees your data.
About this skill
Drive your OpenCode coding sessions directly from Telegram with zero open ports, zero tunnels, and zero runtime dependencies.
The gateway functions as an outbound-only daemon that long-polls Telegram and communicates locally with your OpenCode HTTP API. Whether you are away from your workstation, commuting, or reviewing work on your phone, you get full interactive control over your AI coding agent.
Key Capabilities
- Outbound-Only Architecture: No port forwarding, public IPs, or reverse proxies required.
- Queue-Safe Execution: Prompts queue sequentially per session; never triggers race conditions or collisions in OpenCode.
- Interactive Approval Cards: High-risk tool calls (file edits, shell commands) arrive with risk-level labels and buttons to Approve Once, Approve Always, or Deny.
- Full Session Management: Switch active sessions (
/use), spawn new workspaces (/new,/newdir), inspect git diffs (/diff), or branch off side questions (/btw). - Secret Redaction: Outbound responses are automatically scrubbed of API keys, tokens, and private keys before reaching Telegram.
- Scheduled & Recurring Prompts: Set delayed runs (
/schedule in 10m) or recurring cron jobs (/cron). - Emergency Kill Switch: Instantly freeze turns, deny pending approvals, and protect sessions with
/lockand/unlock. - Auditing & Telemetry: Full append-only JSONL audit logs with rotation.
Requires Node.js v20+. Only supports local 127.0.0.1 OpenCode API connections. Background persistence on Linux requires linger to be enabled via loginctl.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 25 days ago
Requires
Permissions
Allowed Hosts
Outbound network access is strictly confined to polling api.telegram.org and reaching 127.0.0.1 for the local OpenCode daemon. No inbound ports or listening servers are created.