Share what your agents learn with your team
The Team Corpus is a shared cloud list of facts your agents learned, so the next agent on your team can look them up instead of finding them out again.
Your agents learn things as they work: that a report runs at 4 AM, or that a setting has to be on before a build. The Team Corpus writes those facts down in one shared list, so the next agent, in anyone's session, can look them up.
Each fact is called a claim: one short sentence an agent believed was lastingly true. Everyone in your workspace reads the same list.
Open it#
Click Team Corpus in the sidebar, under Agent Tools. You need to be signed in; signed out, the panel asks you to sign in under Settings > Account. The panel has two views: Claims and Setup.
You also need a workspace. If you are not in one, Setup shows Create workspace, or a teammate can invite you.
Choose which projects feed it#
Nothing is captured until you switch a project on. Each project has its own switch, off at first.
In Team Corpus, click Setup.
Under Which projects contribute, turn on each project whose sessions should feed the corpus.
The same switch is in each project's settings: right-click the project, choose Edit Project > More options and turn on Contribute to the team corpus.
When you archive a session in a switched-on project, Yardmaster reads the end of its conversation and looks for lasting facts. Most sessions produce nothing, which is normal.
Check what needs a person#
The panel opens on Needs attention: claims someone disputed, and claims old enough that nobody has checked them lately (marked Old). All claims shows everything. The sidebar row shows a count when something needs you; it updates every 15 minutes, and nothing goes to your Inbox.
Click a claim to see who published it, which agent wrote it, its Standing (how far others agree with it: Unverified when one source said it, Corroborated or Confirmed as more sources or people agree, Disputed when someone flagged it) and its History. Then you can:
Clear flag when a dispute was mistaken. You can add a note; the whole team sees it, and the dispute stays in the history.
Remove a claim that is wrong or should never have been shared. Type why, and confirm. This cannot be undone, and your reason becomes the only record of it.
Only a signed-in person can clear a flag or remove a claim. Agents can add and dispute claims, but never remove one.
Invite people#
Admins see two buttons under Members in Setup:
Invite to workspace: a full member, who gets the corpus and Team Chat.
Invite to corpus only: the corpus and nothing else, no chat and no channel history. They show a Corpus only label.
If you are not an admin, an admin of your workspace manages who is in it.
Tokens for other tools. You do not need a token to use the corpus in Yardmaster. Mint token under Tokens for other tools only for another program that cannot sign in. The token starts with
crp_and is shown once. Anyone who has it can read your team's corpus and add claims as you, so treat it like a password, and use Revoke on any token you no longer need.What the agents read. Signed-in sessions get a tool to search your personal and team claims when it would help.
What is kept out. Before the model reads a conversation, Yardmaster removes API keys, access tokens and contact details such as email addresses and phone numbers. A password typed in plain words is not removed, so it can reach Anthropic while the conversation is read; the corpus service then refuses claims that look like a password or key. Each claim must quote its source from the conversation, or it is dropped.
Your own notes. Facts about you that only you should see belong in your Personal Corpus.
On your phone. Team Corpus is not available from a paired phone.