/ comparison
Cici vs SSH and tmux.
SSH and tmux are powerful general-purpose tools. Cici builds on the same local-session idea but adds a phone-first layer for coding agents.
Choose Cici when...
- You want a phone UI for approvals, prompts, and cancels.
- You want push notifications when an agent is blocked.
- You want non-terminal ergonomics for supervising long-running coding agents.
Choose SSH and tmux when...
- You want complete raw shell access from mobile.
- You already have secure SSH, mosh, and tmux configured exactly how you like.
- You do not need push notifications or agent-specific workflow controls.
Short answers
Why use Cici instead of SSH and tmux?
Use Cici when the job is supervising coding agents from mobile. It adds notifications, quick approvals, and a phone UI around the terminal session.
Can I still use tmux or my normal terminal setup?
Yes. Cici is designed for local terminal workflows and does not replace your Mac development environment.
local-first control
Run the agent on your Mac. Control it from your phone.
Cici is strongest when you want Claude Code, Codex, Gemini, OpenCode, Qwen, or another terminal coding agent to keep working locally while you respond from mobile.