HN user

boudra

172 karma
Posts18
Comments22
View on HN
github.com 1mo ago

Port React Compiler to Rust

boudra
124pts118
paseo.sh 1mo ago

I was wrong about Electron

boudra
6pts3
github.com 3mo ago

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

boudra
6pts1
github.com 3mo ago

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

boudra
14pts0
news.ycombinator.com 3mo ago

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

boudra
5pts1
github.com 4mo ago

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

boudra
5pts2
blank.page 8mo ago

Our tools are failing us

boudra
3pts1
moboudra.com 10mo ago

Your business philosophy is just what you can tolerate doing

boudra
1pts0
konbert.com 1y ago

Why CSV is still king

boudra
122pts144
moboudra.com 3y ago

Procrastination in Software Development

boudra
2pts0
sanerjobs.com 6y ago

Show HN: Jobs ranked by a work-life balance score

boudra
1pts0
moboudra.com 6y ago

Writing as a Learning Medium

boudra
1pts0
www.indiehackers.com 6y ago

Getting better at coming up with viable business ideas

boudra
1pts0
moboudra.com 6y ago

We need to move away from the 40-hour week

boudra
1pts0
moboudra.com 7y ago

Bootstrapping a Side Project to $900/mo Revenue While Working a Full-Time Job

boudra
5pts0
ecoalternatives.to 7y ago

Show HN: Find Eco-friendly alternatives to Products You Use Everyday

boudra
38pts41
moboudra.com 7y ago

Show HN: Whistle, a different way to build interactive web apps in Elixir

boudra
7pts0
sqlify.io 9y ago

Show HN: A Usable CSV and JSON to SQL Converter in Elm and Phoenix

boudra
8pts2

Maintainer here. From the ones you listed, I only have a comparison page to Conductor (see others in the menu): https://paseo.sh/docs/alternatives/conductor

We're all converging on similar interfaces, but there are differences. The main ones right now are:

- FOSS

- Local-first and self-hostable

- No telemetry or forced login

- macOS, Windows and Linux

- Available as a desktop app, web app, native mobile app and PWA

- Daemon/client architecture, run the daemon anywhere you want and connect with any client

- Support for popular agents like Claude Code, Codex, OpenCode and Pi. Plus native ACP support which allows it to support most other agents

---

Paseo supports terminal multiplexing, like Cmux, but I'd consider them completely different product categories.

Claude Code (via the subscription) will continue working under Paseo but it will consume a different pool of credits, which depending on your sub you get different amounts. Practically speaking you will be able to use only a fraction of your usage in Paseo, this applies to any programmatic usage of Claude Code.

This might help: https://support.claude.com/en/articles/15036540-use-the-clau...

Paseo has a terminal if you want to keep using the TUI inside of it, works on mobile and desktop.

I will keep supporting the Claude Code harness in Paseo, as many users are using it via direct API usage and sometimes even with Chinese models.

Thanks. Yes, team of one right now.

I think there's still a lot to do and it feels like I'm only scratching the surface of what's possible in the local layer, so matching what Cursor does is not the end game for me.

I want to keep the core open and local-first, the business, when it comes, will be around the convenience/team/enterprise layer.

Right now I am letting real usage guide me by paying attention to what teams using Paseo need.

Maintainer here. I get the concern, but that has not been my experience.

I don't think of the mobile side as a way to keep working on your phone on top of your full working day, although I will admit it can be used that way.

It is more about being able to step away from the desk without losing access to the work. Let's say you spend 6 hours at your desk, what if you could spend 2 of those hours walking instead?

To me, it has been valuable for steering long running agents, brainstorming ideas or triaging PRs/issues while taking a walk.

Fun fact, Paseo means "stroll" in Spanish, which is where the name came from.

Maintainer here. Yes, the web app is a static Expo export, so the simplest self-host path is to build packages/app and serve the generated dist/ with any static HTTP server. The daemon itself is published to npm as `@getpaseo/cli`.

Docs for this are currently missing, and I should probably package all of this in a Docker image. I'll do that today!