Security
How Ysra protects your code, files and accounts, what always waits for your approval, and the settings you control — for Code on your computer, cloud threads, Ask, routines and machines.
On this page
This page is for anyone deciding whether to let Ysra work on their code, files or servers, and for the people who review that decision. It describes what Ysra protects and what you control. For the controls that apply across the whole product, see Boundaries and safety; for what happens to your data, see Data, privacy and deletion.
How Ysra approaches security#
Ysra is built around one rule: you set the scope before work starts, and anything that leaves your control waits for you. A push, a deploy, an email, a Slack message or a change on a server shows you the exact content or command first, and runs only after you approve it.
Access modes#
Every Code thread has an access mode. You choose it when you start the thread and can change it at any time from the thread's header.
| Mode | What Ysra may do |
|---|---|
| Auto | Works through without asking, running commands and committing on its own branches. Still asks before the actions below. |
| Asks first | Asks once per thread before commands that reach outside the folder or change git. This is the default for a new thread until you pick another. |
| Read only | Reads and explains. Changes nothing. |
Plan first is a separate switch: Ysra writes a plan for you to approve before it makes any change, whatever the access mode. See Access modes.
Auto is for projects you trust
In Auto, commands run without a question. Use it on code you know. The actions below still ask.
What always asks you first#
No access mode skips these, not even Auto:
| Action | What happens |
|---|---|
| Install software on the system | Asks, showing what will run. |
| Overwrite files or work Ysra didn't make | Asks, showing the exact command. |
| Delete a file | Never, for a file Ysra didn't create. One it created in the task, unchanged since, only after asking. |
| Change a place that starts programs by itself | Never: shell start-up files, login items, scheduled jobs, Git hooks and the like. Ysra gives you the line to add yourself. |
| Destructive git, such as discarding changes or deleting a branch | Asks. Ysra never rewrites commits it didn't make. |
| Push to the default branch | Asks every time. Ysra never force-pushes. |
| Deploy, publish or create a cloud resource | Asks, showing the exact command. |
| Send an email, post a message, change a ticket | Shows the exact text; you approve that text and nothing else. |
| Change anything on a machine or device | Asks, unless you signed an approval for that kind of change in advance. |
| Sign in to a service | Never done by Ysra. Signing in is always yours to do. |
In Auto, Ysra may commit on a branch it made or on your current branch when it isn't the default branch, and push a branch it made; see git on your computer. It doesn't rewrite your Git history, delete branches or tags, or run as an administrator.
A script Ysra runs inside your project, such as tests or a build, can still delete project files; undo brings them back. See What always asks.
On your computer#
When you use Code in the desktop app, the CLI or the VS Code extension, the work happens in your folder, on your computer.
- Your folder stays where it is. It isn't uploaded as a whole. Only the parts of files Ysra reads for the task, and the output of commands it runs, are sent to do the work.
- Commands are contained to the folder. On macOS and Linux, commands Ysra runs can write only inside the folder you opened, and can't reach your secrets or your other files. If containment isn't available on a computer, Ysra doesn't run commands there.
- Secret files are never read. Environment files such as
.env, private keys, SSH and signing keys, and the sign-in files of cloud and package tools are off-limits. Add your own patterns to.ysra/denyin the folder; see Keep more files from Ysra. - Undo is exact. Undo puts back the files Ysra changed, exactly as they were, and leaves your own edits alone. If it can't do that precisely, it refuses rather than guess. Ysra keeps its record of the work outside your folder, so your Git history isn't touched.
On Windows
Commands aren't contained on Windows itself, so Ysra asks before each one that isn't a safe read. Run your project inside WSL to get the same containment as on Linux. See Ysra on Windows.
In Ysra's cloud#
A cloud thread works on its own copy of your repository, on a machine of its own, never on your computer.
- Isolated machines. Each thread gets its own machine. Threads can't see each other.
- Limited internet. A cloud machine reaches your code host and your project's package registries, not the open internet.
- Credentials stay out of the work. The code running on the machine never holds your GitHub access.
- Secrets for setup only, by default. A cloud environment's secrets are available to its setup script only. You choose, secret by secret, whether Ysra's commands may read one too. See Secrets.
- Private previews. Previews open through Ysra on a private link; the machine's own address isn't public. Nothing is public until you choose to publish it.
- Limits. Cloud work has daily limits per thread and stops when your credit runs out.
- Cleanup. A paused machine is removed after its work ends; the files of the thread are kept.
See Code in Ysra's cloud.
Ask, colleagues and routines#
- Sources you choose. Ask reads only the sources a conversation is given: your files, the web, and the tools you connected. A routine reads only the sources listed on it.
- Content is information, not instructions. Text in a document, a web page or an email is treated as data. It can't change what Ysra is allowed to do.
- Public colleagues are walled off. A public colleague reads only the files you publish with it, and the web if you allow it. It never reads your connected tools and can't send or change anything.
- Approvals for everything outgoing. Emails and posts from a routine wait for your approval of the exact text, on every run.
- Uploads are checked. Files you upload, and the pictures inside documents and slides, are checked for unsafe content before Ysra uses them.
Connections and credentials#
- Tokens for GitHub, Slack, Jira, Gmail, Microsoft 365 and other connections are stored encrypted and are never shown to the model.
- You can disconnect any integration from Settings → Connectors. Ysra stops using it at once.
- Connected servers you add yourself must use a public HTTPS address.
- Ysra uses your SSH keys and command-line sign-ins where they already are on your computer or gateway. It never asks for or stores a password.
Machines and devices#
- A device connects out. No port is opened on it, and its sign-in reaches that device's work and nothing else.
- Your servers stay private. A machine's address, user and keys stay on the gateway that reaches it. Ysra's servers know only its name and labels.
- Every change is approved by a person, one at a time, or ahead of time with a signed approval you create for named machines and kinds of change.
- Every command is logged on the gateway with who approved it and how it ended.
Your account#
- See every place you're signed in, and sign any of them out, under Settings → Signed in on. If the Ysra team ever accesses your account to help you, that access is listed there too. See Sign-in and sessions.
- Owners and admins decide who joins a workspace and what they can change. See Workspaces and members.
- Your prompts, code and files aren't used to train shared or public models.
Security best practices#
For your own work
- Start new projects in Asks first, and move to Auto once you trust how Ysra works in that project.
- Read the diff before you commit or push. Use Read only to explore code you don't know yet.
- Add anything sensitive that isn't already protected to
.ysra/deny. - Turn on Plan first for large or risky changes.
For teams
- Set the autonomy policy for your workspace so every Code thread follows the same rules.
- Give the Admin role only to people who manage members and settings, and the Billing switch only to people who pay.
- Review connected integrations from time to time and disconnect the ones you no longer use.
Warning
These protections reduce risk; they don't remove it. Review what Ysra proposes, especially commands and changes to production systems.
Reporting a security issue#
If you think you've found a vulnerability in Ysra, don't disclose it publicly. Contact the team through the security contact form with the steps to reproduce it, and give us time to fix it before you share it.
The same form is the way to request a security review: the team walks your security team through data flows, isolation and the audit trail for the work you plan to do with Ysra.
Related#
- Boundaries and safety — the guarantees behind every part of Ysra.
- Access modes — Auto, Asks first, Read only and Plan first.
- Data, privacy and deletion — what is kept, for how long, and how to delete it.
- Acceptable use — the rules for using Ysra.
- Autonomy policy — workspace rules for Code threads.