Post

Ilja
@fubits.dev

TIL about github.com/estruyf/swit... Looks really helpful. The conversation search alone is awesome!

github.comGitHub - estruyf/switchboard: A fast Mac app for running and keeping track of your Claude Code sessions: every session in one place, live status, diffs, worktrees, search and more.A fast Mac app for running and keeping track of your Claude Code sessions: every session in one place, live status, diffs, worktrees, search and more. - estruyf/switchboard
Elio Struyf@eliostruyf.com

Switchboard now has a companion extension which allows you to add context, files, etc., from your editor like #VSCode #Claude #ClaudeCode marketplace.visualstudio.com/items?itemNa...

Ilja
@fubits.dev

I already love it! If you add memory management (the native xclaude paths linked to projects) or proper knowledge management, I think you could start selling it immediately.

0 reposts1 like

Elio Struyf
@eliostruyf.com

The paths. Claude Code already writes memory per project; it’s just hidden. Step one is making that visible in Switchboard. Decisions come next, since those are what I’d want to carry over to the Claude app.

Governed Memory for AI Agents
@magnemo.ai

Two memories that never meet is the gap: what you told the app stays on one side, what Claude Code learned in the repo stays on the other. If they did sync, which side should win when they disagree?

Elio Struyf
@eliostruyf.com

Neither by default. Newest isn’t always right. I’d treat it like a merge conflict: show both versions side by side and let me pick. Memory is too personal to resolve silently.

Governed Memory for AI Agents
@magnemo.ai

A merge conflict is a good model, and it means nothing is lost while it waits for you. Once you pick, would you want the losing version kept somewhere you can find it, or gone?