Maintainer here. Great points! Paseo already supports embedding images in the chat, but no MDX or chart rendering yet. I have been meaning to add Mermaid support but haven't got around to it yet.
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.
I do sometimes wish I can monitor my agent on the go and keep drip-feeding it tasks. Because I do genuinely need to read how the last task went before I decide whether to correct or to move to the next task.
Cool project. I don’t think people will get the mobile version until they need it but when they do it’s a mind bending, life changing realization. I built my own IDE to have it on my phone because I have small kids and it is truly life changing. I get to spend way more time with my kids while still getting work done.
If you’re open to collaborating I’d be happy to share what I’ve learned an see if we can share resources or lessons.
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!
I am in love with Paseo. I really want to express my gratitude for building this and saving me so much time and energy. I have been a heavy user of conductor.build before switching off completely to Paseo.
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.
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.
very nice and well executed product for what i assume is a small team! (of one?)
i guess the obvious question is... if its FOSS and local only, whats the business game plan? you've impressed me that you can ship, but you've basically just matched what eg devin desktop and cursor now do. what next?
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.
I'm the maintainer of Paseo. This is correct, I do not use the word beautiful anywhere.
I personally do think it's beautiful (obviously), but I would not use that word in marketing materials, I'd rather people judge from seeing the screenshots or trying the product.
