A Hotel Wi-Fi Drop During a Release Fix

The release fix is small: repair a pagination bug, add a regression test, and leave a clean diff for review. The hotel connection makes it complicated. Browsing works, but a long Claude Code response stalls. Reconnecting brings back the terminal without making it obvious whether the previous operation finished.

This is a worked field-test scenario, not a measured hotel-network benchmark. It follows that release task through three connection failures and compares what survives. The useful result is a recovery procedure you can repeat before trusting an evening’s work to an unfamiliar network.

The release-fix test at the hotel desk

Start with a clean working tree or a checkpoint commit. Ask Claude Code to inspect the pagination code, propose a narrow fix, run the relevant test, and report the changed files. Keep the task bounded enough that you can independently verify its result.

Run the exercise first on your laptop, then in a remote development environment with Claude Code inside tmux. Use a repository and machine you control. Deliberately disconnect Wi-Fi while a response is streaming, reconnect after a short interruption, and inspect the terminal, working tree, and test output.

Repeat once while a test command is running. Finally, disconnect your SSH client from the remote setup. These failures test different things: the model connection, a local subprocess, and your access to a remote terminal.

A dropped response leaves an uncertain boundary

When a response stops arriving, the last visible line is not proof that the underlying operation stopped there. A request may have reached the provider before your connection failed. A tool command may also have started before its output disappeared.

That uncertainty makes an immediate “try again” risky. Repeating a read is usually harmless; repeating a migration, deployment, or other side effect can matter. For the pagination exercise, inspect the diff and running processes before asking for another attempt. Run the focused test yourself if its completion is unclear.

If Claude Code exits, use its conversation recovery options, such as claude --continue for the most recent conversation in that directory or claude --resume to select one. Conversation recovery restores useful context; it does not establish whether every interrupted action completed.

A remote tmux session survives the missing terminal

The remote setup addresses a different failure. Start tmux on the development host, launch Claude Code there, and work through SSH. If the hotel connection drops, the remote terminal and its processes can keep running. Reconnect and attach with tmux attach.

The important boundary is where Claude Code runs. A local tmux session protects against closing a terminal, but the laptop still uses the hotel’s connection to reach the model service. A remote session moves that connection to the development host.

This does not guarantee uninterrupted work. The remote host can lose connectivity, a request can time out, and an agent can pause for input. It does give you a stable place to return to, with the terminal output and repository available for inspection.

The recovery checklist beside the laptop

• Complete the hotel’s captive-portal login before opening a long session.
• Keep a mobile hotspot available for reconnecting, subject to your data allowance.
• Write the task, verification command, and remaining work into a short repository note.
• Checkpoint completed changes after reviewing the diff and test results.
• After an interruption, inspect state before repeating any operation with side effects.

The setup to use before the next release deadline

For long sessions on unreliable hotel Wi-Fi, my recommendation is Claude Code on a remote development host inside tmux, with small checkpoints and explicit verification after every interruption. Test that recovery path before the deadline. Keep local execution for work you can comfortably pause and inspect.

For the model-access layer, I recommend RelayVano if pay-as-you-go access fits your workflow. It works with Claude Code, but a relay cannot preserve a broken hotel connection or replace terminal persistence. Sign up for RelayVano, verify its current Claude Code configuration, and run this disconnect exercise before starting the release fix.