joaoh82

Hello there,

I am Josh and I always bounce between Windows, Mac, and Linux, and I use coding agents from different providers. I couldn’t find a tool I actually liked that worked the same way on all three, or even had a distribution for all three for that matter, so I decided to build Yardsort and open-source it.

It’s a desktop app: every task gets its own git worktree and a real terminal running the agent CLI you already have (Claude Code, Codex, Cursor, OpenCode, Grok, …). And you can start several agents in parallel sharing the same worktree or branch while working on the same task.

After the first version worked, I started using Yardsort to build Yardsort. That’s how most of the “nice” features showed up. They were just what my own workflow needed. I basically followed the pain.

A lot of tools let you swap agents on the same worktree or branch. Fine until you need the next agent to know what the last one actually did. Context sharing is usually a pain. So I built handoff: it writes the next agent’s first message from the task, commits, changed files, and what was recorded about the runs. It is not a dump of the previous chat. There’s also project memory you approve before any agent sees it.

I was also doing the same chores over and over. For example, “have another agent review what this one just shipped.” So I built the workflows feature. Workflows are YAML you write yourself, or you can ask an LLM to draft one and keep what you like. Built-in example: request a code review from a second agent in the same worktree.

Everything is private by default: no account, no telemetry, no keys of mine. I’m currently working on “Yardsort sync” so you can share memory and do handoffs across machines via a cloud service with end-to-end encryption, and I’m open-sourcing that path too, with an easy self-host option, because I don’t want this to only work my way.

GPL-3.0, Tauri + Rust. Early, moving fast, rough edges expected.

Site: https://yardsort.sh

Repo: https://github.com/joaoh82/yardsort

Downloads for all three OSes via GitHub Releases.

Happy to dig into handoff, workflows, or any other bits if you have questions.

Cheers, Josh

This is a playable AI proof of concept. TypeSafe AI’s Jev model chooses the tactics for every NPC from infantry and tanks to the general. The game handles movement, aiming and combat.

Since we do not have an official Buzz Discord Server yet I created a community one so we can help each other, share thoughts and etc.

Interesting! I'll take a look.

About monetization, that is definitely very important. For now, and not sure how long, could be days or weeks, I am offering api-keys at no charge, because I want the feedback of real users. But obviously that is not sustainable in the long term, servers cost money and monetization also help keep the project alive.

At a second stage, I am planning to offer monthly or yearly plans with different limitations or unlimited also. But I am also planning on offering pay per use with short lives api-keys targeting agentic workflows, for example or people that dont really want to pay a monthly fee, but instead just cents for a short-lived tunnel.

For the monthly plans, I am planning to keep as low cost as possible, just enough to maintain the infrastructure and development + some overhead.

that is a very good use case. I am definitely adding this to the roadmap at least a maybe.

Thanks for the question.

Very good points. Including the AGPL, that is definitely a better license for this type of project. I am just used to starting with MIT when I start a new open source project, but you have a point.

About monetization, that is definitely very important. For now, and not sure how long, could be days or weeks, I am offering api-keys at no charge, because I want the feedback of real users. But obviously that is not sustainable in the long term, servers cost money and monetization also help keep the project alive.

At a second stage, I am planning to offer monthly or yearly plans with different limitations or unlimited also. But I am also planning on offering pay per use with short lives api-keys targeting agentic workflows, for example or people that dont really want to pay a monthly fee, but instead just cents for a short-lived tunnel.

For the monthly plans, I am planning to keep as low cost as possible, just enough to maintain the infrastructure and development + some overhead.

Its not mine, its ours. That is what Open Source is about.

All I know is that I try to build a fast, low latency solution, that I can provide for low cost or people can just self-host themselves. I am trying to keep the docs pretty good.

For now is free. And when we start charging will definitely be cheaper. Also, the project is open source and there is good documentation on how to standup your own infra, if you want to go down that path.

Hey! it does support subdomains. Either by passing a flag --subdomain or just configuring them straight up in you config.yml file.

We also implemented auto-reconnect.

For now we only running servers in Europe, but we are implementing multi-region right now and should have it up in a couple of days. That should cut latency way down for people that not in Europe.

Nice! Will do!

Btw, if anyone wants to test on our own servers just request an api key with github issues: https://github.com/joaoh82/rustunnel?tab=readme-ov-file#gett...

A ngrok-style secure tunnel server written in Rust. Expose local services through a public server over encrypted WebSocket connections with TLS termination, HTTP/TCP proxying, a live dashboard, Prometheus metrics, and audit logging.

I tested plenty and the console logs in the UI is a game changer. Super slick.

The definitive directory for Model Context Protocol (MCP) servers. Discover, install, and contribute to the AI integration ecosystem.

Screen Console is a logging tool made for Godot 4 that allows you to print messages to the screen for debugging and development purposes.

thanks for the tip man. I think you are right. Rust data structures might do the job at first, specially for in-memory operations. But on-disk storage if definitely going to be a problem.

I wouldn't mind partnering up with Mozilla on this. Hey Mozilla!!!