blog: Add Claude Remote Control with coder.ddev.com

AGENTS.md

@@ -59,8 +59,11 @@ When making commits after major changes, use AI-assisted commit messages that in
 
 Only commit when explicitly requested by the user.
 
+Always write the commit message to a file first, then commit with `git commit -F <file>`. Inline HEREDOCs inside `$(...)` (e.g. `git commit -m "$(cat <<'EOF' ... EOF)"`) are unreliable in bash — apostrophes or other special characters in the message can produce a confusing `unexpected EOF` parse error. Writing to a file (e.g. under the scratchpad directory) and using `-F` avoids this.
+
 **Never run `git push` (or any command that pushes to a remote), under any circumstances, even if explicitly asked.** The user always pushes their own branches/commits themselves.
 
+
 ## Working with Claude Code
 
 ### Branch Naming

src/content/blog/claude-remote-control-with-coder.md

@@ -0,0 +1,108 @@
+---
+title: "Claude Remote Control with coder.ddev.com"
+pubDate: 2026-07-17
+summary: "Run Claude Code in a disposable coder.ddev.com workspace, kick off a task with a tmux-backed helper script, then watch and steer it from claude.ai/code or your phone using Claude Code's Remote Control feature."
+author: Randy Fay
+featureImage:
+  src: /img/blog/2026/07/claude-remote-control-coder.png
+  alt: Claude and Coder logos stacked vertically
+categories:
+  - Training
+  - Videos
+  - Guides
+---
+
+Claude Code's [Remote Control](https://code.claude.com/docs/en/remote-control) feature connects [claude.ai/code](https://claude.ai/code) or the Claude mobile app (or macOS or Windows app) to a Claude Code session running elsewhere. The session itself keeps running wherever you started it — the web and mobile interfaces are just a window into it.
+
+Pairing Remote Control with a [coder.ddev.com](https://coder.ddev.com) workspace means the "elsewhere" is a disposable, sandboxed environment, not your computer. You can hand Claude a real task, switch it to auto mode without worrying about your own machine or credentials, and check in from your device while it works.
+
+## Watch the Video
+
+<div class="video-container">
+<iframe width="560" height="315" src="https://www.youtube.com/embed/CXiKVM4JYlE" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
+</div>
+
+## What You'll See
+
+- A real bug: the [Camino](https://github.com/rfay/typo3demo) TYPO3 theme describes the wrong pilgrimage route in one spot
+- Creating a **freeform** coder.ddev.com workspace and connecting to it with `coder ssh` instead of the web terminal
+- Cloning the project and logging into Claude Code
+- A small `cc-remote-control.sh` helper script that starts Claude Code inside a named `tmux` session, so the session survives disconnects and is reachable by name later
+- Handing Claude the bug description, then switching to auto-accept mode since the workspace is fully sandboxed
+- Watching Claude work from both the Claude app on the Mac and the Claude app on a phone, at the same time
+- Asking Claude to coach through contributing the fix back to the upstream project
+
+## Before You Start: Disable Autostop
+
+coder.ddev.com workspaces are configured by default to shut down automatically after a period of inactivity. That's fine for regular use, but if Claude is going to be doing work in a `tmux` session while you're away from the workspace — checking in later from your phone or from claude.ai/code — an autostop can pull the rug out from under it mid-task.
+
+Before starting, go to your workspace's **Settings → Schedule** and make sure **Enable Autostop** is turned off:
+
+![Coder.ddev.com workspace Schedule settings, with Enable Autostart and Enable Autostop both toggled off](/img/blog/2026/07/coder-schedule-autostop.png)
+
+:::warning[Disposable, not durable]
+coder.ddev.com is [experimental](coder-ddev-com-announcement.md) with no guarantees of retention or uptime. Disabling autostop keeps the workspace alive for your session, but you should still push finished work to Git — don't rely on the workspace itself as storage. And please turn off the workspace when not in use. Please don't abuse this service.
+:::
+
+## Steps
+
+1. Create a **freeform** workspace at [coder.ddev.com](https://coder.ddev.com).
+1. Connect over SSH with `coder ssh <workspace-name>` rather than the web terminal — it's a more natural fit for the rest of this workflow. (But the web terminal would work fine too.)
+1. Clone the project you want to work on and `cd` into it.
+1. Log in to Claude Code (`claude`) the first time, following the device-login flow in your browser.
+1. Start Claude inside a named `tmux` session using `cc-remote-control.sh`, a small wrapper script that keeps it running whether or not you're connected:
+
+   ```bash
+   #!/usr/bin/env bash
+
+   # Claude Code remote-control, with tmux usage
+   # cc-remote-control.sh <session> [dir]
+   set -euo pipefail
+
+   NAME="${1:?Usage: cc-remote-control.sh NAME [DIR]}"
+   DIR="${2:-$PWD}"
+
+   tmux new-session -As "$NAME" -c "$DIR" \
+     "claude --remote-control --name '$NAME'"
+   ```
+
+   Run it with a session name that matches the task, for example `cc-remote-control.sh caminofix`.
+
+1. Claude Code prints instructions for connecting from claude.ai/code or the Claude mobile app the moment the session starts.
+1. Describe the problem to Claude. Because the workspace is sandboxed (coder.ddev.com runs each workspace in a Docker-in-Docker [Sysbox](https://github.com/nestybox/sysbox) container), it's reasonable to switch to auto mode and let Claude keep going without approving every step.
+1. Check in from your phone or from claude.ai/code whenever you like — the local session doesn't care whether anything is watching.
+1. When Claude has a working fix, ask it to coach you through the contribution process for the upstream project, even if you aren't familiar with that project's conventions.
+
+## A Few tmux Basics
+
+`cc-remote-control.sh` is just a thin wrapper around `tmux new-session -As`, so it helps to know a handful of `tmux` commands if you haven't used it before:
+
+- `Ctrl-b d` — detach from the current session, leaving it running in the background. You'll probably want to do this right away.
+- `tmux new -s mysession` — start a new named session
+- `tmux new -As mysession` — attach to `mysession` if it already exists, or create it (this is what `cc-remote-control.sh` does)
+- `tmux ls` — list running sessions
+- `tmux attach -t mysession` — reattach to a session you detached from earlier
+
+Detaching is the key move: it lets you close your SSH connection (or lose it) without killing Claude's session, then pick it back up later with `tmux attach` or by rerunning `cc-remote-control.sh` with the same name.
+
+## Following Along from Your Phone
+
+The same `caminofix` session, mid-fix, viewed from the Claude app on a phone:
+
+![Claude app on a phone showing the caminofix session diagnosing the Camino Francés bug, having found the mismatched distance, difficulty, and description copied from the Camino Portugués section](/img/blog/2026/07/claude-remote-control-phone.png)
+
+You can read along and even type feedback in the "Queue feedback" box while Claude keeps working — no need to be at the keyboard where the session started.
+
+## Learn More
+
+- [Claude Code Remote Control docs](https://code.claude.com/docs/en/remote-control)
+- [Introducing coder.ddev.com: DDEV in the Cloud](coder-ddev-com-announcement.md)
+- [github.com/ddev/coder-ddev](https://github.com/ddev/coder-ddev) — templates and source for the freeform, drupal-core, and drupal-contrib templates
+
+If you have questions, reach out in any of the [support channels](https://docs.ddev.com/en/stable/users/support/).
+
+Follow our [blog](https://ddev.com/blog/), [Bluesky](https://bsky.app/profile/ddev.bsky.social), [LinkedIn](https://www.linkedin.com/company/ddev-foundation), [Mastodon](https://fosstodon.org/@ddev), and join us on [Discord](/s/discord). Sign up for the [monthly newsletter](/newsletter).
+
+---
+
+_This article was edited and refined with assistance from Claude Code._