Keep each tool.
Share the useful parts.
Your tools already have instructions and history. SymLink adds a shared place for reusable knowledge.
Separate app stores.
What one remembers may not reach the other.
shared files
what matters
Shared access helps.
It does not guarantee a file was read.
Recording is not the same as learning.
Instructions can tell an agent to save meaningful checkpoints without a reminder. The agent still has to write them. Sync moves saved changes; it does not turn every conversation into reviewed knowledge.
What is already native?
Claude Code and Codex already support readable instruction files. Conversation logs and app-specific memory are separate from those instructions. Memory behavior depends on the tool and its settings.
SymLink extends these native mechanisms with shared files. It does not replace them.
What becomes shared?
Reusable procedures, selected context, durable records and source-backed research can live in maintained files. They may be separate collections, each with its own index and review rules.
Raw records remain evidence. A reviewed note explains what is worth carrying forward.
How does the agent find the right file?
Task → index or short description → selected file → relevant references.
Priorities and pointers guide selection. They do not guarantee attention, unlimited context or correct use.
What about shared tools?
Shared MCP connection setup can help compatible apps reach the same tools. Each app still needs support, authentication and permission.
Configuration is not a login, and a how-to guide does not grant tool access.
How can I start?
Start with one instruction file, one useful guide, one knowledge note and a short index. Tell a connected agent where to start. Test a fresh session and verify which files it read.
Add more only when it helps. Review proposed updates and keep their sources.
Scope of this overview
This is a general architecture explanation, not a live status report for a particular computer. It contains no personal memory, private notes, credentials or local configuration.
Native app behavior, capture and synchronization depend on the actual installation. Verify those before making operational promises.