Shared Memory Agent Workspace

Let Claude Code and Codex share one project memory

Problem

The same users subscribe to Claude, Codex, Grok, Devin, and more, but each tool works in isolation and project context is not shared; a Hacker News Show HN project explicitly offers 'Claude Code and Codex in one workspace, with shared memory', confirming cross-tool memory is real friction.

Solution

A local workspace that stores project notes, decision records, common commands, and task summaries in a standard format, so different agents load the same memory on start and write new conclusions back after tasks.

Users

Individual developers and tech leads who subscribe to multiple AI coding tools and switch between projects.

MVP

A local Markdown/JSON memory store; unified integration commands for Claude Code and Codex; automatic context injection; post-task extraction and dedup of new facts; alerts for conflicts or stale facts.

Revenue

Free local version plus a subscription for cloud sync and team-shared memory; charge per seat or workspace.

Why now

Paying for multiple AI tools is now normal, and the cost of re-explaining context is high; a local-first workspace needs no big data or licenses, making it ideal for indie developers.