HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
getpaseo
paseo
TypeScript2026–2026
getpaseo / paseo

paseo

Orchestrate multiple coding agents from desktop and mobile

9Distinct people
14Mentions
1Explicit recommenders
24KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Orchestrate multiple coding agents from desktop and mobile

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Gotta say: I love how mobile app works on my 13 years old Nexus 7 (2GB RAM). It was the sole reason I choose it, actually - other PWAs are too much for the little guy. I am…

arvigeus used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

Goodbye Claude, hello Pi direct repository linkDebated

Developers are divided between migrating to third-party harnesses like Pi for their customizability and control, versus staying with native tools like Claude Code due to concerns about stability, security, and vendor restrictions. The strongest disagreement centers on whether the flexibility of open-source harnesses outweighs the operational risks of manual configuration and potential Terms of Service violations.

493 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by month14 dated mentions

Observed mentions: 2026-03-16 10:29:55 UTC to 2026-10-31 12:10:13 UTC.

012342026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 4 mentions; 4 submissions, 0 commentsMar 20262026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJun 20262026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC440
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC101
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC211
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC101
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC202
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC101
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC303

What Hacker News says

14 sources
Paseo is Apache 2.0 (vs T3 MIT). Haven't tried T3 and can't find docs for it to get more insight without installing. Re: changes: Paseo's plugin system is very, very good. Some limitations since not all of the internals are accessible via plugin system, but allows building very custom UIs. So this may be a point of delta with T3. But I have some coworkers that have gone absolutely HAM with the plugins and built entirely custom workspaces (wild). For me, what I have found most useful about Paseo is the multi-platform, multi-agent setup because this has given my agent teams much, much more autonomy that I feel like I can trust (after weeks of watching them work). The agent profile system looks too simple at first blush, but actually, that simplicity and semi-structured dynamic nature of the sub-agents is what makes it powerful. Might t
Read the rest
ry T3 for a week and see; thanks for sharing! EDIT: T3 has no docs site yet, but sifting through docs, this was interesting: https://github.com/pingdotgg/t3code/blob/main/docs/user/remo... > Each T3 Connect account can link up to 3 machines. Phones and browsers do not count. A paid T3 Chat plan raises the limit to 10 machines with Pro, or 100 with Premier. Paseo has no paid features; only if you want to use the hosted hub gateway (entry point for Slack, Discord, GH). T3 Connect looks to be the equivalent of the Paseo Relay: https://paseo.sh/docs/connectivity#paseo-relay which has no limits (Herdr's ipml is better, though; Paseo currently cannot manage individual connections which would make it SICK for team collab. See: https://github.com/getpaseo/paseo/discussions/6896)
In Anthropic to receive high 'junk' rating from credit agencies following IPO
How does this compare to https://github.com/pingdotgg/t3code or https://github.com/getpaseo/paseo? Is there a good resource indexing all the coding agent tools / harnesses? Every awesome list I've found so far seems very incomplete, but I'm sure its impossible to keep up. My daily drivers are still: - exe.dev + Shelley + terminal multiplexer (https://zmx.sh/ or tmux) + `codex` CLI - Conductor.build I would love an open source solution with nice desktop / web / mobile / remote options and notifications, but seems like it could be a while before things settle down and the "winners" emerge?
In Show HN: Proliferate- open-source, self-hostable Codex for any coding agent
I prefer Paseo https://github.com/getpaseo/paseo, mainly because I have specific preferences for different harness + model combinations. For example, I like using ChatGPT models via pi, and GLM via Claude Code. If you’re happy with OpenCode as the harness, OpenChamber is great. But if you prefer using different harnesses under the hood, Paseo is a better fit. I installed it on my homelab and can access the same sessions from my MacBook or iPhone at any time. Been really nice to use so far.
In OpenChamber: An Agentic Development Environment
boudra·Mar 30, 2026Submission

Show HN: Paseo, an open source environment for coding agents

Hey HN, I'm Mo. I've been building Paseo, an open source environment for running Claude Code, Codex, and OpenCode across desktop, mobile, web, and CLI. It started last September as a push-to-talk voice interface for Claude Code. I wanted to talk to an agent while going on walks. Then I wanted to see what it was doing. Then text it when I couldn't talk. Then review diffs, run multiple agents, and manage work across machines. After a lot of iteration, it turned into a broader environment. The basic model is: - A daemon runs on your machine (MacBook, desktop, VPS, etc.). - Clients connect to it over WebSocket. - There's an optional built-in E2EE relay for easy remote/mobile access. A few things I care about: - It works with the first-party agent CLIs, not by calling inference APIs directly or extracting OAuth tokens. - It's multi-
Read the rest
provider instead of locking you to one model. - It supports local voice, git worktrees, split panes, terminals, and running agents across different hosts. - No forced account, no telemetry, no tracking. The daemon is written in TypeScript. The app uses Expo for native mobile and web, and the desktop app is Electron. I actually started with Tauri and had to migrate due to platform specific problems. The relay is built on Cloudflare Durable Objects. I use Paseo every day, but one thing I’m increasingly excited about is the CLI. It's turning into a primitive for more advanced orchestration, loops, and agent teams, which feels like a bigger direction than the app alone. Repo: https://github.com/getpaseo/paseo Homepage: https://paseo.sh/ Discord: https://discord.gg/jz8T2uahpH Happy to answer questions about the product, architecture, or where I think this is going.
6 points · Open discussion
boudra·Mar 26, 2026Submission

Show HN: Paseo – Open-source coding agent interface (desktop, mobile, CLI)

Hey HN, I'm Mo. I'm building Paseo, a multi-platform interface for running Claude Code, Codex and OpenCode. The daemon runs on any machine (your Macbook, a VPS, whatever) and clients (web, mobile, desktop, CLI) connect over WebSocket (there's a built-in E2EE relay for convenience, but you can opt-out). I started working on Paseo last September as a push-to-talk voice interface for Claude Code. I wanted to bounce ideas hands-free while going on walks, after a while I wanted to see what the agent was doing, then I wanted to text it when I couldn't talk, then I wanted to see diffs and run multiple agents. I kept fixing rough edges and adding features, and slowly it became what it is today. What it does: - Run multiple providers through the same UI - Works on macOS, Linux, Windows, iOS, Android, and web - Manage agents in different machines f
Read the rest
rom the same UI - E2EE Relay for mobile connectivity - Local voice chat and dictation (NVIDIA Parakeet + Kokoro + Sherpa ONNX) - Split panes to work with agents, files and terminals side by side - Git panel to review diffs and do common actions (commit, push, create PR etc.) - Git worktree management so agents don't step on each other - Docker-style CLI to run agents - No telemetry, no tracking, no login Paseo does not call inference APIs directly or extract your OAuth tokens. It wraps your first-party agent CLIs and runs them exactly as you would in your terminal. Your sessions, your system prompts, your tools, nothing is intercepted or modified. Stack: The daemon is written in Typescript. The app uses Expo and compiles to both native mobile apps and web. The desktop app is in Electron (I started with Tauri and had to migrate). Sharing the same codebase across different form factors was challenging but I'd say that with discipline it's doable an the result has been worth it, as most features I build automatically work in all clients. I did have to implement some platform specific stuff, especially around gestures, audio and scroll behavior. The relay is built on top of Cloudflare DO, so far it's holding up quite well. I love using the app, but I am even more excited about the possibilities of the CLI, as it become a primitive for more advanced agent orchestration, it has much better ergonomics than existing harnesses, and I'm already using it to experiment with loops and agent teams, although it's still new territory. How Paseo compares to similar apps: Anthropic and OpenAI already do some of what Paseo does (Claude Code Remote Control, Codex app, etc.), but with mixed quality and you're locked onto their models. Most other alternatives I know about found are either closed source or not flexible enough for my needs. The license is AGPL-3.0. The desktop app ships with a daemon so that's all you need. But you can also `npm install -g @getpaseo/cli` for headless mode and connect via any client. I mainly use Mac, so Linux and Windows has mostly been tested by a small group of early adopters. If you run into issues, I’d appreciate bug reports on GitHub! Repo: https://github.com/getpaseo/paseo Homepage: https://paseo.sh/ Discord: https://discord.gg/jz8T2uahpH Happy to answer questions about the product, architecture or whatever else! --- I resubmitted this post because I forgot to add the URL and it didn't allow me to add it later.
14 points · Open discussion
boudra·Mar 26, 2026Submission

Show HN: Paseo – Open-source coding agent interface (desktop, mobile, CLI)

Hey HN, I'm Mo. I'm building Paseo, a multi-platform interface for running Claude Code, Codex and OpenCode. The daemon runs on any machine (your Macbook, a VPS, whatever) and clients (web, mobile, desktop, CLI) connect over WebSocket (there's a built-in E2EE relay for convenience, but you can opt-out). I started working on Paseo last September as a push-to-talk voice interface for Claude Code. I wanted to bounce ideas hands-free while going on walks, after a while I wanted to see what the agent was doing, then I wanted to text it when I couldn't talk, then I wanted to see diffs and run multiple agents. I kept fixing rough edges and adding features, and slowly it became what it is today. What it does: - Run multiple providers through the same UI - Works on macOS, Linux, Windows, iOS, Android, and web - Manage agents in different machines f
Read the rest
rom the same UI - E2EE Relay for mobile connectivity - Local voice chat and dictation (NVIDIA Parakeet + Kokoro + Sherpa ONNX) - Split panes to work with agents, files and terminals side by side - Git panel to review diffs and do common actions (commit, push, create PR etc.) - Git worktree management so agents don't step on each other - Docker-style CLI to run agents - No telemetry, no tracking, no login Paseo does not call inference APIs directly or extract your OAuth tokens. It wraps your first-party agent CLIs and runs them exactly as you would in your terminal. Your sessions, your system prompts, your tools, nothing is intercepted or modified. Stack: The daemon is written in Typescript. The app uses Expo and compiles to both native mobile apps and web. The desktop app is in Electron (I started with Tauri and had to migrate). Sharing the same codebase across different form factors was challenging but I'd say that with discipline it's doable an the result has been worth it, as most features I build automatically work in all clients. I did have to implement some platform specific stuff, especially around gestures, audio and scroll behavior. The relay is built on top of Cloudflare DO, so far it's holding up quite well. I love using the app, but I am even more excited about the possibilities of the CLI, as it become a primitive for more advanced agent orchestration, it has much better ergonomics than existing harnesses, and I'm already using it to experiment with loops and agent teams, although it's still new territory. How Paseo compares to similar apps: Anthropic and OpenAI already do some of what Paseo does (Claude Code Remote Control, Codex app, etc.), but with mixed quality and you're locked onto their models. Most other alternatives I know about found are either closed source or not flexible enough for my needs. The license is AGPL-3.0. The desktop app ships with a daemon so that's all you need. But you can also `npm install -g @getpaseo/cli` for headless mode and connect via any client. I mainly use Mac, so Linux and Windows has mostly been tested by a small group of early adopters. If you run into issues, I’d appreciate bug reports on GitHub! Repo: https://github.com/getpaseo/paseo Homepage: https://paseo.sh/ Discord: https://discord.gg/jz8T2uahpH Happy to answer questions about the product, architecture or whatever else!
5 points · Open discussion
boudra·Mar 16, 2026Submission

Show HN: Paseo – Run coding agents from your phone, desktop, or terminal (FOSS)

Hey HN, I built Paseo because i kept SSHing into tmux from my phone to check on agents while on walks, it worked but the UX was rough. I started building a voice-only app for agents but after dogfooding and iterating for months I ended up with this. Both Anthropic and OpenAI are working on versions of this but I didn't like them and I didn't want to be locked into their respective models. Paseo takes a different approach: a daemon runs on your machine and you connect to it from any device. your code never leaves your machine. - Works with Claude Code, Codex, and OpenCode, just launches their CLIs and uses your subs - Voice mode for dictating tasks hands-free, not perfect but it works - Manage agents in isolated git worktrees, review diffs, ship from the app - Terminal support so you don't have to SSH separately - Connect to multiple machi
Read the rest
nes, see all your agents in one place. I run Paseo in a Hetzner VM for when my laptop is closed. - Optional E2E encrypted relay for remote access - iOS, Android, Mac, Windows, Linux, web, and CLI It’s free and open source (AGPL). No accounts, no tracking. The name means "stroll" in Spanish, which is basically the use case. github: https://github.com/getpaseo/paseo homepage: https://paseo.sh
5 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.