# Telegram Usage

Plain text sent from an allowed Telegram chat is forwarded to the configured Linux account’s shell.

Examples:

```
pwd
ls -la
systemctl --user status
tail -n 100 /var/log/syslog
```

## Control Commands

| Command | Description |
| --- | --- |
| `/status` | Show uptime, PID, allowlist, and rate counters |
| `/sigint` | Send Ctrl-C to the shell |
| `/sigterm` | Send SIGTERM to the shell |
| `/restart` | Restart only the shell while keeping the program running |
| `/lock` | Temporarily block shell input |
| `/unlock` | Resume shell input |

## Interactive Program Limits

Telegram uses message-based input and output. TUI and interactive programs like these cannot be controlled reliably:

- `vim`
- `vi`
- `nano`
- `less`
- `more`
- `man`
- `top`
- `htop`
- `tmux`
- `screen`

These programs depend on real-time key input, cursor control, and ANSI escape sequences. With Telegram messages only, they may appear frozen or unusable.

`rtmn` blocks some known interactive programs before execution. This is a convenience guardrail, not a security boundary.

The real security boundaries are:

- Telegram chat allowlist
- Linux execution account permissions
- Server file permissions and sudo policy