Quickstart
Create an account, ask your first question with sources, then install the desktop app and make your first checked code change — in about ten minutes.
On this page
This quickstart takes you from a new account to two results: an answer from your own files, and a code change Ysra made and checked in a folder on your computer. It's for anyone trying Ysra for the first time.
Before you begin#
Make sure you have:
- an email address for your Ysra account;
- a file you'd like to ask about (a PDF, a Word file or a spreadsheet);
- for the code part, a computer running macOS, Windows or Linux, and a folder with code in it (a Git repository is best, but any folder works).
Only want one part?
- Coding in your terminal: start with the CLI quickstart.
- Coding in your editor: see VS Code and Cursor.
- Studying: go straight to Learn.
Step 1: Create your account#
Go to app.ysra.ai and create an account, or open the invitation a colleague sent you. Verify your email address: a new account gets 500 free credits once its address is verified.
The first time you sign in, Ysra offers Set up with Ysra, a short, free conversation about your work that proposes colleagues and routines for you. You can skip it and come back later.
Step 2: Ask your first question#
- Open Library → Files and choose Upload files, or drop a file on the page.
-
Open Ask and type a question about it:
What are the three biggest risks in this contract, and on which page is each? -
Read the answer. Each claim links to its source: click one to see the passage it comes from.
Try a follow-up that turns the answer into something you can use:
Put those risks in a table with what we could do about each.
Make that a one-page Word document I can send to the team.
See Ask a question for sources, speeds and deep dives.
Step 3: Install the desktop app#
Code on your computer runs in the desktop app, the CLI or the VS Code extension. This quickstart uses the desktop app.
- Download it for your system from the install page.
- Open it and choose Sign in to Ysra with your browser, then Allow in the browser, and return to the app.
Step 4: Start a Code thread#
- In the desktop app, open Code.
- Click the folder on the line under the message box (it reads Choose a folder… the first time), then Other folder…, and pick your project. Sending your first message trusts the folder on this computer.
- Check the Access chip. Leave it on Asks first for now: Ysra will ask before each command and change. See Access modes.
-
Ask a question first, to see how Ysra reads your project:
What does this project do, and how do I run its tests?
Step 5: Make your first change#
Describe the outcome you want, not the steps:
Add input validation to the signup form: reject empty names and invalid
email addresses, with a clear message for each. Add tests.
Ysra plans the change, edits the files, and runs your project's own checks: install, lint, tests and build. Approve each step it asks about. You can steer it with another message, or stop it at any time; work done so far is kept.
Step 6: Review and keep the change#
When the work ends, open the side panel:
- Changes shows the diff, file by file. You can comment on a line to ask for a change.
- Report shows which checks ran, which of your requirements are met, and the credits used.
The thread ends with Your changes are ready, and one line that says what
Ysra ran to check it, such as “Ran: npm test (passed).” If the project's
checks fail, it ends Didn't work and says what failed. Either way, the
change stays in your folder. To keep it:
Commit this on a new branch and push it.
Ysra shows a card for the push and waits for your OK.
Tips for good results#
Be specific. Instead of “fix the bug”, try “fix the login bug where users see a blank screen after a wrong password”.
Say how you'll know it's done. “Done when the checkout test passes and the total includes tax” gives Ysra something to check against.
Explore before you change. In an unfamiliar project, start in Read only and ask questions, then switch to Asks first to make changes.
Turn on Plan first for big changes. Ysra writes a plan and waits for you to approve it before any code moves.
What's next#
- How Ysra works — the loop every change goes through.
- Code in Ysra's cloud — work on a GitHub repository while your computer is off.
- Views and Documents and slides — answers you can see and send.
- Routines — have a job done on a schedule.
- Troubleshooting — if something doesn't work.