Termux integration
Run commands in the separate Termux app, setup steps, timeouts, output caps and sessions.
If you use the Termux app, CX can run commands in it. Open the Termux settings page (search settings for "Termux", or Cx Orbit → Tools → Termux).
Setup#
- Install Termux (from F-Droid or GitHub releases). The status row shows Installed — tap to open or Not installed — tap to download.
- Grant the RUN_COMMAND permission (tap to request).
- In Termux, allow external apps:
mkdir -p ~/.termux
echo 'allow-external-apps=true' >> ~/.termux/termux.properties
Then force-stop Termux from Android App Info and reopen it.
- Tap the allow-external-apps row to run the smoke test until it says Verified OK. If it times out, the property is probably not set.
Timeouts and limits#
| Setting | Range |
|---|---|
| Default command timeout | 5 – 600 s |
| Per-turn wall-clock budget (all tools) | 1 – 60 min |
| Tool steps per turn | 1 – 500 |
| Verify smoke-test timeout | 3 – 30 s |
| Default working directory | path |
| Stdout capture cap | 1,000 – 64,000 bytes |
| Stderr capture cap | 500 – 16,000 bytes |
| Auto-wrap apt/dpkg as noninteractive | Adds DEBIAN_FRONTEND=noninteractive so upgrades don't hang. |
What the agent can do#
termux_run_command– run a command in the background and read stdout/stderr/exit code.termux_session_start / send / read / list / kill– persistent interactive sessions (tmux, real pty) for SSH, sudo prompts, REPLs.transcribe_audio_file/whisper_status– speech-to-text with whisper.cpp inside Termux.
Open Termux launches the app. The Doctor (health check) also verifies Termux.