Using Claude Code from Anywhere

I've been using multiple instances of Claude Code and Codex CLI almost every day. But I've gotten frustrated enough to build something that solidifies my workflow. Before, it looked something like this:

• git worktree for parallel instances

• docker for sandboxing work and tooling

• tmux for automation and management of terminal emulator windows

• ssh to a cloud instance for managing work on-the-go.

But I was frustrated by a few things:

1. Parallelism tax. Even with automation, the setup/clean-up grind is tedious. Worktrees share the same git object store, so you still need to be careful with operations and cleanup. Managing claude in docker means that I need to mount files, move around secrets, and manage environment. Remote instances need to be synced.

2. Laptop-locked. SSH from mobile or an iPad will probably never be a good experience, especially with a long-running process like claude code. Laptops aren't made to be treated like servers.

Current solutions are good, but have some shortcomings.

1. Unsupervised agents (Codex Web / Claude Code GitHub Actions). Short feedback loops make Claude Code great. If it makes a wrong turn, you can interrupt and get it back on the right path. Codex Web and Claude Code GitHub Actions are powerful, but often times spend 15 minutes working on a technically correct, but wrong implementation of a feature. Or they get blocked on something that you could have fixed easily.

2. SSH into a VM. You become the platform team: images, secrets, logs, UI, lifecycle. Not a bad choice, but lots of work.

3. Desktop UI: Solves some of the terminal-bound issues: window management, worktree automation, syntax highlighting, patch management. However, still laptop bound.

So my new workflow:

Web UI → ephemeral sandbox per chat → live, interactive session → patch/PR

1. On-demand sandbox execution: Ephemeral, quick to boot, isolated jobs per task with code, tools, and AI agents.

2. Live, steerable session. Stdout/stderr stream in real time; I can interrupt/approve and keep the loop tight—same Claude Code behavior, just remote.

3. Chat Management. Automated branch-per-chat and pull-request creation. Persistence for chats and code changes that isn't in your $HOME folder.

I put up an early version on standard-input.com. Let me know what you think. I'll buy you a coffee if you break out of the sandbox. dangerously-skip-permissions has been renamed to vibe.