HNHacker News
TopNewBestAskShowJobs

patriceckhart

83 karma · joined August 12, 2025

submissionscomments
patriceckhart··on Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
I wrote a blog post about my odyssey: https://www.patriceckhart.com/blog/posts/2026-08-01/hrdx
patriceckhart··on Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
I'm using github.com/aymanbagabas/go-pty. It gives hrdx a common interface for Unix PTYs and Windows ConPTY. The terminal emulator itself is implemented inside hrdx. I would be interested to hear how it fits your workflows once you have had time to try it.
patriceckhart··on Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
These tools are personal because everyones workflow, preferred keybindings, and visual organization differ. Building exactly what you want can be more useful than adapting to a general solution, and the process is valuable too. cscope looks interesting, and I like that it takes a more colorful approach. Thanks for sharing it. hrdx was created, among other reasons, because I wanted full support for my own coding agent, zot.sh, without having to wait for a PR to be merged.
patriceckhart··on Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
Yes, absolutely inspired by herdr. The main reason I built hrdx was that I wanted to explore the idea in Go and shape it around my own workflow. I focused on persistent PTY sessions, workspace and Git branch organization, agent activity indicators, custom agent harnesses, and a socket API for external automation. There is definitely overlap, and I'm not claiming the underlying idea is unique. It is mostly my own take on the same problem.
patriceckhart··on Show HN: Yet another minimal and lightweight terminal multiplexer written in Go.
True. The features arent groundbreaking.

But fair question. If tmux already fits your workflow, there may be no reason to switch. hrdx is more opinionated around running multiple coding agents across projects: it provides a workspace and pane sidebar, agent activity and completion status, built-in launch/resume flows, persistent sessions and layouts, and an external control API. The tradeoff is that it is much younger and less configurable than tmux.

Try it, play around with it, love it or hate it :-)

patriceckhart··on Show HN: Zot – Yet another coding agent harness
I'm working on a GUI. If you are interested, contact me on X or by email. You can find my email address on patriceckhart.com
patriceckhart··on Zot now supports Claude Opus 4.8
I get it. Ha, over in Zerostack I even got a shoutout with zot. :-)
patriceckhart··on Show HN: Zot – Yet another coding agent harness
You rocking your own harness? Public by any chance? If so, mind if I take a look?
patriceckhart··on Show HN: Zot – Yet another coding agent harness
btw, you can totally use zot's packages for your own TUI too.
patriceckhart··on Show HN: Zot – Yet another coding agent harness
Thanks for the tip. I might do that—though honestly, Im a sucker for jokes like this. And yeah, the TUI is literally 98% vibe coded.
patriceckhart··on Show HN: Zot – Yet another coding agent harness
pi is extensible at every turn. thats what makes it special. zot is more limited there.
patriceckhart··on Show HN: Zot – Yet another coding agent harness
zot is a coding agent harness. not a data vault, not a pacemaker, and not a life-support device in any medical sense.

Ive been coding for almost 20 years, and for the past few with Go. Nobody would believe that a project of this scale or even a much smaller one could be pulled off, halfway stable, over a couple of days. Not even with a blueprint or two in hand. Thats why it matters, and its totally fair, to point out when something is largely vibe-coded. "Vibe slopped" is meant more as a joke. The essential parts of the code I actually understand. Some of them I modified and overhauled myself.

zot is a learning project not production logic with peoples sensible data or lives depending on it. ;-)

patriceckhart··on Show HN: Zot – Yet another coding agent harness
pi is awesome, quite possibly the best OSS tool out there. You should definitely give it a shot if it fits your stack. zot has become my daily driver. I didnt build zot to compete. I built it to really get a feel for how harnesses work, and I do it with Go simply because I love the language. More on that here: https://www.patriceckhart.com/blog/posts/2026-04-23/why-i-bu...
patriceckhart··on Show HN: zot – Yet another coding agent harness
Thanks for the feedback! Since version 0.1.44, you can use the left/right arrow keys to jump through the "History".
patriceckhart··on GenesisDB on DigitalOcean: One Click, Done
Others coming soon ;-)
patriceckhart··on Genesis DB is a event sourcing database and there are the technical insights
Genesis DB is a event sourcing database designed for applications that require immutable audit trails, temporal queries. It provides CloudEvents-compatible event storage with cryptographic integrity verification, a powerful query language, and built-in support for GDPR compliance.
patriceckhart··on The Complete Event Sourcing Guide
Start mastering event sourcing and build scalable, auditable, and event-driven systems with our comprehensive guide to event sourcing architecture.
patriceckhart··on Ask HN: Thoughts on Genesis DB LocalStack
I've thought about that. Do you actually see a real use case for running a Mac as a server? Maybe if you're hosting an internal-only app and the Mac acts as the local database server.
patriceckhart··on Ask HN: Thoughts on Genesis DB LocalStack
Over the past months I've been working on Genesis DB an GDPR-ready event-sourcing database built for simplicity, performance, and real-world use.

One piece of feedback that kept coming up: "Docker is great, but for local dev it can feel heavy, especially when I just want to spin up an event store and start building."

So I built Genesis DB LocalStack. A native macOS experience for event-sourced development:

What it does

- Runs Genesis DB locally, natively, no Docker daemon needed

- Launch instances in milliseconds

- Each project gets its own isolated DB + domain (*.genesisdb.local)

- Run multiple instances for microservices workflows

- Export/Import environments for fast team onboarding

- Config lives in plain text: version control friendly

Why?

Local dev today often means container orchestration before first code. Genesis DB LocalStack tries to remove friction: install app > click > build.

Sometimes the fastest developer experience is still the simplest:

Real processes on your machine, predictable ports, zero orchestration overhead.

Is a native, Docker-free local event-store helpful to you?

Appreciate any feedback, especially from folks doing event sourcing and CQRS, perhaps even with Genesis DB, in production.

Many thanks!

patriceckhart··on Show HN: CQRSKit: A TypeScript CQRS Framework with Pluggable Database Adapters
Thank you!
patriceckhart··on Show HN: Genesis DB is now officially listed on dbdb.io
Thank you very much! I'm glad you like Genesis DB!
patriceckhart··on Ask HN: Genesis DB: Thoughts on fine-grained access control
Thanks! Are you using Genesis DB yourself at the moment, or just speaking from general experience with JSON-based policy systems?
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
Not open source, but we're planning to open things up with Genesis DB CE - a free, fully usable community edition: https://www.genesisdb.io/blog/posts/2025-09-25/genesis-db-1-...
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
I appreciate your remarks and the perspective, that's valuable feedback. I'll think about adjusting it to make the message clearer.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
Thank you for your comment! I think it's actually your very first one on Hacker News, or am I mistaken?

If you run into bugs and want to share them, please just open an issue in the GitRepo's, or send us a message, ... Genesis DB is already being used in production projects, and so far issues that came up have been addressed in newer builds, including performance.

On performance specifically, it would be really helpful to know more about your setup: machine, architecture, how much RAM, ... Performance issues mainly existed in the very early versions, some of which were still SQL wrappers.

On the "one-man show" point: The architecture of your software can allow you to swap out the underlying database system, meaning you're not dependent on anyone. Thanks to CloudEvents, your data remains compatible with other CloudEvents-supporting systems.

In the end, it's up to everyone to decide which software they want to use.

patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
It's a playful metaphor. We meant that the logs are thorough, reflective, and give you insights. They help you understand your system and its processes. No worries, you won't end up contemplating the meaning of life, unless you really want to. :-)
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
I understand. Honestly, it was never my intention to get rich with this project. Covering a bit of the development time, servers, and so on would already be nice. Since Genesis DB doesn't limit the number of instances you can run, I would have happily used it myself as a developer at that price point. I've thought about a one-time payment model before. But as I said, I do understand your perspective.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
That's a valid question. At the very least, disclosing the libraries being used might even be mandatory. I'll check on that asap and add it to the documentation.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
TimescaleDB looks great and is built on top of Postgres. Genesis DB, in contrast, is a straightforward (if not simpler) event store that manages data differently than Postgres. That said, TimescaleDB is definitely worth a look.
patriceckhart··on I Built an Event-Sourcing Database Engine: Meet Genesis DB
Not at the moment, but I'm considering a one-time payment option since people generally dislike subscriptions.
Page 1 of 2Next →