Sequel to Premia, I guess?

Obligatory Show HN page.

Sans Serif

I used Claude Code back when it was still cool.

But I used Claude Code via the VSCode extension. It is updated less frequently, is sometimes buggy, and is missing some features, like customizing spinner verbs.

But I still used the VSCode extension, because it uses sans-serif for prose.

CLIs are cool, so coding agents use CLIs. But as a consequence, they display both code and prose in monospace.

Using monospace for prose is just wrong. It is a compromise.

Doing the Right Thing

Here is a list of coding agents that have a GUI, and thus do things the right way:

  • OpenAI Codex, renamed to ChatGPT
  • Claude Desktop, I think. Never used it.
  • GitHub Copilot in VSCode
  • Other editors: Cursor, Zed, …

But these are first-party solutions, and the OpenCode official VSCode extension is simply a glorified terminal window.

So when I needed a remote for my coding agents, I made sure to look for one with a GUI.

Then I found Paseo.

Orchestrate

Paseo runs multiple coding agents in multiple places.

My friend recommended it because they were running multiple GPU tasks on Slurm clusters; I found Paseo because I wanted my agents to run during lunch break.

Paseo daemons control coding agents using their CLIs. These can be on your own machines, or in the cloud.

Paseo clients let you connect to daemons. There are clients for web, desktop, and mobile.

It Just Works

The good thing about Paseo is that it is very well thought out. Everything just works.

The native mobile app has full feature parity with desktop.

Yes, it has:

  • A terminal
  • A Markdown renderer
  • Rendering for inline images
  • Files view, Git view,
  • on both desktop and mobile.

The desktop app comes with a daemon, so it works out of the box; The mobile app has easy pairing with a QR code. It even works behind NAT.

NAT

Wait a minute, you say.

Works behind NAT? It relays all my traffic?

And yes, Paseo comes with an end-to-end encrypted relay, hosted on Cloudflare.

The Security docs is, as one would expect from the rest, thoughtful; the protocol is public, as well as an official relay, so you can self-host a relay. I did.

The Solo Dev

Paseo is, as far as I am aware, a solo dev project.

I vibe-coded a music player called Sparkle recently, so I know the constant urge to polish, fix, and add features.

This happened when there is only one user (me), so I understand it must be very hard to keep up with lots of users, issues, and PRs.

And did break once — update v0.1.108 would not open at all. But the author fixed it real fast, and was kind enough to say “this will not happen again”.

Apart from “amazing work”, what can I say?

Hub

I just checked Paseo docs and it has a new feature, called Hub!

A brief reading suggests that this enables “@paseo have a look at this” and collaboration.

I think this is a promising direction, since coding agents are where the work happens nowadays anyways.

The CLI

Speaking of directions, my friend mentions that Paseo’s CLI is powerful in that it lets coding agents control coding agents.

Despite not using such a workflow myself, I agree. Other coding agents have “subagents”, but they are sort of rigid; By exposing a CLI with --help, Paseo allows workflows to be much more flexible.

Plus it is developing more features like Hub, so an exciting future awaits.