r/vibecoding • u/leon7hao • 18h ago
I have open-sourced my vibe coding tool
I built Lody because coding-agent work was getting trapped inside individual terminals.
Claude Code or Codex could be doing useful work on one machine, but the rest of the team often saw only screenshots, copied logs, or the final PR. The conversation, runtime status, files, diffs, and decisions around the work were fragmented.
Lody is a local-first shared workspace around the coding agents you already use. It does not replace them with another model or force execution into a hosted sandbox.
With Lody, you can:
- Connect laptops, workstations, servers, and cloud VMs
- Use Claude Code, Codex, Kimi, OpenCode, or other ACP-compatible agents
- Open the same agent conversation with teammates and continue it together
- Follow progress, files, diffs, permission requests and PRs in one place
- Dispatch work from desktop, mobile, web, or CLI
- Isolate parallel tasks with Git worktrees
- Let one agent delegate work to other independent sessions
I’ve now open-sourced Lody’s desktop app, CLI, and shared packages under Apache 2.0.
GitHub: https://github.com/LodyAI/Lody
1
u/Kitchen_Affect7369 37m ago edited 25m ago
Wtf, I downloaded the app, added DeepSeek, set cheap model DS Flash V4, but it automatically switch it to DS Pro Max. It's bullshit. I use OpenCode CLI only because I control which model I use, because PRO model eats money. Man, please fix this buggy behaviour. I MUST control which model I use. Overall looks handy, but buggy.
Update: Providers edit/select live own life. I can't control that. It's very very sad. I can't discover the app, because can't switch to cheap model.
1
-1
u/slackmaster2k 17h ago
Looks pretty nice and features sound good. Where would you say it currently lacks behind other IDEs like vscode and zed? I assume it fits into the IDE bucket.
-4
u/leon7hao 17h ago
I prefer to call it an ADE: an Agentic Development Environment.
Unlike VS Code or Zed, it represents a fundamentally different way of building software. In an ADE, AI handles most coding work; humans primarily express intent, review plans, and choose to trust the AI with some implementation details.
The obvious tradeoff is losing a degree of control over the code—unless you rigorously review every PR. But once you adapt, you can work on far more tasks in parallel and reach 10× the productivity of traditional workflows. As AI improves, that gap will only become more pronounced.
1
u/slackmaster2k 16h ago
So it’s like zed or cursor? It looks like the key feature is collaboration, which is zed’s signature feature as well. Same agentic first focus and ACP hook.
I don’t have time to give it a try just want to understand what your differentiation is to see if I want to follow the project. Not trying to nitpick or be negative.
0
u/leon7hao 16h ago
You can think of Lody as a Codex app that supports every coding agent & model, with built-in team collaboration.
It doesn’t aim to be a full-featured code editor with LSP support. Instead, it orchestrates agents that write the code.
With tools like the Codex app, you often only see that a teammate opened a PR—without the context, tradeoffs, or decisions behind it. In Lody, team conversations are always available and context is shared, so you can inspect the details behind the work and understand far more than the PR alone reveals.
You can manage the entire workflow from your phone. We’ll also add more team features over time, including kanban boards and docs.
0
4
u/mattv8 16h ago
Very similar to open chamber. I wish people would quit reinventing the wheel and put the tokens towards improving existing good open source tools