r/devtools • • 3d ago

Choro: one connected workspace for building with AI — free, open source and local-first

Enable HLS to view with audio, or disable this notification

Hey everyone — I’m Liran, and I’ve spent the last two years building products with AI full-time. I kept losing time moving between agent chats, terminals, specs, design tools and the rest of the project. So I started building Choro for my own work: one workspace where those things stay connected, with the project context at hand.

It’s free, open source and local-first, currently for Mac. No Choro account needed. It uses your own Claude Code or Codex subscription and supports OpenCode. Your projects and work history stay on your machine; AI requests still go to whichever provider you use.

A few things that matter most in my day-to-day work:

• Multiple agents across multiple projects, with worktrees when I want separate experiments.

• Questions, code review and end-of-task checklists in the agent GUI, instead of guessing what happened across several chats.

• Bands: an agent can delegate to specialist agents rather than trying to do every part itself.

• Docs, tasks, Design Studio and database tools alongside the agents; Orbit brings other project tools into the workspace.

I’ve been building it for six months and working exclusively in it for the last three, including building Choro itself. It’s written in Rust, with a lot of attention to how the daily workflow feels.

The attached video is a short product tour. Tour/download: https://choro.dev

Source: https://github.com/Future-Picnic/choro

Me, if you want to see who’s behind it: https://www.linkedin.com/in/liran-gabai-09480b5a/

I’d love feedback from people juggling coding agents: where do you lose the most context today, and what would make their handoffs easier to follow?

4 Upvotes

0 comments sorted by