WeWorkBuddy

Show HN: Loop – your coding agents, from your phone

Loop is a mobile-first companion workspace for the coding harnesses you already run. It aggregates results from your harnesses into a continuous feed that is easy to navigate and organize from your phone. I spent several months holding my newborn in one hand and trying to talk to agents one-handed on my phone. Every mobile UI is still based around chat, and it doesn’t scale on mobile, let alone one-handed! So I built Loop: a feed of the work your coding agents do. It’s built around agent results

Read original source
Source page screenshot: Show HN: Loop – your coding agents, from your phone
Source page screenshot · news.ycombinator.com

Source record

Recorded metrics

points · 1 votes
2026-11-08 17:45:21.457Z
cumulative since publication

Research analysis

Project record

Repository: j-asefa/loop. Source account: Loop is a mobile-first companion workspace for the coding harnesses you already run. It aggregates results from your harnesses into a continuous feed that is easy to navigate and organize from your phone. I spent several months holding my newborn in one hand and trying to talk to agents one-handed on my phone. Every mobile UI is still based around chat, and it doesn’t scale on mobile, let alone one-handed! So I built Loop: a feed of the work your coding agents do. It’s built around agent results

Observed adoption & comparisons

Source votes: 1 votes (Nov 8, 2026 UTC; cumulative since publication) Recent records to compare: “Show HN: Record, branch, and compare command runs in stdlib-only Python” (Show HN, Nov 8, 2026); “meta/astryx” (GitHub Trending, Nov 8, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.

Adoption decision

Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.

Unverified requirements

Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.

Next test

Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.