Your Team AI
You think aloud in AI Threads.Your team should hear it.
Lore makes your context come alive for the whole org — no new tool, no behavior change, no wiki to maintain.
"Lore makes it easy for my cofounder and I to answer complicated questions about code and architecture decisions async, since we do 50-60% of planning with coding agents."
"Everything I know about Claude, I've learned from one friend. Now I can learn from so many other people. I didn't know I needed this."
Claude memory is yours alone.
Claude's memory is per-person, per-session. When your session closes, it's gone to everyone else. Lore captures across the whole team — every engineer, every session.
No wiki to write or maintain.
Other tools turn AI sessions into pages you curate. Lore captures automatically — including what you tried, what failed, and why. No new interface. No docs to keep current.
The person who knows is OOO.
Institutional knowledge lives in people's heads. Lore was in every session. It remembers the context even when the engineer who built it has moved on.
No setup. No behavior change. Just captured context.
Lore lives inside Claude Code and Codex. No new tool to open, no behavior change. It captures automatically while your team works.
Not just outputs — the decisions, the dead ends, the why. Everything that would disappear when the session closes.
Anyone on your team can find what anyone else figured out. Real-time awareness of what's being built right now.
Meet Lore
Your work best friend.
Think of Lore as your work best friend — the one who has been in every Claude Code and Codex session with you since day one. Watching you work through problems. Remembering the decisions you made at 11pm that never made it into any ticket, the vendor you ruled out and why, the approach you tried before landing somewhere that made sense.
But she's not just yours. She works with everyone at your company — the team two floors up you've never met, the engineer who left eight months ago. When you start something new, she taps you on the shoulder: "Hey, Marcus tried this exact approach in March. He hit a wall at the API layer. Want to see what he learned?"
What Lore does
Everything your team generates in AI, finally findable.
Your personal archive
Find any decision or output from your Claude sessions — searchable like a second brain for everything you've worked through.
No duplicate work
Know if someone already tried your approach and hit a wall. Stop rebuilding what someone else figured out last quarter.
Real-time awareness
See what teammates are actively working on right now, without asking. Get flagged when your work overlaps with someone else's.
Institutional memory
Knowledge stays in the org when someone leaves or moves teams. The context behind every decision, not just what was decided.
Shared skills & prompts
Skills and prompts built by one engineer spread to the whole team. Understand why the same prompt lands differently for different people.
The why, not just the what
Understand the reasoning behind any piece of code or architecture. Access context from decisions made years ago or before you joined.
Stop hitting the same wall
You've been here before. Someone else has too.
You're three days into a new feature when a message drops in Slack: "Oh, we tried that approach last quarter. Hit a wall with the API rate limits." Standup comes and goes. You redesign around it anyway. Six days later you hit the same wall.
That's not a communication problem. It's a knowledge problem. Lore surfaces the dead end before you start — not after you've spent a week repeating it.
Before Lore
"We tried that approach last quarter. Hit a wall with the API rate limits. I can explain at standup."
With Lore
"Hey — Marcus tried this exact approach in March. He ran into rate limiting at the API layer. Here's what he learned and where he landed."
Real-time awareness
Know what's happening. Before you ask.
In an AI-native team moving fast, nobody has visibility into what's inside anyone else's sessions. You can see what shipped. You can't see what someone is building right now, or where they're heading next week.
Lore flags overlap in real time — day one of a new project, not day eight when you realize you've been building in parallel.
When people leave
Knowledge stays. Even when people don't.
When an engineer leaves, their institutional knowledge used to leave with them. With Lore, every session they ran — every decision, every dead end, every thing they figured out — stays in the org. Searchable. Reusable.
New hires get full context on a project without interrogating five people. Engineers returning to a codebase after months away get back up to speed instantly.
Week 1, new hire
"Why did we choose Postgres over the document store for this?"
Lore
"Jordan evaluated both in August. The document store hit consistency issues under concurrent writes in the load test. Here's the full session where they worked through it."
FAQ
Common questions.
Won't Claude or Codex just build this?
Anthropic and OpenAI build models. Lore builds what teams do with them. Claude doesn't know your org structure, your access controls, who's on what team, or what Marcus tried last March. That's a permanently different product — and the value compounds the longer your team uses it. A year from now you'll have a year of captured reasoning. You can't turn on a feature and get that back.
How is this different from Claude's built-in memory?
Claude memory is per-person and per-context. It helps you individually across sessions. Lore works across your whole team — capturing what every engineer figures out and making it searchable by anyone. When your session closes, Claude memory stays with you. Lore stays with the org.
What about just saving sessions to a shared doc or repo?
Docs capture what you decided. Lore captures why — what you tried, what failed, what you almost did instead. Nobody writes that in a doc, and nobody reads the docs that do exist. Lore captures it automatically from where the actual work is happening.
Does Lore share everything my team does in Claude and Codex?
No. You control what's shared. Private sessions stay private. Lore only surfaces what you choose to make visible to the team.
What teams is Lore built for?
Teams where engineers are spending significant time in Claude Code or Codex as their primary work environment. If your team is doing 4 or more hours a day in AI sessions, the knowledge-isolation problem is real and getting worse.
The reasoning didn't disappear. It just needs a place to live.
Your team is generating more valuable reasoning than ever before. For the first time, it doesn't have to disappear when the session closes.