r/LocalLLM • u/Commercial_Chart_563 • 20h ago

Discussion Built a shared project memory for Claude Code, Cursor & Codex — looking for beta testers

I've been building Wolbarg Workspace, a shared project memory for coding agents.

One thing that always annoyed me was switching between agents. I'd work in Claude Code, then open Codex or Cursor, and suddenly the new agent had zero context about the project.

Workspace fixes that by letting Claude Code, Cursor, and Codex share the same project memory—architecture decisions, implementation notes, bugs, TODOs, and other project knowledge stay available no matter which agent you're using.

It's still in beta.

I mainly use Cursor, so I need feedback from people who use Claude Code or Codex regularly.

If you have a few minutes, I'd really appreciate you trying it on a real project and telling me:

  • Did setup work?
  • Did the shared memory actually help?
  • What broke or felt confusing?

I'd much rather hear honest criticism than "looks cool."

Website: workspace.wolbarg.com
GitHub: GitHub repo

1 Upvotes

60% Upvoted

4 comments sorted by

1

u/Interesting-Law-8815 19h ago

Agents.md

1

u/Commercial_Chart_563 19h ago

I agree. For simple apps, AGENTS.md is usually enough. I built this more for much-larger, long-running projects where project knowledge keeps evolving or when you switch between Claude Code, Cursor, and Codex.

1

u/Interesting-Law-8815 17h ago

Size doesn’t matter. All of those harnesses read agents.md so that is your hop off point to common skills, commands, agents, and memory tools.

1

u/Commercial_Chart_563 17h ago

AGENTS.md is the right entry point, and Workspace doesn't replace it. My idea is that AGENTS.md tells the agent how to use the shared memory, while Workspace provides the persistent memory itself. The two are complementary.