What's new

28 October 2026 · Ysra 3.20.0 · Web app 2.19.0 · Desktop 1.23.0 · CLI 1.15.0 · Mobile 1.10.0

Since 2.5#

Ysra 3.20, web app 2.19 and desktop 1.23: Code does what you ask#

Proportional work: small asks get small changes, “no tests” or “just the code” is respected, and every ending says what ran: “Ran: npm test (passed).” How a task ends →
Access modes: Auto runs commands; Asks first asks once per thread; a short list always asks. Access modes →
git on your computer: Ysra commits and makes branches itself, and asks before committing on main. Commit and push →
Cloud threads: secrets for the setup script only by default, daily limits per thread, and previews on a private link. Code in Ysra's cloud →
Ask keeps long conversations and reuses what it already found. Follow-ups →
GitHub: one-step connect, Disconnect, and Repositories on GitHub. GitHub →
A workspace of your own, made at sign-in if you have none. Workspaces →
Windows: the window fits small screens, zoom keys, and a tip for WSL. Ysra on Windows →
VS Code and Cursor: Ysra's own side bar icon; only selected code is attached. VS Code and Cursor →

Ysra 3.19, web app 2.18 and desktop 1.22: Views, Learn, and documents#

Views in Ask: charts, diagrams and small interactive pages inside answers; Save as View and Open the View. Views →
Learn: notebooks from your course files, free daily review, practice exams that mark your work, topics in planned sessions, and Learn mode in any Ask chat. Learn →
Documents: Word, PowerPoint and PDF files from Ask; “Now as slides” reuses the content. Documents and slides →
Upload checks: pictures in uploads are checked before they're stored. Files you can upload →
Deleting: a deleted workspace or account is erased after 30 days. Data, privacy and deletion →

Ysra 3.18: access modes, deleting, and the terms#

Access modes: Auto, Asks first or Read only, plus Plan first. Access modes →
Fewer questions: asking for the work is the go-ahead; Stop and Continue need no card. Changelog →
Delete and turn off threads, chats, Experts and Workers. Data, privacy and deletion →
Our terms and Report abuse. Acceptable use →
VS Code and Cursor extension. VS Code and Cursor →

Ysra 3.17, web app 2.15 and desktop 1.20: big builds finish, new emails, and plugins per workspace#

Big builds finish: large apps and very large files are built to the end, and a step that still runs too long says so plainly. Work is always saved; Continue picks up. A step runs too long →
Databases on cloud machines: PostgreSQL starts reliably when an app needs it, with nothing to set up. The machine’s life →
New emails: invitations, finished work, visitor questions and account emails are light and short, with links to ysra.ai and the docs, and no technical error text. Emails from Ysra →
iPad and Safari: Download and open in a new tab work for files in Ask, Library and cloud projects; notifications no longer stay on screen. Files →
Plugins per workspace: Settings → Plugins lists this workspace’s plugins, with an All workspaces badge on those used everywhere, and Show plugins from other workspaces shows the others; the same service can be a different account in each workspace. Plugins and workspaces →
Desktop workspace switcher at the top of the side panel, as on the web: switch, New workspace, Files & settings. The panel →
The effort you choose now applies to every model. Effort →

Ysra 3.16, web app 2.14 and desktop 1.19: one panel, Computer replay, and a browser you can drive#

One panel beside a Code thread, the same on the web and the desktop: Computer, Preview, Changes, Files and Progress, and + for a terminal, a phone-width preview or the report. Changelog →
Computer is always there: Ysra’s browser live while it checks your app, a replay of every step afterwards, and one or two screenshots on finished work, with See all steps. Changelog →
Drive the browser yourself (desktop): open any page, sign in, then Let Ysra drive and watch, or Take back at any time. Ysra never types passwords, and sending a form asks you first. Changelog →
Plugins and sources per workspace: each plugin is used in one workspace or all of them, and a workspace chooses its sources. Plugins and workspaces →
Long messages: paste up to 200,000 characters in Ask or Code, and the whole text reaches Ysra. Changelog →
Simple requests stay simple: “make a branch” runs as a few commands, and Ysra asks one question when a request doesn’t fit the folder. How a thread works →
Installs on your computer reach the package registries, and a blocked host is reported as Ysra’s own limit, never as a sign-in. Changelog →
Forge is the default for a thread you don’t pick a mode for, as its header says, and the model list has another choice. Build modes and models →
Ask answers “what can you do?” in a few lines and starts faster, and Set up with Ysra reads sites that live under a path. Set up with Ysra →

Ysra 3.15: what Ysra can do, a real browser, images, and supply-chain checks#

What Ysra can do: every tool, which part gets which, with examples and costs; ask Ysra “can you…?” and it answers from what is on in that conversation. What Ysra can do →
A real browser on any website in Ask, Experts, Code, Workers and Set up with Ysra: pages built with scripts, listings and maps read as a person sees them. Isolated, read-only, never your own browser. Ask →
Images in Ask and Experts, and two new Expert capabilities: Web browser and Images. Capabilities →
Code answers quick questions straight away, read-only, and tasks research the web in every run. What Code uses →
Workers browse and make files: the real browser with live watching, PDF reports, spreadsheets and images, attachable to an email you approve. Worker tools →
Dependency watch: a daily check of a repository’s packages; a compromised one is an alert at once. Dependency watch →
Mayz checks the supply chain: malicious and hijacked packages, known vulnerabilities, fresh incidents, cited. Supply chain →
Set up with Ysra finds your site by search, after asking, and saves your logo and photos. Set up with Ysra →
Code tasks end Done, Needs you or Didn’t work (3.14), and a faster, lower-cost model is the default for everyday building.

Ysra 3.13, web app 2.12 and desktop 1.17: Ask speeds, directions, and a fuller setup#

Auto, Quick or Thorough: choose how hard Ask works on an answer, or leave it on Auto and Ysra picks for each question; each answer says which. Auto, Quick or Thorough →
A speed on each Expert, and a public Expert on Auto answers Quick. Experts →
Directions to you: give an Expert a Location, and visitors who ask the way get a route that opens in their Maps app; a shared Google Maps link is understood. Directions to you →
Links in the website chat open with a tap. On your website →
Ask answers in your language, and a one-word message keeps the conversation’s language. Ask →
Set up with Ysra reads several websites, takes several files per document, and lets you change any part’s text before Start. Set up with Ysra →
Visitor questions per workspace: the workspace you have open shows its own Experts’ visitors. Visitor questions →
Code examples on the web open Code in Ysra’s cloud with the example in the box, and Code’s picker has a faster, lower-cost model for everyday changes. Start here →

Phone 1.9 and 1.10: Code, voice and cloud projects#

Code on the phone, beside Mayz and Ask, on a repository, a folder on your computer or a new cloud project. Mobile app →
Talk with Ysra by voice in Code, Mayz and Ask. Voice →
Publish or deploy a cloud project, and Notices when a deploy is live. Publish or Deploy →
Connectors and @: Microsoft 365, Linear, Notion and more, with live actions in Slack and Jira after your approval. Plugins →

Ysra 3.11, web app 2.10 and desktop 1.15: set up with Ysra, voice, and cloud projects#

Set up with Ysra: a short talk about your company proposes Experts, a public Expert, Workers, build ideas and documents to add; nothing is created until you press Start. Set up with Ysra →
Build ideas from the setup wait under Code’s start box; Start building writes one into the box. What Start creates →
Phone apps follow your phone: the Preview reads the Expo SDK of the phone that scans and offers Move to SDK N. Phone apps and the Expo SDK →
Preview any project without deploying, a site, a web app or a phone app, at a private address. Previews →
Talk with Ysra: voice in a thread, in Ask and on the start boxes, at about 12 credits a minute. Limits →
Cloud projects need no repository, and a website publishes on Ysra’s domain, private first. In Ysra’s cloud →
Ysra thinks about the product first and checks each must-have in the browser; a business site asks for your real contact details first, and work that wasn’t fully checked says why but is never blocked. How a thread works →
Workers stop at their spending limit for a run or a day, and say so. How Workers work →

Ysra 3.5 and web app 2.4: connectors, Microsoft 365, and Ysra Code#

Plugins: connect about thirty services in one click, your company’s own servers, any MCP server, and skills. Plugins →
Microsoft 365: mail, calendar, files, Teams and people; send mail with attachments after you approve it. Microsoft 365 →
Slack and Jira live actions: @slack and @jira search, read and post as you. Slack →
Every change is a card you approve, edit or decline. Actions and approvals →
Code in Ysra’s cloud: start Code on a GitHub repository from the web or desktop app. In Ysra’s cloud →
Mayz reviews: a verdict and findings, with evidence, that never change your project. Mayz reviews →
CLI 1.10: ysra mayz reviews a folder from the terminal, and ysra skills push sends your skills to the cloud. Command reference →
Build is now Code: the same work, under the name Ysra Code. Code →

Ysra 3.4: Build modes, and a refreshed look#

Early access: get an account with an invitation, or request a place. Get an account →
Windows: Build installs Node.js and Python by itself, as on macOS and Linux. Install tools →
Build modes: Spark, Forge or Summit sets the model and how hard it thinks, or pick them yourself. Build modes and models →
The desktop message box is one row, with Access (Asks first, Plan first, Full access) and the model in it. Start a thread →
A new Home in the web and desktop apps, a colour for each part, and Experts on the rail. Tour of the web app →
The command line prints into your terminal, with full screen as a choice. Keys →

Ysra 3.3: Workers inside Ask#

Start a Worker from Ask: describe the job, and a card under the answer says when it runs, what it reads and what it asks first. Start a worker from Ask →
Runs come back to the conversation, with a Workers · N panel beside it, a Workers table and an All runs page. Runs and approvals →
Notices: a bell with what your Workers did, and email for what needs you. Notices →
A report on each public Expert: what visitors asked and what it couldn’t answer. Public Experts →
Credit in any amount from $5 to $5,000. Billing →
Error reports that never include your questions, answers or files, with a switch in Settings. Settings →

Phone 1.8#

Notices: what your Workers finished, failed or stopped to ask, in the menu with an unread count. Notices →
Help in Settings, free. Ysra help →
Usage, People, Signed in on and Support access in Settings, and a Worker’s plan, read-only. Mobile app →
Ask: attach spreadsheets, see how long an answer took, and tap a mention to open it. Mobile app →
No Build on the phone: it runs on your computer. Build →

Ysra 3.2 and web app 2.0: Build runs on your computer#

Build runs in the desktop app and the CLI, on folders on your computer; the web app and the phone no longer start it. Build →
Deploy from your computer, with your own tools, after you say yes. Deploy from your computer →
The web app starts with Ask: Home is the question box, and Settings is one page. Tour of the web app →
Workers: edit one on the same screen you made it on, and see what each run looked at and found. Run details →

Ysra 3.1, web app 1.14 and desktop 1.9#

Ysra help beside the page: free, 20 questions a day, even with no credits left. Ysra help →
Start here: examples you can run, each saying what it needs. Start here →
Public Experts: let anyone with a link, or a chat button on your website, ask one of your Experts, within the limits you set. Public Experts →
More files read: scans, photos of documents, PowerPoint and more, up to 100 MB, and reading uses no credits. Files you can upload →
Ask starts with the same box as Build, with the sources to use under it. Ask →
Workers look the same in the web and desktop apps: plan a new worker as a dry run, then activate it. Create a worker →
Desktop: a folder without Git works as it is, and Where is one searchable list. Start a thread →

Build and Workers say what really happened#

A repository with no tests: Ysra checks the change itself and names what it ran, or says that nothing ran. It never reports checks as passed when none ran. A repository with no tests →
A declined request is tried another way once, then ends with a plain message. When a session stops by itself →
Stopping work that changed files asks whether to carry on, with Carry on. Stopping →
Workers: an approval nobody answers is withdrawn after 7 days, and a step Ysra didn’t do fails in its own words. Runs →
Ask: an answer missing the spreadsheet or PDF it owed says so. Spreadsheets →
Ask knows Ysra and your account: questions about using Ysra are answered from these docs, with the page linked, starting from what is in your way. Questions about Ysra itself →

Organisations#

Work with others: create an organisation, and its balance, plan and settings are shared; your conversations, threads and files stay yours. Organisations and roles →
Roles: Owner, Admin and Member, and a Billing switch for whoever pays. Organisations and roles →
Invite by email, and accept or decline an invitation in the app. Everyone starts with a workspace called My workspace. Organisations and roles →

Credits#

"Worked for 3m · 48 credits": Ask answers and Build work say how long they took, beside the credits that one stretch used. Credits and usage →

Workers#

A worker’s plan as a chart: When, Read, Do, Decide, Act and Deliver steps. Ysra drafts it, you change it and save, and every save is a new version. A run lights the chart up step by step. In the web and desktop apps. A worker’s plan →

Desktop 1.8#

A new sidebar: a rail of icons, with names on hover, and a panel beside it. Desktop app →
Local folders: Ysra keeps its own history of your changes outside your folder, never adds a .git, and never commits unless you ask. Open a folder →

Command line 1.6#

ysra exec runs one task to the end with nobody at the keyboard, for scripts and CI, with clear exit codes. Run Ysra from a script →
ysra ask in the terminal, with files: what the answer makes, such as a spreadsheet, is saved in the current folder. Commands →
Project instructions: AGENTS.md and CLAUDE.md in a folder are read as its instructions. Guide →

Command line 1.7#

ysra exec in containers installs what the work needs with the system’s package manager, ends when the work ends (unverified when not every check finished), exits with 4 when the task was declined, and stamps every stream-json line with the time. Run Ysra from a script →
ysra doctor shows where your sign-in was found. Tools, setup and Docker →
ysra auth token prints a short-lived access token from this computer’s sign-in, for scripts: FORGE_API_TOKEN="$(ysra auth token)". Run Ysra from a script →
Pick up a conversation: ysra --resume shows this folder’s threads to choose from, ysra --resume <thread> opens one, and ysra --continue opens the last. Commands →

Web app 1.11 to 1.13.0#

One layout: the thread layout is the only one. The Playbooks page is gone from Library. A tour →
The new sidebar, as in the desktop app: a rail of icons and a panel for the section that’s open. A tour →
A worker’s plan in the web app: Draft a plan, change the chart and Save plan. A worker’s plan →
Choose where a thread works from one searchable list: your devices and their folders, and your repositories, the most recent first. Where →
Help: Ask Ysra answers questions about using Ysra from what your account has, and Get help sends a conversation to the Ysra team. Ysra help →
Get the apps: the desktop app, the command line and the phone, from the foot of the rail. Install the desktop app →
A paused thread says why under Needs you: built but not verified, stopped before it finished, or at its budget. How a session can end →
A reply that couldn’t do what was asked is a warning card saying what to fix, and a setup question can be answered with I’ve done it, Show me how or Not now. Changelog →

Ysra 2.5.0 (9 October 2026)

9 October 2026 · Ysra 2.5.0 · Web app 1.8.0 · Desktop 1.5.0 · CLI 1.5.0 · Mobile 1.6.0

Credits and billing

Credits are the one unit for threads, Workers, Machines and Ask, and every app shows what's left and what used them. Credits and usage →
500 free credits once your email address is verified. Free credits →
The Usage page charts credits used per day, split by kind of work, and lists what used them. See your usage →
When credits run out, Ysra pauses before its next step, keeps your changes and continues when you tell it to. When credits run out →
Plans: Starter, Pro, Max, and Team by the seat, each adding credits every month. Start, change, cancel and resume in Billing. Plans →
Extra credits in packs, kept until used. Extra credits →
Several payment methods, with a default. Payment methods →
Automatic top-ups add a pack when the balance runs low, up to a monthly limit you set. Automatic top-ups →
Invoices for every payment, each with a PDF. Invoices →
Billing in every app: everything in the web and desktop apps, and ysra usage and ysra billing in the terminal. Billing in each app →

Ask

Answers can be spreadsheets: an Excel workbook or a CSV, with formulas, charts and a Sources sheet. Spreadsheets →
Attach spreadsheets: .xlsx and .csv files, read sheet by sheet. Attach a spreadsheet →
Change a spreadsheet from an earlier answer — add charts, rows or a dashboard sheet — and everything already in it is kept. Change a spreadsheet →
The request sets how deep research goes: ask for 50 companies and Ysra keeps going until it has them, says how many it reached, and doesn't make any up. How far research goes →
Hand to Build and Automate this say what they would do for each answer. A Worker made from an answer stays linked to it and can update its files. Turn an answer into work →
@ mentions point Ysra at your files, conversations, Build threads, Workers and Experts. They're read, never run. Mention your own things →

Signing in

Support access is listed under Signed in on, each time Ysra support looked at your account, read-only. Support access →

Ysra 2.3.0 (7 October 2026)

7 October 2026 · Ysra 2.3.0 · Web app 1.7.0 · Desktop 1.4.0 · CLI 1.4.0 · Mobile 1.6.0

Signing in

Sign in from your browser: the desktop app and the command line open the web app, and you choose Allow; they never see your password. Sign in →
Over SSH, ysra login prints a code to enter in the web app. Without a browser →
Signed in on lists every app signed in to your account, with Sign out and Sign out everywhere; ysra sessions and ysra logout in the terminal. Where you're signed in →
Forgot password? mails a one-hour link, and resetting signs every app out. Forgot your password →
New accounts verify their email with a link that lasts 24 hours. Verify your email →

Workers

Workers can be edited after creation: name, instructions, access and schedule. Each save is a new version, and runs already started keep their instructions. Edit a worker →

Experts

A new Expert starts with all nine capabilities, in every app. Experts →

On your phone

The option chips — Build or Plan first, model, effort and Expert — at the start and inside a thread. Mobile app →
Start on a device's folder from the Folder or repository picker.
Open and edit Workers on the phone: name, description, instructions and schedule. Workers on the phone →

Ysra 2.2.0 (7 October 2026)

7 October 2026 · Ysra 2.2.0 · Desktop 1.3.0 · CLI 1.3.0 · Web app 1.6.0 · Mobile 1.5.0

Since the last release, Ysra looks after fleets of machines, acts on its own within limits you sign, and puts work live on your own servers. Each line below links to the page that explains it. For a real run from start to finish, read the walkthrough.

Ysra (the service) 2.2.0

Targets are now machines, managed through a gateway that keeps their addresses and keys. Machines →
Gateways reach many machines from inside a network, and you can import hundreds from a spreadsheet. Machines and gateways →
Approvals signed ahead of time let agreed kinds of change run on named machines without asking at each step. Approvals and automatic runs →
Runbooks run on many machines at once, on a schedule, with a dry run on each first. Runbooks →
Investigate and fix: when a check fails, Ysra fixes it only from the runbook's If it fails or a document it found, and names the source. How it works →
Fixes come back to the runbook: a fix learned from a document is offered as the step's new If it fails. Keep the fix →
Write a file on a machine, approving the diff, with the old file kept. Write a file →
Deploy a folder to a machine, seeing every file before it goes, with the previous version kept. Deploy a folder →
Deploy a site to your own server, from the build to a page that answers. Deploy a site →
Options change mid-thread: model, effort and plan-first apply from your next message. Start a thread →
No more autonomy choice: Governed and Max are gone, and every thread works the same way.
Questions wait for you: when Ysra ends on a question, the thread shows Needs your input instead of stopping. Ask and change →

Desktop 1.3.0

No start dialog: type on Home, press Enter, and the thread starts. Start a thread →
Options as chips under the message box: where, Build or Plan first, model, effort, Expert, branch. Start a thread →
A new sidebar: Devices at the top, threads by Time, Folder or Device, and New thread on… (Cmd+N). Ysra Desktop →
Settings is a page, with Accounts, Approvals and Appearance. Settings →
The Machines panel in a thread: health at a glance, search, select, run, and every command's output. The Machines panel →
The Machines page lists every machine in the workspace. Machines →
Copy on every message, answer, code block and output. The working timeline →
A file view with a folder tree and Open in editor. Review the diff →

CLI 1.3.0

ysra machines replaces ysra target, which still works. Command reference →
ysra approvers decides which signed approvals a gateway honours. On the gateway →
/machines, /runs and /approvals show machines, runs and approvals in a gateway thread. Command reference →
/settings and /model apply mid-thread, from your next message. Work in a folder →

Web app 1.6.0

A Runbooks page to write, draft from a document, and version runbooks. Machines and gateways →
New thread is a message box with chips, the first being Folder or repository, which also lists device folders. Start a thread → Machines and gateways →
Runs, approvals and schedules in threads; approvals are signed in the desktop app. Approvals →

Mobile 1.5.0

A Machines sheet in gateway threads, with each machine's findings and commands. Machines and gateways →
Approvals listed, with Withdraw; signing stays in the desktop app. Withdraw an approval →
Machines need you in the inbox when a run left machines for a person.

How to update

	How
Desktop app	Settings shows Version 1.3.0 is available · Download
CLI	`ysra update`
Web app and phone	Nothing to do

ysra target … keeps working, and nothing you set up before needs changing.

The previous release: Desktop 1.1.1 and CLI 1.1.1 (4 October 2026)

Windows: the desktop app and the CLI run on Windows. Safe read-only commands run without asking; other commands show a card, or run contained inside WSL.
Allow for the session covers a whole program, such as every npm command.
Run commands without asking for one session, with a warning first.

See the changelog for Desktop and CLI 1.1.1.

Full changelog →