term-connect

Remote terminal CLI.

term-connect runs a local terminal session and exposes it through connectors. The current release ships with a Telegram connector, and the internal connector layout is prepared for additional transports later.

This app intentionally has no command restrictions, no chat allowlist, and no saved config. Anyone who can reach an enabled connector can execute commands on the machine running this process.

Install

npm install -g term-connect

Run

The default connector today is Telegram.

With a token:

term-connect start --token 123456:botfather-token

With an env var:

TELEGRAM_BOT_TOKEN=123456:botfather-token term-connect start

Or run without either and paste the token when prompted:

term-connect start

Usage

Send any command:

pwd
cd ..
ls -la
node -v

Or use /run:

/run echo hola
/run yes test | head -200

cd is handled by the v0 runner and persists for the following commands while the process is running.

Interactive commands stay attached to the current connector session. In Telegram, while a command is running, every new text message in that same chat is sent to the process as stdin.

/run cursor-agent
hello
/ctrlc
/close

Controls:

/ctrlc   send Ctrl-C to the active process
/close   close the active process
/run     replace the active process with a new command

The app streams stdout and stderr through SDK session events. Each connector decides how to deliver those events; Telegram sends them as chat messages in chunks.