Shared sessions
Every agent session on your team runs in a place everyone can see and search — not buried in a teammate's terminal. The full transcript is the source of truth, not a Slack paraphrase of it.
Agent-native teamwork
Work at the speed of agents.
Decide at the speed of your team.
Your agents write the code, draft the memo, run the analysis — in minutes.
Then everyone on the team has to catch up. Slack threads, standups, "got a
sec?" — lossy summaries of work that already exists in full fidelity,
somewhere else.
Sapwood is where that "somewhere else" lives, and where your team collaborates inside it.
The problem
Your agents got faster.
Your team didn't.
Someone on your team spends two hours with an agent untangling a bug, a pricing model, a customer escalation. Then they have to explain it.
A Slack message. A standup. A "got a sec?" in a huddle. Every explanation is a lossy compression of the work that actually happened — a summary of the reasoning, not the reasoning. Your teammate reads it, builds their own mental model, and acts on it.
The parts of the reasoning that got dropped on the floor are exactly the parts that come back to bite you three weeks later.
Misalignment becomes invisible. People nod along to summaries they don't quite understand because the summary sounded plausible. The decision gets made. The consequences show up later, and nobody can remember why the call was made the way it was — because the reasoning was never written down anywhere a human would think to look.
This is the new bottleneck of knowledge work. Not building. Keeping everyone in sync on what was built and why.
How it works
One surface for the work, the questions, and the record.
Four tools, all built around the same idea: the reasoning behind a decision is more valuable than the decision itself, and it should be just as easy to find.
Branches
Have a question about a teammate's work? Branch their agent session at the exact message that raised it. You get a fresh session with the whole story already loaded — and you can ask the agent yourself instead of asking them.
Sidebars
Threaded discussions pinned to the exact moment a decision was being made. Debate in context, link related sessions as evidence, and resolve to a verdict that stays attached to the work — not lost in a channel.
Findings
Every agent session automatically drops a structured note into your knowledge base when it ends. No "now go write it up." The record of what you learned is a byproduct of the work itself.
Who it's for
Two kinds of teams. The same bottleneck.
Sapwood was designed around a single idea: the reasoning behind work is the work. That idea shows up differently depending on who you are — but the bottleneck is the same.
For engineering teams
Review the reasoning, not just the diff.
A PR is the last ten lines of a long conversation with an agent. It drops every alternative you rejected, every assumption you made, every dead end you ruled out. Your reviewer sees none of it.
- Review the agent session, not just the diff
- Branch from any moment to push the architecture a different way
- Decisions stay pinned to the code they shaped
For operating teams
Stop briefing. Start branching.
Strategy, research, pricing, campaign planning — your team already does this work inside agents. Today it gets flattened into a deck before anyone else can engage with it. Skip the flattening step.
- Institutional memory that compounds as a byproduct of work
- Sidebars replace “hop on a call to align”
- Decisions become searchable — not lost in a channel
Proof point
8 weeks
Four engineers. A production financial data sync for a
Fortune 500 enterprise. Work most teams scope for two to three
quarters.
A smaller team. Shipping faster. With a higher quality bar.
A team of four engineers — one senior, two mid-level, one junior — shipped a production-grade data sync system in eight weeks. The project was scoped for a larger team over multiple quarters. The quality bar was unforgiving: it handled financial data, where a shipped bug is a billable incident.
It worked because the team didn't spend their time summarizing work for each other. They spent it branching into each other's sessions, resolving questions in context, and letting the knowledge base accumulate as a byproduct. Sapwood is that workflow, made into a product.
Early access
Join the waitlist.
Sapwood is in private development. We're onboarding a small number of teams whose work is already happening inside agent sessions. Tell us about yours.
We read every response.