codex
Codex stays in the repo.
You stay on the couch.
Codex already gives you an agent in your git tree. We give that session a private phone channel — describe the task in plain language, watch a passing test, tap to show the diff — without turning the loop into another chat app.
Why this over a chat app.
- Keep Codex private. No account, no phone number, no contact graph, no workspace, no readable history on our server.
- Keep Codex local. The CLI works against your repo, tests, shell, and git state — on the machine where the project already lives.
- Keep chat apps out of it. Slack and Telegram are built for people. Diffs and approvals deserve a real surface.
- Keep the phone useful. Tap to decide. Glance at the result. Nudge the loop. Don't pretend the phone is a dev environment.
We're a line. Not a cockpit.
We don't try to out-feature Codex-oriented apps with worktree managers, schedules, voice, or PR dashboards. We wrap Codex with a private encrypted channel — for the moments when you need to steer, approve, read, or interrupt from a phone.
Two minutes to a phone-driven Codex.
Install and sign in to Codex first. Then wrap it from inside a git repo.
npm install -g @openai/codex
codex
hisohiso wrap codexCodex expects a git repo. We don't change that. We open an encrypted channel around the session.
What lands on the phone.
Describe the task. Answer questions. Glance at the result. The file edits and the commands still happen on the machine running Codex.
Hisohiso carries the conversation. Git carries the truth.
Codex handles the repo. We carry the line.
Use it when a normal messaging app is too broad and a phone app is too far from the working tree.