What developers want from remote and background agent sessions

Research note for simstim. Researched on 15 October 2026.

This note asks what developers want when a coding agent runs somewhere other than the laptop in front of them, and what hurts today. It covers setup, persistence, fidelity over SSH, mosh and tmux, notifications, cost, lock-in, and the features that vendors keep behind an account or a paid plan. Amp UX and Orbs already covers Amp and its community, so this note only links to it.

The rules for the note:

• Every source is in the source table with its date, the date I read it, a link and its need codes. In the text, “S12” means row 12 of that table.
• UNVERIFIED marks a claim that I could not confirm from a primary source.
• Counts come first. Quotes are short, linked, and only illustrate a count.
• Reddit text and scores come from an archive copy, not the live page (see Method). Each Reddit claim is therefore UNVERIFIED against reddit.com itself.

Summary

1. Reach comes first. The two most common needs are to reach a session from a phone (40 sources) and to run it on a machine the developer owns (37 sources). Together they appear in 55 of the 132 sources that speak for developers, on 21 GitHub items with 2,715 reactions. The largest single requests are “remote development in the Codex desktop app” (876 reactions, S37) and “Codex remote control from the phone” (544 reactions, S38). People ask to reach their own machine and tools, not a vendor sandbox.
2. Fidelity carries the most reactions. Rendering, scrollback, keys, clipboard and image paste appear in 40 sources and 32 GitHub items with 3,937 reactions. The four most-reacted Claude Code rendering and scroll bugs alone hold 2,315 reactions (S1 to S4). In 2026 both Claude Code (April) and Codex (September) moved to a full-screen view by default. Users pushed back because it breaks native scrollback and copy (S6, S7, S47, S48: 8 of 10 reactions on the Codex announcement are thumbs down).
3. The DIY stack is still the default answer. tmux, mosh or zellij come up in 37 of the 63 Hacker News and Reddit threads I read, and Tailscale in 24. A typical guide joins 3 to 5 tools in 3 to 7 steps (S110, S134, S135, S93). Each tool loses something: mosh has had no scrollback since 2012 (280 reactions, still open, S75) and drops OSC 52 (S76). tmux has no kitty keyboard protocol as of October 2026 (S77, S78) and blocks agent notifications unless they are wrapped (S10).
4. Vendor remote features are welcome, but fragile and locked. Claude Code Remote Control drew 544 points on Hacker News (S79). Its top bugs are about dropped and idle-killed connections (195 reactions, S15, S16). Codex remote needs the ChatGPT desktop app awake on macOS or Windows, and does not support Linux hosts (S140, S40). Remote Control sends all traffic through the Anthropic API and needs a paid plan (S137). Codex remote uses a “secure relay layer” and a signed-in ChatGPT account; its docs do not say whose servers run the relay (S140).
5. Lock-in and cost are the angriest topics. Google’s March 2026 limits on Gemini CLI drew 1,035 thumbs down (S68). Its May 2026 move of consumer users to the closed Antigravity CLI drew 300 thumbs down (S69). The repo for the new CLI has no source code (S70). Anthropic’s legal action against OpenCode drew 483 points (S99). Claude Max usage limits drew 726 reactions and 1,499 comments (S32). Open-source tools that run several agents side by side hold about 132,000 GitHub stars between them (S144 to S150).
6. The bottleneck moves to the human. Parallel agents appear in 18 sources, notifications in 13 and an at-a-glance status in 4. The creator of Claude Code numbers five terminal tabs and relies on system notifications to know which one needs input (S128). A tmux dashboard that shows agent state got 691 points on r/ClaudeAI (S117). Agent notifications often fail inside tmux and zellij (S10, S61).
7. Setup breaks in the same places. These are: logging an agent in on a headless box (3 issues, 245 reactions, S20, S43, S63); the agent dying when SSH drops without tmux (S14, S134); cloud sandboxes that lack the developer’s own tools (S81, S24); and phone keyboards that cannot send agent keys (S111, S85, S135). No source measured setup time.
8. Phone control, cloud sessions and cloud agents all sit behind a vendor plan. Claude Remote Control rejects API keys and Bedrock (S137; S19 has 135 reactions asking for Bedrock). Claude cloud sessions need a claude.ai plan and GitHub to push (S139). Cursor Cloud Agents need the Premium plan or higher (S141). Anthropic’s terms forbid third-party tools from routing requests through a Pro or Max plan, or from handling Claude.ai credentials (S138). Free, open-source alternatives are popular: Happy (24,155 stars), Paseo (20,967) and CloudCLI (14,106).
9. Some needs are rare. Sharing a live session (0 sources), snapshots (1) and secrets handling (3) are rare in this evidence. Voice input (5) matters only on phones.
10. For simstim: most of the top needs are already in the v1 and v2 build: own host, survive sleep, byte-exact fidelity, image paste, status, worktrees, reboot restore and ports. The gaps with the most demand are: a phone path that needs no new client, alerts that reach a phone without a relay, a “who needs me” jump across hosts, agent login checks at host setup, and “continue when my usage limit resets”. See What this means for simstim.

Method

Where the sources come from

How I coded the needs

• I fixed 27 need codes (see Need codes). I refined them from the evidence: multi-device, status and voice were added after reading, and own-env was split from own-host.
• An issue or post got a code when its title or body asks for that need, or complains that it is missing.
• A Hacker News or Reddit thread got a code when at least two comments raise the need. I found candidates with a keyword pass over all comments, then read the matching comments. The keyword counts and the coding script are kept outside git.
• Voice sources are where developers speak: GitHub issues, discussions and pull requests, HN and Reddit threads, posts by developers on X, blogs and talks. Vendor docs, vendor posts and tool repos are in the table, but the ranking does not count them as demand.
• Reactions are the total reactions on a GitHub item when I read it. For a vendor announcement in GitHub Discussions, I count only its thumbs-down reactions, because they are the users’ answer to the announcement.

Limits

• I chose the search terms, so the counts show what is common within the topic of remote and background sessions. They do not show what share of all developers care.
• Reactions measure how strongly people feel better than source counts do. A source count of 5 with 1,000 reactions can matter more than a count of 15 with none.
• GitHub search caps each query, and many Claude Code issues are closed as duplicates, so reaction totals undercount.

Need codes

Needs ranked

Ranked by the number of voice sources, then by GitHub reactions. The last column also counts tool repos and vendor pages.

The same needs, grouped

A source counts once per group, even if it has several codes in the group.

What the ranking shows

• Two kinds of evidence point in different directions. Forums talk about reach, cost and lock-in. GitHub reactions pile up on fidelity. Fidelity has only 2 HN or Reddit sources for render, but 2,655 reactions. People do not start a forum thread about flicker. They add a thumbs-up to the bug.
• Persistence is mostly a “how”, not a “what”. sleep (11) and reconnect (14) are usually the reason people reach for tmux, mosh or a vendor relay. They rarely ask for them by name.
• Sandboxing is talked about but not requested. It has 15 forum sources but no GitHub item in this sample. It is a concern raised about other features (“run it isolated”), not a feature request on its own.

Issue volume by topic

How many issues have the word in their title, in each agent’s repo. This is a rough measure of how often each thing breaks. The counts include closed and duplicate issues, and some are unrelated (for example ssh matches Git over SSH). GitHub search, 15 October 2026.

Sentiment by tool

Each verdict is mine and comes from the counts and sources listed with it.

Claude Code (CLI)

Mixed. People love the agent and fight the terminal.

• Rendering and scrolling are the most-reacted complaints in the whole sample. #3648 (836 reactions), #826 (822), #769 (336) and #1913 (321) total 2,315 reactions.
• A third-party flicker fix reached 192 points on Hacker News. One reply notes it “breaks Ghostty’s native scrollback” (comment).
• The April 2026 full-screen renderer fixed flicker but “completely destroys native terminal scrollback” (#42670, #41965). It also broke tmux copy mode (#60185).
• Inside tmux there are separate bugs: rendering corruption (#29937, 70 reactions), scrollback lag (#4851, 97), and notifications that need DCS wrapping (#19976, 26).
• Usage limits are the biggest cost complaint (#16157, 726 reactions and 1,499 comments; #13354, 215).
• On the positive side, a commenter writes that “no other agentic coding tool comes close” (comment). Its creator runs five sessions at once in numbered tabs (X).

Claude Code Remote Control

Wanted, but seen as fragile and locked.

• The launch reached 544 points and 297 comments on Hacker News. In that thread, 63 comments talk about phones and 33 about tmux, mosh or zellij.
• One commenter called it an “extremely clunky and buggy prerelease” (comment). Others went back to Termux, or to self-hosted hapi with Tailscale (comment). One disliked that the Android app needs a GitHub connection (comment).
• Its top bugs are connection bugs: no automatic reconnect (#34255, 109 reactions) and sessions that die after about 20 minutes idle (#32982, 86). A small HN thread is titled “Anyone else having a terrible experience with Claude Code’s remote control?” (HN).
• Users ask for it on Bedrock (#28795, 135 reactions), on headless servers (#30447, 46) and as a service that survives a reboot (#88166).
• The docs say it needs a Pro, Max, Team or Enterprise plan. API keys and third-party providers are not supported, and all traffic goes through the Anthropic API (docs).

Claude Code on the web (cloud sessions)

Mixed. Good for quick tasks from a phone, weak for real environments.

• The launch reached 578 points on Hacker News and 346 on r/ClaudeAI. A follow-up post, “I’ve been loving Claude Code on the web”, reached 161 points (HN).
• The environment is the most common complaint. One commenter wrote “it doesn’t have support for devcontainers” (comment). Another said their tools were missing and “the LLM spends 10 minutes just trying to get the environment set up… On every interaction” (comment). A third said “yarn install just hangs” (comment). Several repositories per session is an open request with 99 reactions (#23627).
• Some find the clone, change, test and PR loop “too slow of a loop” for anything but small tasks (comment).
• On Reddit, a top comment asked for the opposite of a cloud copy: “remotely run/continue my claude code sessions against the repos already on my PC” (r/ClaudeAI).
• The docs require a claude.ai plan, and GitHub for cloning and pushing. A setup script is cached only if it finishes in about five minutes (docs).

Codex CLI

Positive on speed and stability. Mixed on terminal behaviour since the switch to full screen.

• Users compare its resource use with Claude Code’s. One wrote: “I can run 5-10 codex sessions and my system holds up fine … but 8 CC instances would grind things to a halt” (comment).
• Peter Steinberger reports no flicker, but says it “loses” lines when scrolling quickly (blog). Scrolling inside zellij truncated output (#2558, 135 reactions). Native scroll in tmux broke after an update (#48315).
• The September 2026 full-screen default (announcement) got 8 thumbs down out of 10 reactions. An issue asks to keep native terminal behaviour by default (#48398).
• A built-in --worktree --tmux was asked for with 129 reactions (#12862). A background daemon that starts by itself drew 198 reactions asking to make it opt-in (#48195).

Codex cloud and Codex remote

High demand, uneven delivery.

• Codex cloud is the web agent that “stuck” for Peter Steinberger (blog). Simon Willison uses it for riskier asynchronous tasks, often started from his phone (blog).
• The remote-control request explains why people wanted more: “I cannot set up the environment from the mobile app”, “I prefer using my desktop environment” (discussion #9200, 260 reactions).
• Demand for remote work on one’s own machine is the largest in the sample: #10450 (876 reactions) and #9224 (544).
• The shipped remote has complaints. Two r/codex threads report constant disconnects and failed connections (1, 2). A reply in the first thread complains of a “session is active on another device” error after moving from the desktop to the phone. Resuming a thread can fail with “already has an active writer” (#37403, 48 reactions).
• The docs say the host must run the ChatGPT desktop app on macOS or Windows, and stay awake and online. Linux hosts are not listed (docs). Users ask for headless Linux hosts (#23200, 69 reactions).
• One user on r/codex says their cloud workspace restarted and lost its work (r/codex). A reply prefers “my existing VM setup in my home lab”. What “Dot” in that thread refers to is UNVERIFIED.

opencode

Positive on openness. Mixed on security and terminal fidelity.

• It is very popular: 213,734 GitHub stars and a 1,274-point launch thread (HN). Version 2.0 reached 703 points on 14 October 2026 (HN).
• Security worries are recurring: an unauthenticated remote code execution bug (432 points, HN) and “Annoying and alarming things about OpenCode” (420 points, HN).
• Lock-in hit it directly. After a lawyers’ letter, opencode stopped loading the Claude Max plugin (X; 483 points on HN).
• Its remote story is opencode serve plus a tunnel. Users warn that quick tunnels are “ephemeral” and that “Tailscale + SSH + tmux is the most reliable setup” (r/opencodeCLI).
• Its terminal issues match the others: clipboard (#4283, 134 reactions), Shift+Enter (#1505, 104), and notifications under tmux or zellij (#29099). Users also ask for SSH from the desktop app (#7790, 116) and a mobile version (#10288, 103).

Gemini CLI

Negative, because of churn and lock-in.

• The launch was the biggest thread in the sample: 1,428 points (HN). The free tier was a large part of the draw.
• In March 2026 Google added abuse detection for “using Gemini CLI oAuth with third-party software”, and limited free users to Flash models. Of 1,396 reactions, 1,035 were thumbs down (discussion #22970).
• In May 2026 Google announced that Gemini CLI would stop serving Pro, Ultra and free users on 18 June 2026, and moved them to Antigravity CLI (Google blog). The announcement drew 300 thumbs down out of 374 reactions (discussion #27274) and 406 points on HN. One commenter wrote: “google can kill your account for using an unsupported harness” (comment).
• The Antigravity CLI repo holds a README, a changelog and examples, with no source and no licence (repo). Gemini CLI itself stays Apache-2.0 and is still updated.
• Remote pains were the usual ones: login over SSH (#1437, 64 reactions) and flicker in tmux (#22004).

aider

Quiet. Respected for control, but slowing down.

• The last release is v0.86.0, from 9 August 2025 (releases). A community fork, Aider-CE, became “official” in November 2025 (HN). One commenter there calls aider their “Goldilocks zone” for reviewing each line.
• It has very few remote complaints: 1 issue with “tmux” in the title and 3 with “ssh”. It has had notifications since March 2025 (docs). A request to run several instances in parallel dates from 2023 (#302).
• My reading is that its line-by-line interface suits tmux well, and few people run it as a background agent. This is an inference, not a count.

Amp

Mixed. Covered in detail in Amp UX and Orbs.

• In short, the Orbs thread (116 points, HN) splits between “the best $20/month” and “a thin wrapper over a remote virtual machine”. One commenter asks for plain OpenSSH. Price is the most common complaint in that note.

Cursor background agents (Cloud Agents)

Negative to mixed.

• When Background Agent reached general availability with Cursor 1.0, r/cursor was sceptical (thread). One reply said it could not be used in privacy mode. A May 2026 post saying it “actually works now” drew replies that doubt it (thread).
• On Hacker News, one user said Cursor’s agents “would make entirely new mistakes” that the local IDE did not (comment).
• In June 2026, installing the Cursor iOS app switched one user’s account to a softer privacy mode, whose terms allow storing code “for Background Agents”. The post reached 249 points (HN). Replies say the mobile app “cannot start an agent session on your computer” and that cloud agents are “significantly more limiting” (1, 2).
• Cursor’s docs say Cloud Agents need the Premium plan or higher (pricing). They are the only feature for which Cursor keeps encrypted copies of the repository while the agent runs (privacy docs).

tmux, zellij and mosh setups

Trusted and robust, but fiddly and lossy.

• This is the default answer. tmux comes up in 35 of the 63 HN and Reddit threads I read (178 comments), Tailscale in 24, mosh in 17, Termux in 14, Termius in 9 and zellij in 8. The r/tmux subreddit complained that it had become “just claude code tmux plugins” (110 points, thread).
• People trust it more than vendor relays. One HN commenter runs “the agent in tmux in a colo” and uses Remote Control only on the go (comment). Another, under a mobile-agent launch, asked: “So you’ve reinvented SSH+screen except slower and much less flexible?” (comment).
• What it loses:
  • Scrollback under mosh: “Mosh paints the screen, meaning no native scrollback” (comment). The mosh issue is open since 2012 with 280 reactions (#122). A Rust port with scrollback appeared on 14 October 2026 (HN).
  • Clipboard under mosh: no OSC 52 (#637). One user said this “sent me back to tmux” (comment). Over mosh, repeated copies of the same text are deduplicated (Claude Code #89030).
  • Keys under tmux: the kitty keyboard pull request was closed unmerged (#4912). The roadmap lists kitty keys as “potentially” 3.9, and save and restore as “probably 4.0” (#5406). A newer kitty keyboard pull request was still open on 15 October 2026 (#5615, S156). Shift+Enter needs extended keys inside tmux (Codex #21699).
  • Phones: “tmux keybindings can be awkward on a phone keyboard” (Twingate). Users remap Shift+Tab by hand (r/ClaudeAI). They also report that “Mosh has lots of visual artifacts” (same thread).
  • Reboots: “Such a pain to get back to before a reboot” (comment).

Setup pains

The usual stack

These are the parts a developer joins together to get a persistent remote agent today. The count is how many of the 63 HN and Reddit threads name each one.

Steps and time

• Time: no source measured setup time. One HN commenter guessed “a couple of hours” when calling a paid relay “expensive” (comment). That is one claim, not a measure.
• Repeatability: the Reddit author built a CLI because sharing the setup with a team “was challenging” (S110). Codeman (176 points on r/selfhosted) and Herdr (44,140 stars) exist to package the same job.

What breaks, with evidence

Paywalled and account-locked features

These are features that developers say they want, and that a vendor keeps behind a paid plan, a vendor account, a vendor relay or a vendor platform.

The pattern is clear. Each vendor ships phone access and background sessions for its own agent, through its own relay, on its own paid account. The open-source tools that do the same job for any agent are among the fastest-growing repos in this space: Herdr (44,140 stars since March 2026), Happy (24,155), Paseo (20,967), Superset (15,219) and CloudCLI (14,106).

What this means for simstim

The table maps the top needs to what simstim does today and to candidate features. Demand is the number of voice sources, then the GitHub reactions. “Built” refers to the v1 and v2 work in the README and the plan.

Needs not to build, from this evidence:

• Sharing and watching (0 voice sources), snapshots (1) and secrets management (3) have little demand here. Secrets also conflict with simstim’s rule of storing no secrets.
• Voice input (5) belongs to the phone’s keyboard, not to simstim.
• A web or phone UI would meet the top need, but the evidence also warns against it. The sample has an unauthenticated remote code execution bug in opencode’s server (S102), a widely shared critique of opencode’s security (S103), and a mobile app that changed a user’s privacy setting (S108). The plan already rules a web or phone UI out. The phone path above reaches the same users through plain SSH.

Unverified and open points

• Reddit (UNVERIFIED against the live site): all Reddit text and scores come from the Arctic Shift archive, not from reddit.com, which needs a login. The live pages may differ. Scores can be lower than today’s. Two threads I fetched had been removed by moderators, and one more had nothing on topic. None of the three is used.
• X: I read X posts through X’s oEmbed endpoint, which returns the post text. I could not see replies or view counts.
• Codex “Dot” and “Dots” (UNVERIFIED): the r/codex thread (S123) uses the word for a cloud workspace. I could not confirm what the product is.
• Codex mobile plans (UNVERIFIED): third-party sites say the preview reached all plans, including Free. OpenAI’s page does not say.
• Omnara’s price (UNVERIFIED): taken from a commenter, not from Omnara.
• Claude Code full-screen opt-out (UNVERIFIED): I did not confirm which setting turns the full-screen renderer off in the current version.
• Setup time: no source measured it.
• Talk date (UNVERIFIED): the talk page names AI Engineer World’s Fair 2025, not the month. I give June 2025 from secondary sources.
• Usage terms: Anthropic says the advertised Pro and Max limits “assume ordinary, individual usage” (S138). Whether many parallel, always-on sessions fit that is for Anthropic to say, not this note.
• Selection bias: I chose the queries. A different set of queries would change the counts, but probably not the order of the top five, because those lead on both source counts and reactions.

Sources

All sources were read on 15 October 2026. Reactions and comment counts are as of that day. “Vendor” rows (docs and vendor posts) and “Repo” rows are not counted as demand in the ranking.