Metadata-Version: 2.4
Name: oc-rox
Version: 0.2.0
Summary: Control your OpenCode session from Telegram
Author: prime
License-Expression: MIT
Project-URL: Homepage, https://github.com/make-moneyy/oc-rox
Project-URL: Issues, https://github.com/make-moneyy/oc-rox/issues
Keywords: opencode,telegram,bot,bridge,cli
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: python-telegram-bot>=20.0
Requires-Dist: pexpect>=4.8.0
Requires-Dist: python-dotenv>=1.0.0
Provides-Extra: dev
Requires-Dist: build; extra == "dev"
Requires-Dist: twine; extra == "dev"
Dynamic: license-file

# 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`..

### 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
