oc-rox

control your opencode session from telegram bot

Install

pip install oc-rox

Put a .env file in ~/.config/oc-rox/ with:

TELEGRAM_BOT_TOKEN=your_bot_token
ALLOWED_TELEGRAM_USER_ID=your_telegram_id

Run

oc-rox

Run as a service

Same commands on Linux and macOS. oc-rox enable writes the service config once, resolving your oc-rox binary path automatically.

oc-rox enable        # installs service + starts now and at boot
oc-rox status        # check it
oc-rox stop          # stop
oc-rox disable       # stop + remove from boot
oc-rox start         # start again
oc-rox restart       # restart

Linux

oc-rox enable writes ~/.config/systemd/user/oc-rox.service and enables it. The service runs in your user context, so it can reach your tmux sessions and ~/.config/oc-rox/.env.

The service runs with a minimal PATH, so if opencode is not in /usr/bin etc., set its absolute path in ~/.config/oc-rox/.env:

OPENCODE_CMD=/path/to/opencode

The unit is regenerated on oc-rox enable (re-run it after changing OPENCODE_CMD or moving binaries).

macOS

oc-rox enable writes ~/Library/LaunchAgents/oc-rox.plist and loads it via launchctl. Logs go to ~/Library/Logs/oc-rox.log and oc-rox-error.log.

Windows

will add in few days