Vibe coding left me with too many side projects. So I built one more.

I've been doing a little too much vibe coding lately.

An idea turns into a new folder. Another idea, another project. Before long, my drive is full of things I'll "definitely get back to."

Then I open one a week later and wonder: what was this supposed to do? How do I run it? Where did I leave off? Was that conversation in Claude Code, Codex, or OpenCode?

I got better at starting projects. Remembering them didn't get any easier.

So, naturally, I started another project to deal with the others.

It's called RepoAtlas, an open-source desktop app for organizing local projects and finding your way back into them.

Getting back to a project

The workflow I’m trying to make easier is pretty simple:

1. Find the project. Scan directories you choose, search your project library, and group related work without moving folders around.
2. Get it running. Save dev, test, and build commands, run them from the app, and keep their output and history.
3. Pick up the conversation. Search authorized local histories from coding agents, preview the relevant messages, and resume the selected session.

That last part matters when the code is still there, but the reasoning behind it is buried in an old chat.

Session search supports tools including Claude Code, Codex CLI, and OpenCode. Resuming takes you back to the original agent; it doesn't migrate conversations between tools.

The screenshots use fictional demo data.

Avoiding another catalog to maintain

Manually describing every half-finished experiment would become its own unfinished project.

RepoAtlas has an MCP integration so an external coding agent can help inventory approved directories and add project descriptions and reusable commands based on the actual files. Manual setup is available too.

The app is built with Tauri + React and released under the MIT license. Project records, task logs, and indexed session history stay local. There's no RepoAtlas account to create; your coding agents still use their own accounts and model providers.

Still early — macOS testers especially welcome

I mainly develop and test on Windows. I don't have a Mac, so the macOS packages haven't been tested on real hardware and are experimental, not a supported release.

Help with macOS builds, installation, session launching, and bug reports would be especially useful. Contributions and PRs are welcome.

A packaging note: the Windows beta installers are currently unsigned, and the experimental macOS packages aren't notarized.

Source and downloads: Wujerry/RepoAtlas on GitHub

Hopefully, the tool for managing unfinished projects won't become another unfinished project itself.

How do you keep track of your side projects and the AI conversations that go with them?

---

AI assisted with drafting this article.