Their agent, their app. Or your box, any CLI.
Official remotes are the right product if you live inside one vendor. They are the wrong product if the process on your VPS is tests, a shell, Codex today and Claude tomorrow.
Official mobile and remote-control surfaces from Anthropic (Claude Code) and OpenAI (Codex). They let you steer that vendor's agent from another device, inside that vendor's product.
Where they win. People who only run one vendor's agent and want that vendor's own mobile chat UX.
The difference. 1SessionTool is not competing with Claude or Codex official mobile as a chat UI. We win only if the job is a provider-neutral PTY on a box you own, with no vendor session.
| 1SessionTool | Claude Code Remote / Codex mobile | |
|---|---|---|
| Steer Claude / Codex from another device | If that CLI is the argv | Yes |
| Arbitrary CLI on your box | Yes | No |
| No vendor session required | Yes | No |
| Process lives on a host you own | Yes | Vendor product |
| Phone is glass, not the computer | Yes | Chat UX on the phone |
| Works with tests and a plain shell | Yes | No |
| Official chat UX for that vendor | No | Yes |
| Pricing | One-time license | Tied to the vendor subscription |
Checked September 2026. No competitor prices.
Can I still use Claude Code?
Yes. Spawn it. claude is the argv. 1SessionTool does not wrap it and does not replace the official client.
Will this be a better Claude mobile app?
No. That is a non-goal. If you want their chat UX, use their app.
Claude Code Remote / Codex mobile site · Switching from Claude Code Remote / Codex mobile