The pain
The bottleneck isn’t skill — it’s context. Every new Claude session starts blank. Decisions, rejected paths, and workarounds from the last session vaporize when it closes.
Wyren
Multiple humans. One brain. Zero workflow change.
What is Wyren?
Section titled “What is Wyren?”Git made code collaboration possible. Wyren does the same for the AI working alongside your team.
Wyren is a Claude Code plugin that gives a team one shared memory across every teammate’s sessions. No one has to change how they work.
Right now, every teammate has a different Claude — blank, unconfigured, and unaware of what the rest of the team has built, decided, or deliberately left unfinished. Wyren gives your whole team one shared brain.
When anyone on the team runs Claude Code, Wyren:
- Watches the session transcript in the background.
- Distills decisions, rejected paths, and live workarounds into a compact
memory.md. - Syncs that memory to every teammate via git.
- Injects it as hidden context at every new
SessionStart— so any Claude, on any laptop, starts warm.
The 10-second pitch
Section titled “The 10-second pitch”The insight
Markdown captures conclusions. Wyren captures the reasoning — the rejected ideas, live hacks, and deliberate shortcuts that look like bugs.
The result
Open Claude Code on a 4-hour-old project. Without Wyren: clueless. With Wyren: names the known workarounds and rejected approaches in the first assistant message, unprompted.
The footprint
One Claude Code plugin. Zero infra. Works with your existing git remote.
How Wyren is different
Section titled “How Wyren is different”| What it does for teams | |
|---|---|
| Git | Syncs code, not comprehension. |
CLAUDE.md alone | Static; someone has to remember to write it — at the moment they have least time. |
| Claude Projects | Shared docs, but no live session memory or cross-teammate sync. |
| Agent Teams | Multi-agent coordination under one human. Doesn’t help N humans with N Claudes. |
| Wyren | Continuously distilled, git-synced, auto-injected team memory. |
See the problem for the full comparison matrix.
Key selling points
Section titled “Key selling points”Zero friction
Nobody changes how they work. Open Claude Code, get full team context. No commands, no syncing, no briefing.
Works on handoff
When work changes hands, the new session already knows everything. Zero briefing, zero dead zone, immediate productivity.
Captures the why
The only tool that preserves the reasoning behind the codebase, not just the output of it.
Consistent behavior
Shared skills and settings mean every teammate’s Claude behaves the same way on the same project.
Get started
Section titled “Get started”Ready to install? Follow the install guide — two minutes, one shared brain.
Or start with the problem to understand why existing tools fall short, then walk through how it works.