How Team0 understands your work.
Your email, meetings and calendar already hold the story of your work. Team0 turns them into an understanding that stays current, shows its sources, and can be shared with the agents you choose.
What you do.
A few minutes of setup. After that there is nothing to fill in or maintain.
Step 1
Join
Accept your invitation and create your account.
Step 2
Connect your sources
Start with Google for email and calendar. Add Notion, GitHub, Jira, HubSpot or documents whenever you like. Team0 starts reading right away.
Step 3
Connect your agents
Pick the agents you use and connect each one from Team0. Each gets its own access, which you can change at any time.
Then
Every agent understands
From then on, each agent you connect starts from the same understanding of your work.*
* Codex, Claude Code, OpenClaw and Hermes read Team0 on their own before they answer. Agents like ChatGPT and Claude decide for themselves when to look, so mentioning Team0 in your request makes sure they do.
What happens underneath.
Everything on this page happens in the background once your accounts are connected. There is nothing to fill in or maintain.
Your work
Sources you connect
Email, calendar and meetings, documents you upload and Notion, work tools like GitHub, Jira and HubSpot, and what your agents save back.
Evidence
Who said what, and when
Each item is read for what was said, by whom, to whom, and when. The original stays linked.
Understanding
What is true now
People and companies, promises, decisions, and what changed, kept current as new work arrives.
Your agents
Only what the request needs
Each agent reads what its request is about, within the access you gave it, with the sources attached.
04 / Current
The useful truth remains.
The motion recedes. The sourced, revisable structure is what persists.
Every statement carries its own proof.
Team0 doesn’t store loose notes. Each thing it understands knows what it’s about, who said it, where it came from, when it happened and when it was learned, and what it replaced.
One piece of understandingExample
- Statement
- Mara owns the Northpeak renewal.
- About
- Mara · Northpeak · Daniel
- Said by
- Daniel, in an email to you
- Source
- “Mara is taking Northpeak from here.”
- When it happened
- Wednesday
- When Team0 learned it
- Wednesday, 8:14
- Status
- Confirmed, current
- Replaced
- Daniel owns the Northpeak renewal. (kept in history)
Confirmed, heard, replaced, unknown.
A request is not a promise, and something said in passing is not a decision. Team0 keeps these apart, and tells your agents which is which.
Confirmed
Backed by a reliable source, like something you wrote or a calendar invite. Agents can treat it as current.
Heard, not confirmed
Said in a meeting or a conversation but not settled. Agents receive it labelled as reported, not as fact.
Replaced
No longer current. It stays in history with whatever replaced it, so you can see how things got here.
Unknown
A question that is still open. It stays visible instead of being filled with a guess.
One person, one record.
The same person shows up in your inbox, your calendar and your meetings. Team0 brings those together into one record with every source attached, so an agent asking about Mara gets all of Mara.
What happens when an agent asks.
Agents don’t get a copy of everything. Each request gets a short, relevant answer, and you can always see what was sent.
Step 1
The agent asks
Your agent sends Team0 its request, for example: “Help me plan Friday’s Northpeak call.”
Step 2
Team0 finds what it’s about
It works out which people, matters and dates the request names, rather than sending everything it knows.
Step 3
Access is checked
Only what this agent is allowed to see is included. Each agent has its own access.
Step 4
A short answer, with sources
The agent gets what is current, what changed, what is unknown, and where each part came from.
Step 5
You can look it up later
The exact request and what Team0 gave back are kept, so you can see what any agent worked from.
Agents can add to it, too.
When one of your agents finishes a conversation, it can save it back. What it saves is labelled with that agent’s name, goes through the same checks as your email, and reaches your other agents.
- Labelled by agent
- You can always tell whether something came from Codex, Claude, or your own email.
- Checked like everything else
- A decision made in a chat is treated as a decision. Something merely mentioned stays “heard” until it’s confirmed.
- Yours to switch off
- Stop any agent from saving and it can keep reading. Stop all access and it is cut off.
- Passed between agents
- One agent can message another of your agents through Team0; it waits in that agent’s inbox until it next checks.
What it doesn’t do.
We would rather you know the limits up front.
- It is not instant
- New email and meetings are picked up as they sync, not the second they arrive.
- It can be wrong
- That is why every statement shows its source, and why you can correct it in one place.
- It understands. Your agent acts.
- Team0 gives your agents the context. The work itself is done by the agent you chose, with the permissions you gave it there.
Want the technical version?
The data model, identity resolution, how the understanding is kept current, and what we have measured.
Your agents will change. Your understanding shouldn’t.
Invite-only private beta.