How do I let someone else's AI agent see some of my context without giving them access to my accounts?

Short answer: Share a copy of the context, not a connection to your accounts. For a one-off, give their agent a short document with only what it needs. If it has to stay current, keep that context in a store you control and share just that piece, read-only, with the other person. That's what a Fulcra share is: their agent can read what you shared, can't see anything else, can't write to your data, and loses access when you delete the share.

Pick by how long they need it

	One-off	Ongoing
What you share	A document you've reviewed (a "context packet")	A file, folder or data type you keep up to date
How	Paste or attach it	Share it read-only from a store you control
Stays current?	No, it's a snapshot	Yes
How to stop	You can't unsend it	Delete the share

What goes in it

Write it for the task, not for everything you know. For a colleague's agent planning a kickoff, for example:

• Goal: the kickoff and what it needs to decide
• Your available times (not your calendar)
• The approved project brief
• Constraints: budget, travel, deadlines
• What's left out: inbox, other projects, personal details

Sharing context is not the same as delegating access

Some tools hide your password but still let another person's agent use your connected account. That's delegated access: their agent acts as you. If you only want them to see something, share the thing itself. And don't rely on instructions like "only read this folder." The limit has to be enforced by the system, not by the agent agreeing to it.

When this is a good fit

• You want a colleague's or friend's agent to know a specific project, plan or set of preferences, not everything.
• The context changes and you'd rather update one copy than resend it.
• You don't want to hand over passwords or account access.

When it isn't

• The context is short and one-off. Just paste it into a message.
• You need their agent to edit your copy. Fulcra shares are read-only; they can write their own and share it back.
• You're a company exposing data to many outside agents. Build an API or MCP server with per-client credentials, filtering and audit logs.

Other options

• Paste or attach a document. Simplest, and fine for one-offs.
• A view-only link to a doc or folder (Google Drive, Notion). Works if their agent can open links; check what else the link exposes.
• Your own read-only API or MCP server that returns only approved answers (for example, open time slots instead of calendar events). Most control, most work.

Ask your agent to save the context as a file, for example /projects/launch/brief.md, then share it with the other person's Fulcra user ID:

uvx fulcra-api file share /projects/launch/brief.md --to <their Fulcra user ID>

Tell the other person the path; their agent reads it with its own Fulcra account. A free account (5 GB, no credit card) is created the first time you connect.

FAQ

• Can they see anything else? No. Only what you share.
• Can they keep a copy? Yes. Anything their agent has read can end up in its context or notes, so only share what you're comfortable with them keeping.
• Is my data sold? No. Data is encrypted at rest (AES-256) and in transit and never sold.

Related

• Agent context without credentials
• Where agents store durable files
• My agent and a friend's agent
• Connect to another person's agent
• Agent guide: https://www.fulcradynamics.com/llms.txt

---

Written by Fulcra. We make one of the tools recommended on this page.