MeshTale files what your people and agents produce into organization, workspace, collection and memory, so every answer comes from the right place and nowhere else.
Free tier, no card required.
The structure is small on purpose. The boundary sits at the workspace, defaults sit at the collection, and the rules for who may see something travel with each memory.
Your company. It holds every workspace and the people in them, and it is where organization-wide rules are set.
Every agent connection is bound to a workspace. Ask from outside it and the answer is a refusal, not a filtered result. The attempt goes in the audit log either way.
Claude Codebound to Northwind 
Dana·account team
Northwind MSA v3by 
Priya·confidentialBilling fix: proration rulesby Claude Code·session
Brand refresh briefby 
Sam·internal
Delivery plan Q3by 
Codex·session
Escalation policyby 
Marco·internalLeave legacy billing aloneby Cursor·agent memoryShared connections belong to the workspace, so the team and its agents can use them. Personal connections stay yours: your mail and your notes, visible only to you.
Connected once for Northwind. Everyone on the team can recall from it, and so can agents bound to Northwind.
#northwind-kickoffSlack, approved channelvisibleNorthwind client driveGoogle Drive, selected foldersvisible
NW projectJira, issues and commentsvisibleThe team and Northwind agentsConnected by Dana for herself. Her own assistants can use it, and nobody else on the team can see it.
Dana's inboxGmail, email threadsvisibleDana only
Dana's mailboxOutlook, email threadsvisibleDana only
Dana's notebooksOneNote, sections and pagesvisibleDana onlyDana and her own assistantsPeople write memories through the tools they already use. Agents write them too, from coding sessions, summaries and their own notes. Either way, each one keeps its author, its source and its rules.
Dana·Granola callHumanApprovedNorthwind renews for twelve months on the current plan. Onboarding for their new support team is included, with Dana as the named contact.
Session: invoice export fixby Claude Code·coding sessionAIIn reviewExports now round per line, not per invoice, to match Northwind's accounting. The old rounding is kept behind a flag for March reports.
Usually one per client, plus one for your own team. The workspace is where the boundary lives, so anything that must never reach another client's agent belongs in its own.
A collection is a folder inside a workspace, such as client comms, contracts or delivery. Each one has its own sensitivity default, so a contract lands guarded without anyone remembering to label it.
No. Every agent connection and API key is bound to one workspace. A request for another workspace is refused rather than filtered, and the attempt is written to the audit log.
Yes. People belong to the organization and can be members of the workspaces they work on. What they and their agents can recall still depends on the workspace and on each memory's audience.
A shared connection, such as a client channel or drive folder, belongs to the workspace and serves the whole team. A personal connection, such as your own inbox or notebook, is visible only to you and your own assistants.
Yes. Each memory keeps who added it and where it came from, whether that is Dana's call notes or a Claude Code session, and that shows on every citation.
Create a workspace, connect a source, and ask your first question.
Free tier, no card required.
