Last updated: 2026-05-28
PC Companion Setup
One-time PC setup steps to unlock the full phone experience.
Pair Your Phone
hiterm pair
Auto-detects dependencies, prints install commands if anything is missing, then generates a QR code. Scan it from your phone to pair.
Name Sessions for Quick Access
tmux new -A -s backend-gemini
tmux new -A -s frontend-claude
Sessions appear in the โฐ side panel on your phone. Name them clearly โ that's how you'll switch between them.
Enable Notifications for Long Tasks
# Test notifications
hiterm notify test
# Login for AI tool hooks
hiterm login
Claude Code, Gemini CLI, and OpenAI Codex are auto-configured by hiterm pair. For other tools, use the prompt below.
Auto-Configure Notifications for Any AI Tool
Click to expand the prompt
You are configuring push notifications for Hi Term. Hi Term is a mobile terminal app โ when you finish a task or need attention, it pushes a notification to the user's Android phone.
Your task: add a notification hook to your own config file so Hi Term can notify the user.
## How it works
The hook command is:
hiterm notify hook --tool=<your-name> --event=<event>
Events:
stop โ you finished a task or session ended
notification โ you need the user's attention
Stdin: you will receive JSON context (cwd, session info, etc.) โ no action needed, just call the command.
## Steps
1. **Identify yourself**: Determine which AI tool you are (Claude Code, Gemini CLI, Codex, Cursor, Windsurf, Aider, Continue, etc.)
2. **Find your config file**: Locate your tool's settings/config file. Common locations:
- Claude Code: ~/.claude/settings.json
- Gemini CLI: ~/.gemini/settings.json
- Codex CLI: ~/.codex/config.toml
- Cursor: ~/.cursor/settings.json
- Windsurf: ~/.windsurf/settings.json
- Aider: ~/.aider.conf.yml
- If unsure, check your documentation or search for config files in your home directory.
3. **Determine the hook format**: Each tool has its own hook/event mechanism. Read your documentation to find how to register hooks that run a command on events like "task completed" or "notification".
For reference, here's how Claude Code does it (in ~/.claude/settings.json):
{
"hooks": {
"Stop": [{
"hooks": [{
"type": "command",
"command": "hiterm notify hook --tool=claude --event=stop"
}]
}],
"Notification": [{
"matcher": "*",
"hooks": [{
"type": "command",
"command": "hiterm notify hook --tool=claude --event=notification"
}]
}]
}
}
And how Codex does it (in ~/.codex/config.toml):
notify = ["hiterm notify hook --tool=codex --event=stop"]
4. **Write the config**: Read your config file first. If the hiterm hook already exists (contains "hiterm notify hook"), skip writing โ it's already configured. Otherwise, add the hook. Replace <your-name> with your tool name (lowercase, e.g., "cursor", "windsurf", "aider").
5. **Verify**: Read back the config file to confirm the hook was written correctly.
IMPORTANT: Write the actual config file. Do not just show the JSON/TOML/YAML.
Paste this into any AI tool โ it will find its own config and add the hook.
Diagnostics
# Auto-detect and fix most issues
hiterm doctor
Next Steps
- User Guide โ Two core workflows: PC-to-phone and phone-to-PC
- Phone Operations โ Gestures and navigation
- Command Reference โ All hiterm CLI commands
- Troubleshooting & FAQ โ Common issues