How Ysra finds and uses your information

Ysra works only from information you give it or let it read: connected sources, your files, the web, your memories and what you write. This page matters when you want to know why an answer used something (or didn’t), or what to remove to make Ysra stop using it. It lists every source, where each is used, and how to remove it; how sources and citations look in an answer is on Sources and citations.

Reading is not acting#

Reading is not acting. Everything Ysra reads is information to reason about, never an order, and anything that would change something outside Ysra waits for your approval of the exact action.

Where information comes from#

Source	What it is	Where you manage it
Connected company sources	Slack, Jira and Gmail content from the integrations you connected. Kept up to date about every 15 minutes.	Integrations
Workspace files	Files you uploaded with + Upload files, indexed so their contents can be searched.	Files
The web	Web search, web pages and PDFs, read when needed.	The Expert’s Web research capability; a Worker’s Search the web and Check a URL grants.
Memory	Facts and preferences you asked Ysra to keep.	Memory
Experts’ instructions	The purpose and instructions you wrote for an Expert.	Experts
Your messages and attachments	What you type in Ask, files you attach to a question, and the brief you write for a Code thread.	In each conversation or thread
Rules & instructions	Conventions for Code work, such as “use pnpm”.	Rules & instructions

GitHub is a separate case. Its connection is kept on the web app’s Integrations page, and Ask cannot read or write GitHub. See GitHub.

Which sources Ask, Code and Workers use#

“Yes” means the source is used there.

Source	Ask	Code thread	Worker
Connected company sources	Yes. Searched when the question needs company context, and cited.	Through Hand to Code in the desktop app: the answer, with what it found, is handed to the thread.	Yes. Only the sources chosen under Company sources it may read.
Workspace files	Yes. Searched and cited.	Yes. Files are searchable in threads.	No. “Files in your workspace are not reachable from an agent — company sources only.”
The web	Yes, when the Expert has Web research.	Not covered on this page.	Yes, with the Search the web or Check a URL grant.
Memory	Yes, when the Expert has Memory.	Yes. Code threads read your memories.	Not covered on this page.
Experts	Yes. Instructions, sources and capabilities all apply.	Partly. Choose one under + → Expert in the message box. Only its name, purpose and instructions apply, fixed for the thread.	Not yet. Workers don’t use Experts today.
Your messages and attachments	Yes. Your question and attached files.	Yes. Your brief starts the work.	Yes. The job you describe becomes the Worker’s standing instructions. They cannot be edited later.
Rules & instructions	No.	Yes.	No.

A public Expert is narrower still: for a visitor, it reads only the files you chose for it, and the web if you allowed it; never your connected sources or your memories.

For Workers, see How Workers work and Start a Worker from Ask.

What may tell Ysra how to behave#

Tells Ysra how to behave	Is only information
Your messages	Slack messages, emails, Jira comments
An Expert’s instructions	Your files and attachments
Your memories	Web pages and PDFs
Rules & instructions for Code work	What the company search finds: it is “never treated as instructions”
A Worker’s standing instructions	Anything else Ysra reads

If a source contains text such as “ignore your rules”, it is treated as content, not as an order.

When Ysra wants to change something#

Where	What waits for your approval
Ask	Slack messages, Jira changes, and changes in services connected in Plugins: proposals you approve exactly. See Actions and approvals.
Workers	Sending mail and posting a chat message always stop for your approval of the exact text; this can't be turned off. See How Workers work.
Public Experts	Nothing: a public Expert can’t send or change anything.

What memory never holds#

“Credentials and retrieved company content are never stored.” Memory holds only the facts and preferences you asked Ysra to keep. It is not a copy of your Slack, Jira, Gmail or file content.

Removing information#

To remove…	Do this
A memory	Choose Forget on it in Library → Memory, or on the phone under Settings → “What Ysra remembers”. See Memory.
Slack content	Disconnect on the Slack card. See Slack.
Jira content	Disconnect on the Jira card. Its context is revoked. See Jira.
A Gmail mailbox used for search	Disconnect on that mailbox. See Gmail.
A Worker’s access	Archive the Worker. It stops running; its run history is kept. See Workers.
An Expert from a Code thread	Start the thread with No Expert. The choice is fixed once the thread starts.
A file from a public Expert	Take it out of Files a visitor’s question may read, then Save changes. See Public Experts.
A shared chat link	Revoke it in Share a read-only copy. See Sharing.

To disconnect GitHub, use Disconnect on the GitHub card in Integrations. See GitHub.

Sources and citations — adding each source, and how citations look.
Memory — what is remembered and how to forget it.
Actions and approvals — what happens when you approve a proposal.
How Workers work — what a Worker may read and do.