Publish a guide to steering a running Codex turn from a phone

[artemiia]

What changes for the user?

Adds one blog post at /blog/how-to-steer-a-running-codex-turn-from-your-phone-and-keep-ctrl-x-working/.

• Title: How to Steer a Running Codex Turn From Your Phone and Keep Ctrl-X Working
• Format: tutorial (category Guide), by Artemii Amelin, dated 2026-10-17
• News hook: Codex CLI 0.163.0 (released 2026-10-15) takes follow-ups while a turn is running (instant interrupts on by default) and adds a leader key whose default is Ctrl+X. That is also the first key of shell attach's Ctrl-X D detach sequence.
• What it covers: starting Codex with shell --name ... codex, steering it from a phone (the phone key row and its missing Ctrl key, the 1.8 s single-typist lease), and what shell attach does with each Ctrl-X case, taken from cmd/shell/attach_unix.go (750 ms window, Ctrl-] legacy key, the browser link bypassing the filter). It also has a section on what the setup does not do.
• Files:
  • blog/posts.json (new first entry)
  • blog/posts/how-to-steer-a-running-codex-turn-from-your-phone-and-keep-ctrl-x-working.html
  • public/blog/banners/how-to-steer-a-running-codex-turn-from-your-phone-and-keep-ctrl-x-working.webp (1200x630)

Verification

Run from the repository root on this branch:

• python3 ../tools/lint_post.py <slug>: passed (1,897 words, 27 links: 15 outside across 8 sites, 3 to pilotprotocol.network). One warning: the GitHub repository is linked twice.
• python3 ../tools/check_links.py blog/posts/<slug>.html: 26 links, 26 ok, 0 blocked, 0 dead
• npx vitest run tests/blog.test.ts: 1 file, 15 tests passed
• node scripts/test-landing-seo.mjs: passed
• npm run build:web: succeeded

I checked the post's statements about shell against help.go, docs/content.json, cmd/shell/attach_unix.go, cmd/shell/session_unix.go, worker/index.ts and web/main.ts. None of those code paths changed between v0.25.0 and main. Claims about Codex come from the 0.163.0 release notes and from PRs openai/codex#51812 and #52273.

Access and privacy

No product change. This adds content only. The session ID, path and session name in the examples are made up.

• No real share links, credentials, private terminal content or deployment secrets are included.
• User-facing docs and the changelog are updated, or I explain why no update is needed. (An article does not need a changelog entry.)

Rollout

Website only. The post goes live after the next deploy. No CLI or host update is needed.

🤖 Generated with Claude Code