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?
So this is an alternative to using one coding agent with openrouter, changing the models between tasks? I am a neophite in these things, my ai use is more calling apis from scripts right now. Can somebody please explain the pros and cons (beyond to openrouter fees) of each?
This looks like something worth trying and I'm glad it's open source. I've been using https://github.com/openchamber/openchamber for a few months now and I'm pleased with its features. Their web based pwa and locally running cli is similar.
It's like people pulling their phones out while taking a piss standing, or having to pull their phones out when the traffic lights are red in a crossing.
Just, do one thing at a time, live a life.
Shipping code from your phone, whhhyy. Mates, this isn't a flex, it's depression.
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.
This seems extreme. Maybe I’m just optimistic but I think people can be intentional and present while also having the convenience and accessibility that something like paseo offers.
- If I’m on-call, it would be great to just take my iPad mini around with me instead of my heavy MacBook Pro.
- Sometimes I’m on the couch with my phone and want to query an agent with access to my computer’s file system.
Not to undercut the open source nature of this, but what makes this "beautiful"? From a design standpoint, it's basic tailwind. Neutral grey tailwind at that, using Lucide icons. There's nothing wrong with these, but it'd be more apt to say that the design is unopinionated. It's the default choice when design intent is the afterthought and a focus is on functionality.
Again, not trying to undercut - looks like a solid agent interface, it just struck me as strange that beautiful was the adjective chosen when design seems to not be the objective here.
If you were to compare it to a painting or to the Grand Canyon or to the Northern Lights or like an act of kindness or a parent's love for their child or something, then I guess fine, not beautiful.
But for an open source project it's very nice!
(Note: none of the marketing materials for the website chose that word, at first glance. It seems to just be a descriptor given by the HN poster.)
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.
If anything it’s unglued me from my computer. I’ve been able to keep an agent working on a project while on long runs, bike rides, in transit. Much of our development workflow is the human in the loop refinement cycle now.
When I see "Beautiful", I automatically ignore it. Beauty is subjective, fashion changes. Bootstrap or React were considered beautiful in their time.
So basically an open source agentic GUI. Instead of "beautiful", it should emphasize what makes it special. Is it fast or lightweight? Does it do something other tools don't? Or does it do it better? What's it killer feature?
(Designer here) I like checking up what a product looks like when it's pitched as "beautiful". Mostly there are two ways to really meet that promise:
1. Masterful application of a trend (Stripe, Raycast)
2. Strong and recognizable personality (!boring, Notion, OG Basecamp)
Option 2 is the most accessible to small teams, but it's not an intuitive conclusion to draw. Both need an experienced designer to succeed, but option 1 sounds like it's a safe bet instead of a leap.
Most claimed "beautiful" products result from work done without the experience & taste to tell option 1 apart from an attempt at option 1.
In reality, you can pull off a strong personality and a clumsy execution, whereas following a trend clumsily looks like failing to read the room, and leaves you looking dated almost instantly.
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'm the maintainer of Paseo. I didn't submit this, so it was a nice surprise to see it on HN!
I'm around if anyone has questions about the project.
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?
Could you publish terminal-bench scores? What about memory usage?
btw, there is already a paseo package on f-droid, it's a step counter
So this is an alternative to using one coding agent with openrouter, changing the models between tasks? I am a neophite in these things, my ai use is more calling apis from scripts right now. Can somebody please explain the pros and cons (beyond to openrouter fees) of each?
This looks like something worth trying and I'm glad it's open source. I've been using https://github.com/openchamber/openchamber for a few months now and I'm pleased with its features. Their web based pwa and locally running cli is similar.
"Ship on the go" is so insane to me.
It's like people pulling their phones out while taking a piss standing, or having to pull their phones out when the traffic lights are red in a crossing.
Just, do one thing at a time, live a life.
Shipping code from your phone, whhhyy. Mates, this isn't a flex, it's depression.
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.
This seems extreme. Maybe I’m just optimistic but I think people can be intentional and present while also having the convenience and accessibility that something like paseo offers.
- If I’m on-call, it would be great to just take my iPad mini around with me instead of my heavy MacBook Pro. - Sometimes I’m on the couch with my phone and want to query an agent with access to my computer’s file system.
Not to undercut the open source nature of this, but what makes this "beautiful"? From a design standpoint, it's basic tailwind. Neutral grey tailwind at that, using Lucide icons. There's nothing wrong with these, but it'd be more apt to say that the design is unopinionated. It's the default choice when design intent is the afterthought and a focus is on functionality.
Again, not trying to undercut - looks like a solid agent interface, it just struck me as strange that beautiful was the adjective chosen when design seems to not be the objective here.
If you were to compare it to a painting or to the Grand Canyon or to the Northern Lights or like an act of kindness or a parent's love for their child or something, then I guess fine, not beautiful.
But for an open source project it's very nice!
(Note: none of the marketing materials for the website chose that word, at first glance. It seems to just be a descriptor given by the HN poster.)
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.
If anything it’s unglued me from my computer. I’ve been able to keep an agent working on a project while on long runs, bike rides, in transit. Much of our development workflow is the human in the loop refinement cycle now.
When I see "Beautiful", I automatically ignore it. Beauty is subjective, fashion changes. Bootstrap or React were considered beautiful in their time.
So basically an open source agentic GUI. Instead of "beautiful", it should emphasize what makes it special. Is it fast or lightweight? Does it do something other tools don't? Or does it do it better? What's it killer feature?
(Designer here) I like checking up what a product looks like when it's pitched as "beautiful". Mostly there are two ways to really meet that promise:
Option 2 is the most accessible to small teams, but it's not an intuitive conclusion to draw. Both need an experienced designer to succeed, but option 1 sounds like it's a safe bet instead of a leap.Most claimed "beautiful" products result from work done without the experience & taste to tell option 1 apart from an attempt at option 1.
In reality, you can pull off a strong personality and a clumsy execution, whereas following a trend clumsily looks like failing to read the room, and leaves you looking dated almost instantly.
I do think it's possible for one to qualify/quantify the how and why they deemed their product "beautiful".
I have the same reaction, it goes into a discard pile for me.
I think this is a neat idea. Is there a way to self-host the web app interface?
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!
Looks incredible, I just built what seems to be a shittier version of this using OrbStack + JJ a couple days ago. Will take a look!