Changelog
What changed in each Ysra release. Ysra follows semantic versioning.
On this page
Ysra follows semantic versioning, and Git tags use the matching vX.Y.Z form.
Routines were called Workers and colleagues were called Experts in earlier releases. These notes use today's names.
Current versions#
| Version | How to check | |
|---|---|---|
| Ysra (the service) | 3.39.4 | — |
| Web app | 2.53.0 | — |
| Desktop app | 1.23.1 | Settings footer, or About Ysra |
| CLI | 1.20.0 | ysra --version |
| Mobile app | 1.10.0 | The foot of Settings, under Sign out |
Update the desktop app or the CLI.
3.39.1 to 3.39.4 — A new look for your team, meetings, and repositories from anywhere#
21 November 2026
Ysra 3.39.1 to 3.39.4 · web 2.50.1 to 2.53.0.
New
- A new look for your team. Every colleague has a new face from one Ysra family, with their own colour and something they wear. The face shows at a glance whether a colleague is ready, working on it, needs you, or done. You see it in the app and on ysra.ai.
- Your calendar in Ask. Ask what's on your calendar, and Ysra answers from your connected Google Calendar. See Plugins, connectors and skills.
- Keep a meeting to your team. One switch keeps a call to just your team.
- Ask about your work during a call. In a meeting, ask Ysra about your Work board and how your goals are progressing.
- Add a repository from anywhere. Wherever you pick a repository, you can connect GitHub or GitLab, paste a git link, or start an empty project. See GitHub.
- Rename a colleague after hiring.
Improved
- One repository picker everywhere. It is searchable, shows your recent repositories first, groups them by source and uses their real names. Rename a project right where you pick it.
- Meetings. Ysra stays in the language you're speaking, speaks in the call, and leaves when you ask. When it can't read something it needs, it says exactly why.
- Colleagues keep up with you. Turn on a skill for a colleague and they can use it straight away, even in a conversation already started. When something is switched off, they name the exact switch, such as Nova → Skills → MCP servers. See Choose what a colleague can use.
- A colleague's computer starts more reliably.
- Team setup proposes and hires a larger team in one go. See Company.
- One workspace on screen at a time. Switching workspace takes you to that workspace's lists, team and company. A link to something in another of your workspaces opens it there, with a short notice. Runs, goals and memories belong to their workspace. See Workspaces and files.
- Home loads smoothly on every device.
- Asking Ysra for Chrome about a page answers reliably.
Security
- Stronger access controls across workspaces.
- Stronger safeguards on the links a colleague opens when work is handed from one colleague to another.
3.39 — Ysra staffs your company, colleagues per plan, and Ysra for Chrome#
20 November 2026
Ysra 3.39.0 · web 2.50.0.
New
- Ysra staffs your company. Describe your business in one line and Ysra proposes departments, their leads and the right number of colleagues: a small business gets a small team. Untick anyone you don't want, then hire everyone in one click. Each colleague lands in their department on the Team map.
- Files your company will need. Beside the team, Ysra lists up to 10 documents your company will need, such as a price list, contracts, a security policy or case studies. Each one is marked as already in your workspace or missing, with Add it.
- Ysra for Chrome, rolling out on the Chrome Web Store. Ysra opens in a side panel beside any page. Ask about the page you're on: Ysra reads it only when you press send. Or right-click and choose Ask Ysra about this.
- Help improve Ysra. The apps count which features are used, never what you write, your files or the pages you visit. Turn it off in Settings → General. Enterprise workspaces are never included.
Improved
- Colleagues per plan. Free has Ysra only, Starter includes 10 colleagues, and Pro, Max and Team have as many as you need. The room left on your plan shows before you hire. See Hire and shape your colleagues.
- A cleaner Settings. Every Settings page has one layout, in light and dark, and in Arabic. See Settings.
Security
- If a connected tool changes, Ysra tells you before you approve its next action: “This tool changed since you reviewed it.” See What Ysra may do with it.
- Stronger safeguards on what Ysra reads and opens when it works with web pages, emails, connected tools and a colleague's computer.
3.38 — Memory you can see, a new message box, and editing your own messages#
19 November 2026
Ysra 3.38.0 · web 2.49.0.
New
- Memory you can see. When an answer saves, updates or forgets something about you, a line at its top says so: “Saved to memory”, “Memory updated” or “Forgot: …”. Open it to see each change (an update shows the old words and the new ones), whether it is used in every workspace or this one only, with Undo and All memories. See Memory.
- Save to memory? When the words didn't clearly come from you, or the answer read something from outside (a web page, an email, a forwarded message), Ysra asks instead of saving, with Save and Not now. Nothing is kept until you choose. Something about your private life, such as getting married or moving house, is always asked first, unless you asked Ysra to remember it in that message.
- Library → Memory shows where each memory was learned (a link to the conversation, or “Added by you”), where it is used and its date, with Edit and Forget.
- Edit, retry and copy your own messages. Under a message you sent: Retry, Edit and Copy, and when you sent it. Edit changes the words and asks again from that point; Retry asks the same message again. Earlier versions are kept: switch between them with ‹ ½ ›. See Ask.
- A new message box. It starts two lines tall and grows as you write. + holds attaching files and the options, such as Learn mode, and the microphone, voice and send buttons sit together at the end. The number of free quick answers left shows only when few are left.
Improved
- Every colleague keeps your memory. Ask any colleague to remember something and it goes into your memory, which Ysra and every colleague read. A colleague's Memory switch is now Own notes: with it on, the colleague also keeps notes of its own from your conversations.
- In a team conversation, something about you (a fact, a preference, something to remember or forget) goes to Ysra, unless you address a colleague or it is clearly that colleague's work.
- Ysra understands your company first. “The product”, “the launch” and your company's name mean your business, whatever it is called, and plans for it are your company's next steps, not software to build.
- Every answer knows today's date, so plans and deadlines start from today.
- “go” after a plan does its next step, in the language you are writing in, instead of writing the plan again.
- Answers follow the language of your latest message, the first message of a conversation and short messages included. The conversation's title is written in that language too.
- Hiring from a request reads the role from your words, and asks once more when there is none. A hire is offered only for work none of your colleagues already does.
- What the team knows about us takes a decision from a conversation only when you state it plainly, never from a short reply or a correction, and it waits until an owner or admin keeps it.
Fixed
- A hire draft that doesn't work says so in your language, instead of a general error.
Security
- A memory is saved by itself only when it comes from your own words in the conversation and the answer read nothing from outside; otherwise it is only proposed. This holds for an edited or retried message too.
- In an Enterprise workspace, what is learned there stays in that workspace. Changing a memory you keep for every workspace makes a version for that workspace and leaves the original as it was.
3.37.1 to 3.37.3 — Fewer approvals on a colleague's computer, result cards you can act on, and old Excel files#
18 and 19 November 2026
Ysra 3.37.1 to 3.37.3 · web 2.48.0.
New
- Approve all on this site for this task. When a colleague's computer asks before sending or publishing on a site, a second button approves that kind of step on that site for the rest of the task. Payments, uploads and deletions always ask. See Let a colleague use a computer.
- Result cards you can act on. The steps on a result card have real checkboxes, kept with the answer, and a count such as “2 of 6 done”. Add to Work board makes one task per step, and Make it a goal makes a company goal measured by the steps you tick. Copy as text copies the card as plain text, ready to paste into an email, a document or WhatsApp. See The result card.
- Old Excel files (.xls) are accepted everywhere you can upload an .xlsx file, and read the same way.
Improved
- A colleague's computer asks only for what leaves. Opening, reading and clicking through pages no longer asks for your OK. A step you approved isn't asked again in the same task; a send is asked each time.
- A colleague can double-click to open an item in a file list, such as a folder in Google Drive.
- A link into one of your apps, such as a Google Drive folder, offers that app's Connect card.
- Files from earlier in the conversation that Ysra reads again keep their sources, so the answer cites them.
- When an answer can't run calculations (on the Free plan, or a Quick answer), it gives only figures your files show, never totals or trends it didn't work out, and says the exact calculation needs the Starter plan or Thorough.
Fixed
- A refused upload says why in your language, instead of a general error.
- The same click on a page no longer asks for approval again and again.
Security
- Approve all on this site covers only the site and the kind of step you approved, and is never offered when the page shows an amount or a file is attached.
3.37 — Teams and the Team map, exams, missions and dashboards#
18 November 2026
Ysra 3.37.0 · web 2.47.0 · CLI 1.20.0. Ysra 3.36.3 to 3.36.5 went out earlier the same day and are included here.
New
- Departments and teams. Group your colleagues into departments and teams, up to four levels deep. Each team can have a manager colleague, people who approve its work, and a limit on what its colleagues do alone. A manager splits work for their team, hands the pieces down and reviews them before the answer comes back. See Team map.
- The Team map (it was called How it runs). Departments and teams are frames you move and resize; drop a colleague in a frame to put them on that team. Each card shows the colleague's level and the apps they work with, with a missing connection marked. What's happening lists what waits for you, with Approve and Not now.
- See the run. An answer that handed work to the team links to its run on the Team map, where you can replay it step by step: who handed what to whom, what was approved, and what came back.
- Exams for colleagues. Build a test set from your company's own examples (answers they gave you, actions you approved, routine runs, questions drawn from a document, or your own), keep part of it hidden from the colleague, and run the exam. A pass offers the next level, Ask → Approve → Auto, and the colleague moves up only when you say yes. See Exams.
- Missions on goals. Give a company goal to a colleague as a mission: what counts as success, a credit budget, what needs your OK first, and how often you hear back (only when something blocks, daily or weekly). Work starts only once you agree. Each round of work is read by an independent check against what counts, and the goal's number moves only when you confirm it. See Missions.
- Ysra understands what you need first. Ask a big brief, such as connecting your sales tools and getting a dashboard by brand, and Ysra maps each point to its own steps, proposes a plan and asks at most a question or two, instead of offering to build custom software. The plan comes with cards to act on it: Connect an app, set up a routine, or open a page. See Plans and cards.
- A result card under answers. When an answer comes to something (a verdict, a score, a comparison or table, actions with owners, or key figures), it shows as a card under the words, with its sources and Copy.
- Dashboards made of blocks. Make a dashboard from blocks: a pinned View, a table's figures, a goal's progress, a note, or a block Ysra or a colleague builds from a request. Arrange and resize the blocks, share a dashboard with the workspace, or use one as your Home (My dashboard). See Dashboards and pins.
- Ask about a dashboard. A dashboard has its own chat: ask Ysra or a colleague what changed, or ask them to add a chart, resize a block or rename it. Each change shows under the answer with Undo.
- Dashboards that look like dashboards. Ask for a dashboard in Ask and you get key figures with their change, real charts and filters, and “No data yet” with what is missing, never invented numbers.
- Business Central can be connected by invited pilot customers, from Settings → Connectors. Every change it would make asks you first, and tools that delete are never offered.
Improved
- Eight pins. You can pin up to eight Views (it was five). Pins and dashboards sit on the sidebar's Pinned shelf, and a new pin says where it went.
- Hire from anywhere. Hiring opens over the page you're on, and you stay there. In the company setup, Hire all hires the suggested colleagues at once, and says first if your plan has room for fewer.
- The sidebar reads Home, Company, Work board, Team, then Library, Learn and the rest.
- What the team knows about us is the new name of the company wiki. Each page has a hint and an example to borrow, and your own lines come first.
- A routine's page lets its maker change who runs it.
Fixed
- Error messages are sentences, never codes or raw responses.
- A pinned View's Refresh no longer shows an internal reference in the conversation.
Security
- Signing in to a connector is tied to the browser that started it, so a sign-in link sent to someone else can't connect their account to yours.
- Pages and files Ysra reads from the web are checked at every redirect.
- Invitation links no longer travel in addresses that servers record.
- CLI 1.20.0: code written straight into a command asks first, as a delete does; Ysra's own sign-in never reaches the programs it runs; and Git in a folder you haven't trusted yet runs none of that folder's hooks or helper programs. See Install the CLI.
3.36 — One Connectors page, company setup in three steps, and the colleague library#
17 November 2026
Ysra 3.36.0 to 3.36.2 · web 2.43.0 to 2.46.0.
New
- One Connectors page. Settings → Connectors replaces Plugins and Integrations, with three tabs: Apps, MCP servers and Skills. The old addresses lead there. See Plugins, connectors and skills.
- Company setup in three steps, on the Company page: your company (read from your website when you give it), one goal with a real target, a deadline and how it is measured, and the first colleagues to hire. A goal reads “Not measured yet” until a real reading counts, and a number a colleague proposes counts only once you confirm it. See Understand the Company workspace.
- The colleague library. Team → Browse colleagues lists ready-made colleagues, each with one clear job, next to the packs. See Hire and shape a colleague.
Improved
- Ask says which apps it can't reach. Name an app that isn't connected and Ask says so in one line, “… isn't connected. Connect it in Settings → Connectors.”, instead of promising work it can't do.
- No card under a plain question. Hire, routine and capability cards come only when you ask for a change to your team or work that repeats.
- Google sign-in says in plain words which box to tick when Gmail or Calendar wasn't allowed, with Try again.
- Code runs that use your own model key are no longer charged to your credits.
- The build card in Ask shows the cloud notice and Accept and build, and always says why a build didn't start.
3.35 — Routines that research, honest results, and more colleagues on Pro and Max#
17 November 2026
Ysra 3.35.0.
New
- Routines can research. Any routine can search the web and read pages. A run that found nothing says what it tried and why, instead of “Finished”. See Create and run a routine.
Improved
- Done needs evidence. A colleague's task closes as done only when what came back holds what was asked; otherwise it waits for you to review, with one line saying why.
- More colleagues: Pro includes 10 active colleagues (was 6) and Max 25 (was 15). Colleagues made before 14 November don't count toward the limit. See Wallet, plans and limits.
- A routine that fails or finds nothing three times in a row pauses, and tells you why. A failed run is given back when the failure was ours.
- Today's names everywhere: colleagues and routines in every message and email, in all four languages.
Security
- Pasted secrets are removed. A password, key, token or card number pasted into Ask, Code or a colleague's chat is replaced by a marker before it is stored or read. Ysra tells you once to change it, and never asks for a secret.
3.34 — The Routines tab and honest goal progress#
16 November 2026
Ysra 3.34.0 · web 2.41.0.
New
- Team → Routines lists every routine by who runs it, with its schedule, last and next run, an on/off switch, and Runs as readable cards.
- Mayz compliance readiness: check a project and your answers against common security and privacy frameworks, with the gaps ranked and a report to save.
Improved
- Goal progress on the work board comes only from what was measured, such as steps you marked done. Otherwise it reads “Not measured yet”.
- Help points to today's pages: routines on Team → Routines, colleagues on Team.
3.33 — Plan credits#
16 November 2026
Ysra 3.33.0.
- Monthly credits: Starter 2,000, Pro 10,000, Max 20,000, Team 4,000 a seat, from each subscriber's next renewal. Max includes 300 free quick answers a day. See Wallet, plans and limits.
3.32 — One request across several repositories#
15 November 2026
Ysra 3.32.0 and 3.32.1.
New
- Products. Describe a product as its repositories, each with a one-line role, then start one request across them. Ysra plans across up to eight repositories first, saying what changes in each and why, and each part runs as a Code task in its own repository. See Projects.
3.31 — The Company page and a team from a few words#
15 November 2026
Ysra 3.31.0 and 3.31.1.
New
- The Company page brings your profile, what the team knows, your growth plan and the colleagues suited to your company into one place in the sidebar. See Understand the Company workspace.
- Describe the team you need. Say what your business needs help with, and Ysra proposes two to four colleagues, each with a name, a role and who they hand work to.
- Ysra knows its own app. Ask Ysra to hire someone, add a pack or set up your company, and it offers a card you confirm.
3.30 — Your AI company#
14 November 2026
Ysra 3.30.0 and 3.30.1.
New
- Hire colleagues. A colleague has a name, a role, a personality and a mark of their own. Hire a ready-made one, a pack, or describe the person you need. For each kind of action you choose whether they ask you first, tell you after, or just do it; sending outside the company and hiring always ask. See Hire and shape a colleague.
- Home is your team. Who is working, what needs you, and what was done today; a morning digest at your hour; and Pause the company.
- Projects with a team. A conversation can have a team: Ysra passes each message to the right colleague, and hand-offs between colleagues show with Approve and Not now when they ask first.
- Colleagues who build. A colleague allowed to code builds what you ask under their own name, and reports each round in their conversation.
- The work board and the company wiki. Goals, projects and tasks in one board, and shared facts the team writes down as it works, where your own lines always win. See Maintain shared company knowledge.
- How it runs (now the Team map): a map of your colleagues, routines and hand-off lines, with an “only when” rule and an approval on each line.
- A colleague's own page: what they are doing, what they know about you, suggestions from what they learned, and Look for work. See Use a colleague's page.
- Let a colleague use a computer to work on websites, live in front of you, asking before anything final. See Let them use a computer.
- Colleagues in Slack: ask one by name from Slack. See Talk to a colleague anywhere.
- Routines owned by colleagues, check-ins that ask you a question, spoken audio results, and each run's real cost. See Create and run a routine.
- Tables and pinned Views. Keep a live table in the workspace, see it as a table, a board or a dashboard, and pin a View to the sidebar. See Views and tables.
- New plans with free quick answers every day. See Wallet, plans and limits.
Improved
- Long conversations keep what was said at their start.
- When Ask uses its read-only browser, you can watch it in the thread.
- Web search is more reliable.
- Making videos is paused for now; pictures and posts stay.
3.29 — Editorial documents and honest sources#
9 November 2026
Ysra 3.29.0 to 3.29.3.
Improved
- Decks and PDFs in an editorial look, with key figures, timelines and comparisons, a summary at the start, and several looks or your own brand. See Documents and slides.
- Ask says where things came from, and never that it read a page it couldn't. A page that showed only menus, or an error, is marked as not read.
- When our model provider is unavailable, Ask says so plainly and charges nothing, instead of blaming your balance.
- Each part of a build made side by side is kept: download it, or bring it into the project.
- Goals show only in their own workspace.
- Pictures and videos stay in Ask however you word them.
Fixed
- Web search works again.
- A document made twice in one answer is attached once.
Security
- Document search no longer keeps your question in our logs.
3.28 — Code waits for your decisions#
8 November 2026
Ysra 3.28.0.
- Before I start. When Ask hands a build to Code, its open decisions come back with Ysra's suggestion already chosen; change any of them, and the build starts only with what you chose.
- Everything made or saved in the conversation goes with the build.
- Stop stops every part of a build, and each part opens on its own, read only, with Stop this part.
3.27 — Send to Telegram from Ask#
8 November 2026
Ysra 3.27.0.
- Ysra sends to Telegram. Ask Ysra to send something to your own Telegram, or to a group you added Ysra to. A card shows the message, and it goes only when you approve it. See Talk to a colleague anywhere.
3.26 — One free answer on ysra.ai, and connectors keep all their tools#
8 November 2026
Ysra 3.26.0.
- Try Ysra without signing in: a visitor's first question on ysra.ai gets one short answer.
- Telegram is a connector card next to the others.
- Connectors with many tools keep all of them, such as the campaign and results tools for Meta Ads.
3.25 — Pictures in Ask, Telegram and Meta Ads#
8 November 2026
Ysra 3.25.0 · web 2.36.0.
New
- Pictures and videos in Ask. Ask for a social post, a banner or a short clip, and it develops in a card with its price in credits. A Studio for each one: edit with words, variations, resize for each network, remove the background, and a brand kit. Everything is kept in the Library. (Making videos has been paused since 14 November.)
- Ysra on Telegram. Connect it, then ask in a private chat, with photos and documents. The conversation is kept in Ask.
- Meta Ads. Ask about your Facebook and Instagram ads: results, campaigns, ad sets, catalogs and tests. Every change is approved first.
- Let Ysra manage it. Ask hands a build to Code and looks after it until the goal is met, round by round.
- Run tokens for unattended CLI runs: limited to the run's own work, never money or approvals. See Run Ysra from a script.
Improved
- Grow my business writes in your language, reads a Google Maps link, and asks for a price it can't find instead of making one up.
- Handwritten pages and tables in photos are written out, a table as real columns. See Files you can upload.
Security
- Document safety. Ysra won't create or alter identity or third-party documents. For your own invoice or quote, it asks once that it's yours, then helps. See Documents and slides.
3.24 — Code wastes less time#
5 November 2026
Ysra 3.24.0 and 3.24.1 · CLI 1.16.0 to 1.19.2.
Improved
- Long commands don't hold Code up. A command still running after a quiet spell keeps going in the background while Code carries on.
- Approval cards and paused questions are in the language you write in.
- Local ports are asked once per folder.
- “What's in this folder?” is answered by looking.
- Fewer scratch files. Ysra removes its own scratch files without asking, and Undo my changes names any new file of yours it left in place.
- Code threads load faster.
- CLI 1.19:
ysra security checkchecks a computer by looking only, and you see what will be read first. See Check your computer.
Security
- CLI 1.18: every way we found for Ysra to lose or leak your files is closed, tested on macOS, Linux and Windows 11.
3.23 — One home for Ask, Code and Mayz, and Ready to build#
3 November 2026
Ysra 3.22.1 to 3.23.4 · web 2.24.0 to 2.25.6.
New
- A new web app layout. One sidebar on every page, one Recents list of your conversations, threads, reviews and runs, and one box on Home: choose Ask, Code or Mayz at its top, and what you typed stays when you switch. See Find your way around the web app.
- Ready to build. Ask a build question and Ask asks only what blocks it, at most five questions, then shows the brief Code will get, with Move to Code.
- Continue in Code, or in Ask. When a request fits another place better, a card offers to continue there. Nothing moves without your click.
Improved
- Why an answer failed: a failed answer says why, in your language.
- Your script: Ysra answers in the script you write in, such as Darija in Latin letters.
- Your own files from a link: give Code a link to your logo, images, fonts or PDFs, and it brings them into the project, checked first.
- Open preview and Open site in a thread's header.
- Mayz reports are clearer, with a Summary for managers to save as PDF or Word, and places chosen from a country list.
- A review on a short balance still gives its verdict on what it read.
3.22 — Mayz privacy reviews, objectives and plans#
2 November 2026
Ysra 3.22.0 · web 2.23.0.
- Mayz reviews privacy. Choose Privacy under Look at; Everything includes it too. The report adds a Personal data map: each personal or linkable field, with its file and line, where it is collected, stored and sent, how long it is kept, who reads it and how it is deleted. See Privacy.
- Privacy protections. Mayz checks minimum group sizes, hashing with or without a secret key, pseudonym keys, joins, collecting only what is needed, encryption, and added noise when the project says it uses it. Each check says what was found, or Not checked.
- Laws for the places you name. Say where you operate and where your users are, when you start or later on the project. Mayz never guesses a place and never stops a review to ask. Without places, the report says laws weren't checked.
- Coverage. Security, privacy and full reviews show which checks ran, mapped to broad areas of OWASP ASVS, the OWASP Top 10 Privacy Risks and the NIST Privacy Framework. This shows what was looked at; it is not a certification.
- Reports in your language, with a fixed notice: “This review is not a legal opinion, a certification or a replacement for a human audit.” Save as PDF, or as Word from the web app's Mayz page.
- Objectives and plans. Set a goal in your own words, make a plan of steps you approve, start the next step from Home, and link Ask chats, Code threads, Learn notebooks, Runbooks and routines to it. Weekly notes give the facts and are off by default. See Objectives and plans.
- Routines go further. A run can take up to 200 steps by default and 500 at most, and stops early when it keeps repeating itself or keeps failing. See Limits.
- Arabic answers are in Modern Standard Arabic unless you ask for a dialect by name. See When you write in another language.
3.21 — Private Views, workspace members, and Ysra never deletes your files#
30 October 2026
Ysra 3.21.0 · web 2.20.0 · desktop 1.23.1 · CLI 1.15.1 · VS Code extension 0.1.4.
- Private Views. A View opens only for the person who asked for it, and for the people its chat is shared with. Its link renews itself while you use it, and stops when a share is revoked or expires. See Views.
- Workspace members. Share a workspace with colleagues and give each a role: Owner, Admin, Member or Viewer. See Share a workspace with members.
- Try in Ysra. Examples in these docs have a Try in Ysra button that opens the web app with the example in the box, unsent. See Start here.
- Questions about your computer from a folder's thread. With Let Ysra look at this computer on, a thread on a folder can look at the rest of the computer, read only, and check what fills the disk. With it off, Ysra says where to turn it on. See Questions about your computer.
- Ysra never deletes files it didn't create, in any mode. A file it created, and nobody changed since, is deleted only after it asks. A script Ysra runs inside your project, such as tests or a build, can still delete project files, and undo brings them back. See What always asks.
- Places that start programs by themselves are never changed, such as shell start-up files, login items, scheduled tasks and Git hooks. Ysra gives you the line to add yourself.
- Windows. The desktop app no longer freezes: contained commands are paused for now, so commands ask first or run inside WSL. A big folder opens without freezing, and a folder without Git opens too, with each change asked. Windows doesn't need Git installed: Ysra brings its own. See Ysra Desktop on Windows.
- Cloud threads can commit, stash and switch branches on their machine; what you get is always compared with where the task started.
- Your name can't be your password: sign-up, invitations, your profile and a password reset refuse it.
- Fixes. Commands show as running only once they really start. Approval
cards show hidden characters, such as
<U+202E>. Show log file in desktop Settings shows the app's log, to send with a report.
3.20 — Code does what you ask, git on your computer, and safer cloud threads#
28 October 2026
Ysra 3.20.0 · web 2.19.0 · desktop 1.23.0 · CLI 1.15.0 · VS Code extension 0.1.3.
- Code does what you ask. A small ask gets a small change, with no tests
you didn't ask for. “No tests”, “don't install anything” or “just the
code” is respected from start to finish. Every ending has one plain receipt
line, such as “Ran:
npm test(passed).” or “Ran: nothing.”, and the “unverified” and “not fully checked” wording is gone. See How a Code thread works. - Access modes, updated. Auto runs commands. Asks first asks once per thread before running commands, on a new commands card. Read only is unchanged. Even in Auto, Ysra still asks before system installs, deleting or overwriting, destructive git, and pushes to the default branch or force pushes. See Access modes.
- git on your computer. Ysra commits and makes branches with its own git
tool. In Auto it commits on your current branch when that isn't the default
branch; on
mainit asks: “Commit on main? Or I can make a branch first.” Pushes of branches Ysra made run in Auto; a push to the default branch asks. It never rewrites commits it didn't make. In the cloud, delivery handles commit and push. See Commit and push. - Cloud environment secrets are available only to the setup script by default. A switch on each secret makes it available to Ysra's commands too. See Cloud environments.
- Cloud limits. A thread's cloud work has daily limits, and stops with a plain message when your credit runs out. See Limits.
- Cloud previews open through Ysra only, on a private link; the machine's own address isn't public. See Previews.
- Ask remembers long conversations, and follow-ups reuse the files and sources already found: “what does page 4 say?” See Long conversations and follow-ups.
- GitHub. Connecting finishes in one step. The GitHub card in Integrations has Disconnect and Repositories on GitHub, and the repository picker shows when it's loading and lets you try again. See GitHub.
- Workspaces. Everyone works in a workspace of their own. If you have none, Ysra asks you to create one when you sign in, and your earlier chats move into it. Archived workspaces appear in the switcher. See Workspaces and files.
- Plugins and skills from your other tools are picked up quietly when their plugin updates them. Ysra asks only about new or hand-edited ones, once per change. See Plugins.
- Desktop on Windows. The window fits small screens, zoom with Ctrl+-, Ctrl++ and Ctrl+0, account and settings are always reachable, and a tip suggests running commands in WSL. See Ysra Desktop on Windows.
- VS Code and Cursor. Ysra has its own icon in the side bar, and only the code you select is attached. See VS Code and Cursor.
- Fixes. The Files tab shows the open file at full width again. Decks made in Ask open in Keynote.
3.19 — Views, Learn, and Word, PowerPoint and PDF files#
27 October 2026
Ysra 3.19.0 · web 2.18.0 · desktop 1.22.0 · CLI 1.14.0.
- Views in Ask. When a picture explains better than words, Ysra shows one in its answer: a chart from real numbers, a diagram, or a small interactive page with sliders and things to drag. Math is laid out properly. Save as View keeps one in the side panel, and Open the View opens it on its own page. A View runs walled off from your account. See Views.
- Learn. A new Learn section: notebooks made from your course files, with a guide, cards and practice exams for each chapter, every item cited to its page; a daily review that uses no credits; practice answers marked, typed or as a photo; topics learned in planned sessions; and Learn mode in any Ask chat, with hints before answers. See Learn.
- Documents. Ask makes Word, PowerPoint and PDF files, with real charts and tables, footnotes and sources, and right-to-left languages laid out properly. “Now as slides” turns the same content into a deck. Each file is checked before you get it, and its first pages show in the side panel. See Documents and slides.
- Reading Word files includes comments, tracked changes (shown as proposed) and what the pictures show. See Files you can upload.
- Upload checks. Pictures in uploads, including those inside PDF, Word, PowerPoint and Excel files, are checked before they're stored. A file that can't be checked is refused with a plain reason. See Files you can upload.
- Members and deleting. When someone leaves an organisation, its workspaces, colleagues and routines stay with it, and an owner or admin takes them over. Deleting a workspace or an account hides it at once and erases it after 30 days. See Data, privacy and deletion.
3.18 — Access modes, deleting, and the terms#
26–27 October 2026
Ysra 3.18.0 to 3.18.2 · web 2.16 to 2.17 · desktop 1.21.
- Access modes for Code threads: Auto, Asks first or Read only, with Plan first as a separate switch. Read only reads, explains and plans, and changes nothing. See Access modes.
- Fewer questions. Asking for the work is the go-ahead: there's no separate card to approve paid work. Stop and Continue need no card, and in Asks first Ysra asks once per thread before installing your project's packages.
- Checks that fit the change. A small change is checked the way that proves it, and the ending says plainly what was checked and what wasn't.
- Delete and turn off. Delete your Code threads, Ask chats, colleagues and routines; turn a colleague or a routine off and on again. See Data, privacy and deletion.
- Our terms. Accept the Terms and the Acceptable Use Policy once, with one box; public colleagues and published sites have a Report abuse link. See Acceptable use.
- Buying credits asks you to confirm that you want them available now, which waives the 14-day withdrawal right for credits you use. See Plans and billing.
- Usage on a shared wallet names only your own Code threads; a colleague's appear as one line per person.
- Public colleagues always show “You're chatting with an AI assistant. Answers can be wrong.”
- VS Code and Cursor. The Ysra extension brings Code threads into your editor. See VS Code and Cursor.
3.17 — Big builds finish, new emails, and plugins per workspace#
26 October 2026
Ysra 3.17.0 · web 2.15.0 · desktop 1.20.0 · CLI 1.13.0.
- Big builds finish. Large apps and very large files are built to the end. If a step still runs too long, Ysra says so plainly. Your work is always saved, and Continue picks up from there. See A step runs too long.
- Databases on cloud machines. When an app needs PostgreSQL, it starts reliably on the machine; there is nothing to set up. See The machine’s life.
- New emails. Invitations, finished work, visitor questions and account emails are light and short: one headline, a line or two, one button, and links to ysra.ai and the docs. They never carry technical error text. See Emails from Ysra.
- iPad and Safari. Download and open in a new tab work for files in Ask, Library and cloud projects, and notifications no longer stay on screen.
- Plugins per workspace. Settings → Plugins lists the plugins of the workspace you have open; those used everywhere carry an All workspaces badge, and Show plugins from other workspaces shows the rest. Connecting the same service in another workspace keeps a separate connection, for example a different account for each workspace. See Plugins and workspaces.
- Desktop: the workspace switcher is at the top of the side panel, as on the web: switch, New workspace, or Files & settings. See The panel.
- Models. The effort you choose now applies to every model in the list.
3.16 — One panel, Computer replay, and a browser you can drive#
26 October 2026
Ysra 3.16.0 · web 2.14.0 · desktop 1.19.0 · CLI 1.13.0.
- One panel beside a Code thread, the same on the web and the desktop: tabs for Computer, Preview, Changes, Files and Progress, and + for a terminal, a phone-width preview or the report. One button opens and closes it.
- Computer is always there. It shows Ysra's browser live while it checks your app, and a replay of every step afterwards.
- Screenshots in the thread. Finished work shows one or two of the screenshots Ysra took; click one to see it full size, or See all steps.
- Drive the browser yourself (desktop). In a thread on your computer, the Computer tab is a real browser: open any page, sign in, then Let Ysra drive and watch every click, or Take back at any time. Ysra only sees your page while it drives or when you switch on Ysra can see this page. It never types passwords, and sending a form asks you first.
- Plugins and sources per workspace. Each plugin can be used in one workspace or all of them, and a workspace can choose the sources it uses. Routines on the desktop show only the open workspace's.
- Long messages. Paste up to 200,000 characters in Ask or Code; the whole text reaches Ysra, and Code keeps earlier long messages whole.
- Simple requests stay simple. "Create a worktree" or "make a branch" runs as a few commands, and Ysra asks one question when a request doesn't fit the folder.
- Installs on your computer reach the package registries, and a blocked host is reported as Ysra's own limit, never as a sign-in. Your project's tests can start a local server once you allow it for the thread.
- Models. A thread you don't pick a mode for runs on Forge, as its header says. Code review uses the thread's own model. The model list has another choice.
- Ask answers "what can you do?" in a few lines, starts faster, and Set up with Ysra reads sites that live under a path (for example a GitHub Pages project site).
3.15 — What Ysra can do: a real browser, images, and supply-chain checks#
26 October 2026
This entry covers 3.14.0 to 3.14.3 and 3.15.0.
- What Ysra can do: a new page lists every tool, which part of Ysra gets which, with examples and costs. Asked “can you open this link?” or “where do I turn that on?”, Ysra answers from what is on in that conversation, says what is off and why, and where to turn it on. See What Ysra can do.
- A real browser on any website in Ask, colleagues, Code, routines and Set up with Ysra: pages built with scripts, listings and maps are opened in an isolated browser that runs their scripts, reads what a person would see, scrolls, clicks and takes screenshots. Read-only, never your own browser; its time is charged with the work. Public colleagues never get it.
- Images in Ask and colleagues: make an image from a description, or save a picture from the web into the conversation’s files. Colleagues get two new capabilities, Web browser and Images. See colleagues.
- Code’s quick replies read: “what’s in this folder?” or “open this link” is answered straight away from the project’s files, the web or Ysra’s docs, without starting a task. Tasks get web research, the real browser, Ysra’s docs and route links in every run, and screenshots of the built app are checked by default. See What Code uses.
- Routines read pages, browse, and make files: read a page, open one in the real browser and watch it live, write a PDF report or a spreadsheet, make images. Files come back with the run and can be attached to an email you approve. See The tools a routine can be given.
- Dependency watch: a routine that checks a repository’s packages every day and tells you only what is new; a malicious or compromised package is an alert at once. See Dependency watch.
- Mayz checks the supply chain in every review: exact package versions against public advisories, malicious and hijacked packages included, plus web lookups for fresh incidents, cited. See Supply chain.
- Set up with Ysra finds your site: name your business and Ysra searches for its website, asks whether it is yours, reads sites built with scripts, and saves your logo and photos. See Set up with Ysra.
- Code tasks end three plain ways (3.14): Done, Needs you or Didn’t work, with what failed said in plain words.
- A faster, lower-cost model is the default for everyday building (3.14).
- Images made in a Code task: up to 6 a task.
3.13, web app 2.12 and desktop 1.17 — Ask speeds, and directions to your door#
24 October 2026 Web app 2.12.1 Desktop 1.17.0
This entry covers 3.13.0, 3.13.1 and 3.13.2, web app 2.12.0 and 2.12.1, and desktop 1.17.0.
- Ask speeds: a Speed choice in Ask’s box, Auto, Quick or Thorough. Auto picks for each question: Quick for chat, rewording and short questions; Thorough for research, files, reports and anything about what is true now, such as the latest version or today’s prices. The speed you pick stays with the conversation, and each answer says which one it was worked on, beside its credits. See Auto, Quick or Thorough.
- A speed on each colleague: set it in the colleague’s settings. A public colleague on Auto answers Quick. See colleagues.
- Directions: give a colleague a Location, its address and what to know On arriving, and visitors who ask the way get a few lines on how to come and a route link that opens in their own Maps app, turn by turn. Ask gives route links too. See Directions to you.
- Shared map links are understood: a Google Maps link a visitor pastes is read for the place it points to, so “I’m here, how do I get to you?” gets a route from there.
- Links in the website chat open: a route link or a page in an answer is a link the visitor can tap.
- Ask answers in the language you write in, and a message too short to tell, such as a name, a word or a link, keeps the conversation’s language.
- Web app: a pasted link or a long word in a question wraps inside its bubble.
3.12, web app 2.11 and desktop 1.16 — a fuller Set up with Ysra#
24 October 2026 Web app 2.11.1 Desktop 1.16.0
This entry covers 3.12.0 and 3.12.1, web app 2.11.0 and 2.11.1, and desktop 1.16.0.
- Several websites: Set up with Ysra reads up to 3 sites you name, your website and your docs for example, about 6 pages each from the sitemap, and says what it read (“Read ysra.ai · 6 pages, docs.ysra.ai · 6 pages”). The setup names only websites it read or that you typed. See You give a website, or several.
- Change any part before Start: click a part’s name or text, change it, and click away to keep it; Escape puts it back. See You remove or change a part.
- Several files at once for a document slot, and Add files for … on the public colleague, which shows how many files are shared and how many are still being read. See What Start creates.
- At most one customer-facing colleague in a setup, allowed on every website you gave.
- Visitor questions per workspace: the list and the waiting count show the colleagues of the workspace you have open. See Visitor questions.
- Code examples on the web open Code in Ysra’s cloud: Try it in Code on the Start page writes the example into Code’s start box. See Start here.
- Another model in Code’s picker: a faster, lower-cost model for everyday changes. See Choosing a model yourself.
3.11.0, web app 2.10 and desktop 1.15 — Set up with Ysra, and the phone decides the SDK#
23 October 2026 Web app 2.10.1 Desktop 1.15.1
This entry covers web app 2.10.0 and 2.10.1 and desktop 1.15.0 and 1.15.1.
- Set up with Ysra: a new account talks with Ysra about its company, one question at a time and in its own language. Give your website’s address and Ysra reads it once. Ysra then proposes a setup to trim: documents to add, colleagues, a public colleague for your site, build ideas and routines. Nothing is created until you press Start, and each part then says whether it is ready, waiting for a file or a plugin, or failed with Try again. Closing the app loses nothing. Routines start switched off and run in your time zone. The setup is free. It opens once for a new account and is in Settings to run again. See Set up with Ysra.
- Build ideas under Code’s start box: the ideas the setup saves wait there and are never run by themselves. Start building writes the idea into the box, and ✕ puts it away. The box and the ideas scroll together.
- Phone apps follow the phone that scans: the Preview reads which Expo SDK the scanning phone’s Expo Go runs, compares it with the app’s, and says exactly what to do: move the app to the phone’s SDK, or update Expo Go. Move to SDK N asks Ysra to make the move. See Phone apps and the Expo SDK.
CLI 1.12.0 — an exit code for work that wasn’t fully checked#
23 October 2026 CLI 1.12.0
ysra execexits with 11 when it finished and wrote its changes but not every check finished. 0 now means done and checked only. See Exit codes.- On the whole computer, commands only ever run contained: read-only, with no network. Where that can’t start, a command is refused with the reason instead of running uncontained.
- An outdated WSL helper is reported before a whole-computer command fails.
3.10.0 — business sites, built fast and with real details#
23 October 2026
- A one-page site asked for in French, Spanish, Darija or Arabic is built the fast way, as one asked for in English.
- A business’s first site that gives no contact details asks for them first, on one card in your language: type your real details, and choose photos or none in one tap. The site is then built with them, never with a placeholder phone number. The card is asked only when you speak of your own business.
- A one-page site never asks to install packages, and never gets a login or admin area you didn’t ask for: bookings go to WhatsApp or email.
- A message that only asks for the preview, in any language, starts the preview instead of a paid change. See Previews.
3.9 — phone apps for the Expo Go you have, and checks that read the page#
23 October 2026
This entry covers 3.9.0 and 3.9.1.
- New phone apps open in Expo Go as people have it: Ysra creates them for the SDK the store’s Expo Go runs, and the Preview’s hint names the project’s SDK and the exact move, instead of moving a project past what Expo Go can open. See Phone apps and the Expo SDK.
- Browser checks read the running page before they test it, so they use the page’s real fields instead of guessing. A save button in French, Spanish or Arabic counts as saving.
- When a check misses only because the page words a value differently, the check is rewritten from what the page shows, instead of sending a working app for repair.
- Code keeps the model you chose for the whole task.
Web app 2.9 and desktop 1.14 — Preview in a cloud thread#
23 October 2026 Web app 2.9.1 Desktop 1.14.1
This entry covers web app 2.9.0 and 2.9.1 and desktop 1.14.0 and 1.14.1.
- Preview in a cloud thread starts the project on the thread’s own machine, and shows Starting… while it does. If it doesn’t start, it says so, never an endless spinner. A phone app shows its QR code. Download the project saves the thread’s files. See Previews.
- A task that ends Not fully checked closes its last stretch of work, so it no longer reads “Mulling… 25m” for good.
- Links never show a preview link’s private token, and long words and addresses wrap inside their message.
- Desktop: Ask’s Copy sits under the message, with its time, as in Code.
- Desktop: a setting that could make programs run by themselves is asked about in a dialog naming the file, every time. A command on the whole computer runs contained, read-only and with no network.
3.8 — Ysra thinks about the product first, previews for any project, and Render#
22 October 2026
This entry covers 3.8.0 and 3.8.1.
- What I’ll build: for a new app, or a short or vague request, Ysra first writes a short brief (who uses it, the must-haves, the data and the rules) and shows it as a note; the work starts at once. Language, country and currency come from how you write. At the end, each must-have is checked working in the browser. See How a thread works.
- Preview any project without deploying: a static site, a web app with its database, or a phone app, on the thread’s cloud machine, at a private address only you can open. “Preview” or “can I run this?” starts it, and is never charged as a change. See Previews.
- Phone apps open in Expo Go from any network, with live reload.
- Deploy to your own Render: Ysra shows the plan first (what it creates or reuses, the plan and region, why a database, and that Render bills you), and creates nothing before your OK. Render is in the connectors directory.
- The hosting you pick is remembered: “deploy” doesn’t ask again, and a deploy needs only the connections that hosting uses. See Publish and deploy.
- Not fully checked says why, once: “Not confirmed: … The change is kept; you can still use or deliver it.” A note such as “this is a temporary preview link” no longer makes working work read as not fully checked.
- Built pages can load browser libraries from the common public CDNs.
Web app 2.8.0 — Code on a phone#
22 October 2026 Web app 2.8.0
- On a phone, a Code thread’s Panel, Files, Preview and review open as full-screen sheets over the thread, one at a time. Closing one returns to the same place. The review lists the changed files, then shows one file’s changes with a back button.
- A message’s time and Copy sit under it, never over its words.
- Send always stays inside the message box, however narrow the window.
Desktop 1.13.0 — safer commands and clearer waits#
22 October 2026 Desktop 1.13.0
- A command on the whole computer that installs, deletes, moves or changes permissions always needs a person, on Windows too.
- “Allow for this session” covers that exact command, never a whole tool, and auto mode never runs project code uncontained.
- When Ysra can’t be reached for a while, Ask and routines say “Can’t reach Ysra, retrying…” and carry on once it answers.
CLI 1.11.0 — ysra exec runs the whole product#
22 October 2026 CLI 1.11.0
ysra exec --review mayzhas Mayz review the work, fix what it found and review again (--review-rounds, 2 by default). New exit codes: 5 needs work, 6 unsafe, 7 the review didn’t finish, and 10 when a stop wasn’t confirmed. See Exit codes.--allow commit,push,deliver,deploy,publish,undolets a sandboxed run do those itself;--approve-plan,--timeout,--max-turnsand--traceare new.ysra helpandysra help <command>work, and an unknown flag is an error./mayz,/mayz fixand/mayz againwork in the chat./computer changes onis available; every change still asks first.- Safety: Git run by commands never runs the repository’s hooks; a file you changed since Ysra read it is never overwritten; the browser opens only previews Ysra started. See Command reference.
Mobile 1.9 and 1.10 — Code, voice and cloud projects on the phone#
22 October 2026 Mobile 1.10.0
This entry covers mobile 1.9.0 and 1.10.0.
- Code on the phone, next to Mayz and Ask: start and follow Code threads, on a GitHub repository, a folder on one of your computers, or a New cloud project with no repository. See Mobile app.
- Talk with Ysra by voice in Code, Mayz and Ask, and from the start box; the app says what voice costs before it starts. See Voice.
- A cloud project in one place: its machine, connectors, background tasks, outputs, the files Ysra made and the published site. Download the project saves its files as a zip.
- Publish and Deploy from the phone: publish a website on Ysra, private until you share it, or deploy an app with a server to your own hosting, then go live. A deploy shows in the thread as it happens, and Notices say when it is live or didn’t go through.
- Mayz reviews your work and fixes what it finds when you say so.
- Connectors: Microsoft 365, Linear, Notion and more, with live actions in Slack and Jira after your approval. Type @ to point at a file, a conversation, a thread, a colleague or a connector, and see what each can read and do.
- Expo Go: open a cloud thread’s phone app from any network, or an app running on your computer.
3.7 — limits Ysra keeps to, and fixes#
22 October 2026 Web app 2.7.0
This entry covers 3.7.0, 3.7.1 and web app 2.7.0.
- A Code task can be given a limit on its model calls; it stops cleanly at the limit, Not fully checked, and never asks for money or carries on. See How a thread works.
- Code works longer before stopping a task that isn’t making progress.
- A task that ends with a check failed or not run, or a known issue, ends Not fully checked and says plainly what didn’t pass. The work is kept and can still be delivered.
- Routines stop before a step once a run or the routine’s day has spent its limit. A routine started from Ask can’t run more often than every 5 minutes. See How routines work.
- Allow & continue on the install card sticks: it is no longer asked twice.
- A public link’s monthly limit counts answers still being written. See Public colleagues.
- An email address signs in in any case,
Sam@Example.comassam@example.com.
3.6.0, web app 2.5 to 2.6 and desktop 1.12 — talk with Ysra, cloud projects, and deploys that never block#
21 October 2026 Web app 2.6.2 Desktop 1.12.0
This entry covers web app 2.5.0 to 2.6.2 and desktop 1.12.0.
- Talk with Ysra: a voice button in a thread, in Ask, and on the start boxes. Ysra says what voice costs first; then the message box gives way to Ysra as a sphere of light that listens and speaks, with the time, Mute, End and Minimise. Your words go into the thread as you said them, and Ysra reads the thread’s replies, questions and results aloud, in your language (English, French or Darija). Say “yes” while a card waits and it answers the card. Talk over her and she stops. A minimised call floats in a corner with Open and End, so it is never lost. Your first spoken request can start a new thread. Voice uses about 12 credits a minute. See Limits.
- Dictation gets the thread’s names right. A clip is at most 2 minutes, and an hour a day.
- Cloud projects: Code in Ysra’s cloud with no repository. Choose New cloud project; Ysra keeps the files between turns, and Add repository moves them to GitHub when you want. Files the work makes show as download cards. See In Ysra’s cloud.
- Publish on Ysra: a website gets an address on Ysra’s domain, private first, then Share to make it public. A project that needs a server offers Deploy instead. See Publish and deploy.
- Deploy a cloud thread to your own hosting and database accounts: a preview, then Go live. With no hosting connected, Ysra asks where on a card. A preview deploys apart from the live site, so it never changes its settings.
- A deploy is a turn in the thread: its step while it runs, the address once it’s live, or what went wrong with Reconnect. The bell says when it’s live or didn’t go through. A hosting connection that needs reconnecting is asked for by name.
- Ysra warns, never blocks: a commit, push, pull request, deploy, Go live or Publish you ask for goes through, marked not fully checked when it wasn’t. A secret in the work is asked about (“Move it to a secret first, or deliver it as it is?”) and its value is never shown. Open pull request asks Draft or Ready for review. See Ysra warns, it never blocks.
- Question cards: when Ysra needs you to choose, the recommended choice comes first, with Other and Skip. While Ysra works, ⌘⏎ queues your message for when the current step ends.
- A cloud thread’s panel: its environment, connectors, background tasks with their log and Stop, outputs, and Download the project. A cloud environment takes secrets for the machine and more allowed domains.
- A phone app in a cloud thread has Open on your phone: a QR code for Expo Go that works from any network.
@offers Slack, Jira and Gmail when they’re connected.- Web app: what the desktop has, in the browser: Preview and Files panes beside a thread, Hand to Code, Mayz reviews as panels, Code’s modes and an colleague on the start box, ⌘K for threads and settings, Settings → Devices, and spreadsheets and Markdown to edit in the file viewer, saved as a copy. On a phone, menus open as sheets.
- Desktop: a new Code thread starts in the last folder you used on this computer; a repository is never chosen for you.
CLI 1.10.0 — Mayz in the terminal, and your skills in the cloud#
20 October 2026 CLI 1.10.0
This entry covers CLI 1.8.2, 1.9.0 and 1.10.0.
ysra mayzreviews a folder as it is and never changes it.--focuspicks what to look at, and--printprints the report and exits with0ready,1needs work,2unsafe or3not finished. A review that didn’t finish is never reported as ready. When the credits are too low to start one, it says so and what to do. See Review a project.ysra skills pushuploads your own skills, so work in Ysra’s cloud has them too. See Command reference.- Safer commands: on macOS and Linux, a destructive command in a project
folder shows a red card you have to approve, and undo brings back small
files Git ignores, such as
.env. Deletes hidden in scripts,git clean -f, encoded PowerShell and inline Python or Node deletes all count as destructive. - Windows: when commands aren’t contained, deleting or overwriting files
that already existed is refused.
ysra contain(alpha) runs commands under Ysra’s own Windows account. See Windows. - Saying “ok” or “install” to an install Ysra proposes does what its Install button does.
- Without Git, Ysra says once how to install it, instead of repeating an error on every message.
- Build is now called Code.
3.5.0 — connectors, Microsoft 365, and changes you approve#
20 October 2026 Web app 2.4.0
- Settings → Plugins, in the web and desktop apps: about thirty services
to connect in one click from Browse directory, your company’s own
servers (ServiceNow, Jenkins, JFrog, Splunk, Snowflake, Azure DevOps), any
MCP server by its address, and skills. Mention a service in Ask with
@, such as@linear. See Plugins, connectors and skills. - Microsoft 365: Outlook mail and calendar, OneDrive and SharePoint, Teams and people, with work or personal accounts. Send mail with attachments, create events and Teams meetings, and post in Teams, each after you approve it. See Microsoft 365.
- Slack and Jira live actions:
@slacksearches, reads and posts;@jiracovers Jira and Confluence. See Slack and Jira. - Changes are always approved in Ask: anything that sends or changes something is a card with exactly what will happen, and Approve, Edit or Decline. See Actions and approvals.
- Ask: Stop stops an answer; a PDF report can be emailed with the PDF attached; “send it to Sam too” reuses the same email.
- Code in Ysra’s cloud: start Code on a GitHub repository from the web app or the desktop app, with cloud environments and app previews. Cloud time uses credits. See Code in Ysra’s cloud.
- Mayz reviews: Mayz reads a project and reports a verdict and findings, with evidence, without changing it. See Mayz reviews.
- Build is now called Code (Ysra Code). Only the name changed: addresses and settings stay as they were.
Desktop 1.11.3 — Copy all, and installs after a yes in words#
16 October 2026 Desktop 1.11.3
- Copy all: the ⋯ in a thread’s header (or ⌘⇧C, Ctrl+Shift+C on Windows and Linux) copies the whole thread as Markdown, with its messages, steps, commands and their output, approvals and times. Save as .md… writes the same text to a file.
- Answer “ok” or “install” and Ysra installs the tool it asked about, as the Install card does, then says how it went. See Install tools with your OK.
- A failed install never just says it failed: under the plain reason is a line with the code, the reason and the command to run by hand.
3.4.2 — installs that follow your system#
15 October 2026
- On Windows, commands name Python the way Windows has it (
python), andpython3on macOS and Linux. - A question about installing a tool gives the command for your system: the
wingetcommand on Windows, Apple’s installer for Git only on a Mac. - Typing “Install” in a conversation no longer goes round in circles: Ysra says installing happens on the computer with the folder, from the card in Ysra there or by installing it yourself.
Desktop 1.11.2 and CLI 1.8.1 — Windows installs Node.js and Python#
15 October 2026 Desktop 1.11.2 CLI 1.8.1
- Node.js and Python install on Windows too, into Ysra’s own folder, as
on macOS and Linux.
npm,npxand other.cmdprograms run wherever Ysra starts them. When Ysra can’t install a tool, the card gives the steps, such as thewingetcommand. See Install tools with your OK. - Desktop: opening Ysra again from the desktop shortcut while it is in the tray brings the window back, and clicking a notification opens its thread even after the window was closed.
- Desktop: a network share’s top folder counts as a whole disk, and Open in Ysra on a drive in Explorer works.
Desktop 1.11.1 — create an account or request access#
15 October 2026 Desktop 1.11.1
- The sign-in screen always uses Ysra’s server, and offers Request access while sign-up is closed. See Get an account.
Web app 2.3.0 and Ysra 3.4.1 — early access#
15 October 2026 Web app 2.3.0
- Ysra is in early access, by invitation only. The sign-in page says “New to Ysra? Request access, or open the invitation link someone on your team sent you.” See Get an account.
- Invitations work as before.
- Home scrolls on a short window, so its top can always be reached.
3.4.0 — Build modes#
15 October 2026
- Build modes: Spark for small, clear jobs, Forge for everyday building (the default) and Summit for large or tricky work. Each sets the model and how hard it thinks. You can still pick a model and an effort yourself. See Build modes and models.
- Each model in the list says what it’s best for and how much it costs.
- Before reading code to answer a question, Build asks in plain words, such as “I’ll read the code to answer, without changing anything… Go ahead?”.
- Build asks for several lookups at once, instead of one at a time.
Web app 2.2.0 — a colour per part, a new Home, and colleagues on the rail#
15 October 2026 Web app 2.2.0
- The rail names each part, each with its colour: Home, Ask, colleagues, routines and Library, then Machines and Runbooks where you have them. An orange count says what waits for you. See Tour of the web app.
- Home shows what is going on: Routines on, colleagues public, what waits for you, the numbers for each part, and what happened lately, with the Ask box in the middle.
- Colleagues have a place of their own on the rail, with Visitor questions beside them. Old addresses lead there. See colleagues.
- The Ask box is one row: +, who answers, Answer or Deep dive, the sources, and send.
- A public colleague’s settings say visitors see neither your files nor their names, only the answer.
Desktop 1.11.0 — the message box in one row, and Build modes#
15 October 2026 Desktop 1.11.0
- Choose how Build works with one control in the message box: a mode, or a model you pick yourself, and how hard it thinks (Quick, Balanced, Thorough). The thread’s header says which. See Build modes and models.
- The message box is one row: + for files and a colleague, Access (Asks first, Plan first or Full access), the model, the mic, and one button that sends, or stops while it works. Where the thread runs is a quiet line under the box. See Start a thread.
- Commands that can’t be undone say so in red, with Don’t run first and Run it anyway, and are never allowed for the whole session. See The command card.
- The rail names each part, with colleagues as a section of its own, and Home shows what is going on. See Ysra Desktop.
CLI 1.8.0 — the chat in your terminal, and Build modes#
15 October 2026 CLI 1.8.0
- The chat prints into the terminal itself: the mouse wheel and the
scrollback scroll it, and you can select and copy. Full screen is a choice:
ysra --fullscreen, or/settings→ Screen. Ctrl+O shows the latest step in full. See Keys. /mode,/modeland/effort, kept for new threads, andysra exec --mode,--modeland--effort quick|balanced|thorough. The line above the box shows the folder, mode, model, effort and account. See Build modes and models.- On Windows, some commands always ask: one that deletes or can’t be undone, one that works outside the folder, and network tools. See Windows.
- A preview Ysra started stops when
ysraexits, instead of holding its port. - The CLI connects to Ysra’s new address. A sign-in from before the move
says “Ysra has moved to a new home. Sign in again with
ysra login(you’ll need a new account).”
3.3.5 — times in a routine’s schedule read as you write them#
14 October 2026
- A time in a request is read as written: “every Monday at 10” runs at 10:00, “around 8h30” at 08:30 and “daily at 6pm” at 18:00. Before, a time without minutes or am/pm ran at 09:00. See Schedules.
3.3 — routines inside Ask, notices, and a report on each public colleague#
14 October 2026 Ysra 3.3.4
- Routines start from Ask. Describe a standing job in a conversation (“check our website every day”) and a routine card appears under the answer: when it runs, what it reads, what it does and what it asks you first. The card fills in what was missing, such as the address, from your next replies. Start this routine switches it on; a website watch checks once straight away. There are no kinds of routine or permission boxes to choose. See Start a routine from Ask.
- Runs come back to the conversation as short run cards, and Routines · N in its header opens a panel with each routine’s switch, Run now, Edit, its runs and its approvals. Every send or post still waits for your approval of the exact text. See Runs and approvals.
- Schedules come from your words, at your local time: “every Monday at 9:00”, “every 5 minutes”. See Schedules.
- Notices: a bell with what your routines did. Failures, approvals, outages and recoveries are also emailed, unless you turn that off. See Notices.
- A report on each public colleague: what visitors asked over 7, 30 or 90 days, what it couldn’t answer, and which files its answers used. See Public colleagues.
- Credit in any amount from $5 to $5,000, in whole dollars. See Billing.
- The steps under an answer list only what Ysra looked at.
Web app 2.1.0 — routines in Ask, notices, and error reports#
14 October 2026 Web app 2.1.0
- Routines inside Ask: the routine card under an answer, or Make this a Routine in an answer’s … menu; the Routines · N panel; run cards with Show run. Routines is a table with Open in Ask →, and All runs is a page of its own. + New routine opens Ask. See routines.
- Notices: the bell at the foot of the sidebar, and Settings → Email notices. See Notices.
- The public colleague report, under Anyone with the link can ask.
- Other amount beside the credit packs, and in automatic top-ups. See Billing.
- Send error reports in Settings, on by default. Reports never include your questions, answers or files. A crash shows a page to reload instead of a blank screen. See Settings.
- Integrations shows Sources and the mailbox Gmail for a routine; what was left from Build on the web is gone. See Integrations.
Desktop 1.10.0 — routines in Ask, notices, and Rules & instructions#
14 October 2026 Desktop 1.10.0
- Routines inside Ask, the Routines table and All runs, as in the web app. See routines.
- Notices: the bell at the foot of the rail, a system notification while the app is in the background, and the email switches in Settings → General. See Notices.
- Library → Rules & instructions and Library → Colleagues, as on the web, and the public colleague report. See Rules.
- Error reports: Send error reports in Settings → General, and Help → Send a report…. See Troubleshooting.
- Build runs only on your computer. A thread no longer offers a preview on Ysra’s servers; older threads that ran there are no longer listed. See Review a change.
Also 1.9.1: the sidebar takes clicks again on a Mac, and the “Ysra couldn’t start” message can be clicked.
Mobile 1.8.1 — a new address#
15 October 2026 Mobile 1.8.1
- The app connects to Ysra’s new address. An account from before the move signs in again: “Ysra has moved to a new home. Sign in again (you’ll need a new account).” No screens changed.
Mobile 1.8.0 — Notices, Help, and no Build#
14 October 2026 Mobile 1.8.0
The first phone release since 1.6.0.
- Notices: a routine finished, failed or stopped to ask, or an uptime routine saw an outage or a recovery. Notices in the menu counts the unread ones; tap one to open its routine. No push notifications yet. See Notices.
- Help: Settings → Help answers questions about using Ysra, free, and Get help from the team sends a conversation to the team. See Ysra help.
- Settings: Usage, People (for those who can manage the organisation), Signed in on, Support access, Require unlock, Show times and Send error reports. Show reasoning and the accent colour are gone. See Mobile app settings.
- Ask: attach CSV, TSV and Excel files; a spreadsheet Ysra makes shows as a file; an answer says how long it took; a mention opens the conversation, routine or file it names.
- Routines: a routine’s page shows its plan, read-only, with what the latest run did at each step.
- Build is no longer on the phone. It runs on your computer, in the desktop app or the CLI. A link to a Build thread opens Home.
3.2.0 — Build runs on your computer#
13 October 2026
- Build runs on your own computer, in the desktop app or the CLI, on a folder there. It no longer runs on Ysra’s servers, so it can’t be started from the web app or the phone. Work started from somewhere it can’t run says “Build runs on your own computer now. Open the Ysra desktop app or the command line in your project’s folder to start it.” Threads on your own computer are unchanged. See Build.
- Deploying is a step Build takes on your computer, with your own tools, only after you say yes. See Deploy from your computer.
- Ask knows this: it says Build is on your computer, and that Hand to Build is in the desktop app.
- The built-in colleague’s third suggested question is now “Research this and write me a report”. Questions you wrote yourself are left as they are.
Web app 2.0 — Ask first; Build moves to your computer#
13 October 2026 Web app 2.0.1
- Build is no longer in the web app: its place in the rail, its start box, thread pages, previews and deployments are gone. Use the desktop app or the CLI, signed in with the same account. Nothing is deleted.
- Home is where you ask: “What do you want to know?”, then Automate a job → and Build runs on your computer. Get the apps. Cmd+N starts a new question; with no match, Cmd+K asks what you typed. See Tour of the web app.
- Old Build links open a page headed Build runs on your computer, with Get the apps and Ask a question instead.
- Ask no longer offers Hand to Build on the web; Automate this stays. See Turn an answer into work.
- Settings is one page. The Secrets, Team and Workspace computer tabs are gone; people are under Account → People and keys under Account → Integrations. See Settings.
- Routines: Edit opens the same screen as making a routine, filled with what it has. A run shows what it looked at and found: a mail run’s search, matches and draft; an uptime run’s address, state, answer and response time. See Edit a routine and Run details.
- Public colleagues can be given images, once Ysra has read them. See Public colleagues.
- Library → Memory, Colleagues and Files and the workspace switcher are the same screens as in the desktop app. Usage still lists past Build work.
3.1.1 — a public colleague keeps to its job#
13 October 2026
- A public colleague keeps to the job its description gives it and declines anything else in one sentence. When nothing you published covers a question, it says so instead of answering from what it happens to know. See Its job is its description.
- Visitors no longer see the names of your files under an answer. Visitor questions still show which files each answer used. A web page an answer used is still linked.
Desktop 1.9.0 — Help, public colleagues, more files, and the web app’s routines#
13 October 2026 Desktop 1.9.0
- Ysra help from every screen: Help in the rail (Cmd+/) opens a panel on the right. Get the apps is in the account menu. See Ysra help.
- Public colleagues: Anyone with the link can ask on a colleague you own, and Library → Visitor questions. An colleague says which workspace it belongs to. See Public colleagues.
- Files: more kinds, up to 100 MB each. A file being read shows its progress on its chip and in Library → Files; one that can’t be read says why. See Files you can upload.
- Ask starts with Build’s box: attach, microphone, the colleague, and Answer or Deep dive.
- Routines are the same screens as in the web app: cards, a page for each routine, and a new routine planned as a dry run before it is activated. See Create a routine.
- Library shows the open page’s docs at the right. An unverified email shows a quiet line in the sidebar with Send the link again.
Also since 1.8.0:
- 1.8.1: a folder without Git works as it is, with no question and nothing added to it; Set up Git here… is there if you want your own history. Where is one searchable list of this computer and your devices.
- 1.8.2: the app never opens on a blank window; if it can’t start, it says so and where its log is.
Web app 1.14.0 — Help beside the page, Start here, and routines as on the desktop#
13 October 2026 Web app 1.14.0
- Ysra help opens in a panel beside the page you are on. It is free, 20 questions a day, even when credits are out or the account is paused. Help conversations stay out of Ask’s list; Cmd+K finds them. See Ysra help.
- Start here: examples you can run, each saying what it needs and whether you have it. Home, Ask, routines and colleagues link to it. See Start here: examples.
- Public colleagues: Anyone with the link can ask on a colleague you own, with its limits and the websites its chat button may be on. Library → Visitor questions lists what visitors asked, those waiting for a person first. See Public colleagues.
- Files: PowerPoint, Excel, CSV and TSV, web pages, JSON, RTF and images, besides PDF, Word, Markdown and text, up to 100 MB each. A file says what Ysra is doing while it reads it, and what wasn’t read. See Files you can upload.
- Ask starts with the same box as Build, with the colleague, Answer or Deep dive, and Sources under it. Suggested questions fill the box instead of sending. The sidebar lists Answering, then Earlier. See Ask.
- Routines use the desktop app’s screens: a card for each routine, a page for each with its plan, runs and approvals, and New routine with Plan it, a dry run, before Activate routine. Changing a routine still uses the Edit screen. See Create a routine.
- The Build list and Cmd+K say “threads”. Library → Memory is headed “Memory”.
3.1.0 — colleagues anyone can ask, free help, and more files read#
13 October 2026
Colleagues anyone with the link can ask
- An colleague can be published with its own link. Its owner chooses the files a visitor’s question may read, whether it may search the web, and limits per visitor and per day, with an optional monthly credit ceiling. A visitor needs no account; answers use the owner’s credits. See Public colleagues.
- A visitor can leave a question for a person. Anyone in the owner’s organisation can reply, and the visitor sees “The team”.
- A chat button for your own website, from one line of code, working only on the websites you list. Its colour, light or dark, and corner are options.
- Answers appear as they are written. When a limit is reached, or the owner’s credits run out, visitors read that the assistant is resting, never an error. When many people ask at once, they are asked to try again in a moment.
Ysra help
- Questions about using Ysra are free: 20 a day, answered from these docs and what your account has set up, even when credits are out or the account is paused. See Ysra help.
Files
- Scanned PDFs, photos of documents and uploaded images are read; charts and pictures in a PDF are described in words. Reading a file uses no credits.
- New kinds: PowerPoint, HTML, JSON, TSV and RTF. Older
.doc,.xlsand.pptfiles are refused with what to do instead. - Up to 100 MB a file, 2,000 pages per PDF, 200,000 spreadsheet rows. Over a limit, the file is still accepted and says what was read. See Files you can upload.
- A long file shows how far its reading has got. Reports and spreadsheets Ysra makes can be searched in later questions.
- A long file attached to a question is read to the end, and a question about a file still being read waits for it.
Answers and routines
- An answer that reaches its length limit is finished instead of stopping mid-sentence. Summaries and questions about attached files get more room.
- A research routine writes a summary of what it found.
- A routine can only use your own connected tools and its workspace’s sources, and can’t be moved while it still reads another workspace’s.
Build
- On your own computer, Ysra no longer keeps restarting a preview it can’t reach.
- A review that runs out of room still gives its verdict.
Web app 1.13.0 — Help, and the apps for your computer#
12 October 2026 Web app 1.13.0
- Help, at the foot of the rail: Ask Ysra opens Ask with “How can Ysra help?” and three questions to start from; Ysra answers from what your account has connected, what is missing and what waits on you. The menu also has Read the docs, the docs page for where you are, What’s new and Get the apps. See Ysra help.
- Ask Ysra about this where you are stuck (no repository or folder to work on yet, a routine that can’t be activated) opens Ask with a question about it in the box, unsent.
- Get help in an Ask conversation sends it to the Ysra team, with an optional note. They reply by email. See Get help from the team.
- Get the apps, from a button at the foot of the rail, the account menu and Cmd+K: the desktop app for this computer, the command line’s one-line install with a copy button, and how to get the phone app. Home says once, “Ysra also runs on your computer”.
- Finish setup on a routine that was never activated finishes that draft, instead of making a second routine. A draft can also be archived.
- After signing in, or accepting an invitation, you land on Home. Library, Account and routines pages link to their docs page.
3.0.10 — Ask answers from these docs#
12 October 2026
- Asked how to do something in Ysra, Ask answers from these docs and links the page it used. See Questions about Ysra itself.
3.0.9 — Ask answers for the person asking#
12 October 2026
- Ask knows facts about your account (your role and what it may not do, your credits, which tools are connected or missing, what is waiting on you), never their content. When one of them is in your way, the answer says so first, with where to fix it or who can.
3.0.8 — Ask knows every part of Ysra#
12 October 2026
- Asked about Build, Ask, colleagues, routines, Machines, devices, integrations, the Library or the apps, Ask answers with the steps and the docs page, instead of asking what you mean.
Web app 1.12.3 — a reply that couldn’t do what was asked#
11 October 2026 Web app 1.12.3
- A reply that couldn’t do what was asked is a warning card, never an ordinary answer, whatever the reason: the folder isn’t connected, the app on that computer is too old, a commit, delivery, preview, deploy, undo or rewind can’t happen (the card says why), a device or the place to run it isn’t available, or the reply waits for an answer. Try again sends the last message again where that can help. See How a session can end.
- A setup question ("I need X. Want me to install it?") can be answered in the web app: I’ve done it (Ysra carries on), Show me how (Ysra replies with the steps) or Not now ("Okay. Say continue when it’s ready."). Installing it for you is still done on the computer that shares the folder, and the card says so.
- In Ask, a conversation handed to Build several times shows its two newest "Built in" links and "and N more", on one line.
- Under the routines runs: "These are the 40 most recent runs.", when there are that many.
Web app 1.12.2 — a paused thread says why#
11 October 2026 Web app 1.12.2
- A paused thread is under Needs you, never under Running, and its row says what happened and what to do: "Built, not verified. Open it to look at the change or say what to check", "Stopped before it finished. Open it to continue" or "Paused at its budget. Open it to continue". A thread that has just stopped leaves Running straight away.
- A reply that couldn’t start the work is a warning card: "This folder
isn’t connected. Open it in Ysra on that computer, or run
ysra servethere.", with Try again, or "Update Ysra on that computer to change this folder." - A setup question from a device is shown in the web app, with "Answer this on edge-01." (the device’s name).
- Plain words: Deploy, Inspect, a thread’s history, Integrations and the sign-in page say "the change" and "where it stopped".
CLI 1.7.3 — why a run paused#
11 October 2026 CLI 1.7.3
ysra exec’s result says why a thread is paused:pause_reason. See Run Ysra from a script.- A turn Ysra couldn’t carry out (the folder isn’t connected, the device is unavailable, …) ends the run as failed, with the reason; a question to answer first stops it for a person.
- Under
--approval auto, a stop whose only choice is Carry on is answered with it, three times at most. - An approved install in a container is waited for; the run no longer ends while it is still running.
- The connection is tried again when it drops.
3.0.6 — clearer setup steps#
11 October 2026
- A setup step says what it is doing in one line, for example “Getting jq ready: apt-get install -y jq”.
- A declined request still reads as declined when Ysra can’t try another way.
3.0.5 — fixes for work in your own folder#
11 October 2026
- Writing several files at once to a folder on your computer no longer reports a failure after the files were written.
- Commands, processes and previews in your own folder always run from a place
inside it. A task that names an absolute path, such as
/app, is told what to use instead. - Approving a plan while a question is still open says what it is waiting for.
CLI 1.7.2 — ysra exec for unattended runs#
11 October 2026 CLI 1.7.2
- A run ends when the work ends: changes written but not every check finished
is
unverified, exit0, with the summary. - The task is sent only once the folder is connected; a folder that can’t be connected is a failure, never “done”.
- In a container with
--approval auto, or with--yes-i-am-sandboxed, running as root or with password-lesssudo, Ysra installs what the work needs withapt-get,apk,dnforyum, and Git when it’s missing. - A declined task is
refused, exit code4. - Every
stream-jsonline carries a timestamp (ts). ysra updatetries again when the connection drops.- See Run Ysra from a script.
3.0.4 — saying what really happened#
11 October 2026
- A repository with no tests: Ysra checks the change itself (runs the
program, a sample input or the page, or a small test of its own) and names
what it ran: "This repository has no tests, so I checked it myself:
python cli.py --helpworked." If nothing ran, it says so, and never reports checks as passed. See A repository with no tests. - A declined request is tried another way once; if that is declined too, the work ends with a plain message. Ask answers say so too.
- Stopping work that changed files asks "Want me to carry on from here?", with Carry on.
- Routines: an approval nobody answers is withdrawn after 7 days and the run ends cancelled; a step Ysra says it didn’t do fails in its own words; research that finds nothing says so.
- Ask: an answer still missing the spreadsheet or PDF it owed says so and is marked incomplete; a question from an app that closed says so after 5 minutes.
- Plain words: summaries of the work read like "Done: 2 files changed. Checks passed: 3 of 3; …", with no commit hashes or internal terms.
- In a container where
ysraruns as root, Ysra may install withapt-get,apk,dnforyum.
CLI 1.7.1 — a clearer sign-in#
10 October 2026 CLI 1.7.1
- Sign-in problems say what to do instead of "You're not signed in".
ysra doctorshows where your sign-in was found.- On Linux, a sign-in kept in the owner-only file is no longer hidden by an older one in the system keyring.
Web app 1.12.1 — choosing where a thread works#
10 October 2026 Web app 1.12.1
- The Folder or repository chip opens a searchable list: each of your devices with the folders it shares, then Hosted repositories (GitHub repositories not added yet come after, and choosing one adds it). The most recent first; type to filter, arrows, Enter and Esc. A device that isn’t connected shows the folder used last time, marked, and it can’t be picked. See Where.
3.0.3 — the sidebar and a routine’s plan on the web, and sign-in for scripts#
10 October 2026 CLI 1.7.0 Web app 1.12.0 Desktop 1.8.0 Mobile 1.6.0
Web app 1.12.0
- The sidebar the desktop app has: a rail of icons, with names on hover, and a panel for the section that’s open. Home and Build open on the message box; their threads are in the panel. See A tour.
- A routine’s plan as a chart: Draft a plan, change the steps and Save plan, each save a new version. See A routine’s plan.
CLI 1.7.0
ysra auth tokenprints a short-lived access token from this computer’s sign-in, for scripts.ysra --resume,ysra --resume <thread>,ysra --continueandysra resumeopen an earlier conversation. See Commands.
Ysra 3.0.3
- Invitation and build emails say Ysra in their subject, header and footer.
3.0.2 — organisations, a routine’s plan, and running Ysra from a script#
10 October 2026 Desktop 1.8.0 CLI 1.6.0 Web app 1.11.0 Mobile 1.6.0
The short version is in What's new. Ysra 2.6.0 to 3.0.2 were released on 9 and 10 October; this entry covers them together.
Organisations
- An organisation shares one balance, one plan, its settings and the keys it runs on. Conversations, threads, files, routines and colleagues stay each person’s own.
- Roles: Owner, Admin and Member, with a Billing switch an owner gives to whoever pays. Invitations by email, accepted or declined in the app.
- People is under Account in the web app and under Settings in the desktop app. See Organisations and roles.
Credits
- Ask answers and Build work say how long they took, beside the credits that one stretch used: "Worked for 3m · 48 credits". See Credits and usage.
Routines
- A routine’s plan is a chart of When, Read, Do, Decide, Act and Deliver steps. Ysra drafts it; you change it and save, and each save is a new version. Steps that need something the routine hasn’t been given say so. An Act step can ask first. A run marks each step as it goes. The chart is shown and edited in the desktop app. See A routine’s plan.
Build
- A folder lent from your computer brings its own instructions (
AGENTS.md,CLAUDE.mdand the like), applied to the work in it. - The words at the end of the work are plain: "Every check that applies to this change passed…".
Desktop 1.8.0
- A new sidebar: an icon rail with names on hover, and a panel.
- Local folders: Ysra keeps its own history of your changes outside your
folder, never adds a
.gitand never commits unless you ask. - People, and a routine’s plan as a chart.
CLI 1.6.0
ysra exec(alsoysra -p) runs one task to the end and exits with 0 done, 1 failed, 2 needs a decision or an answer, 3 out of credits. See Run Ysra from a script.ysra askwith--file; files in the answer are saved in the current folder, never overwriting one.ysra --helplists every command, flag and environment variable. See Commands.- Project instructions (
AGENTS.md,CLAUDE.md…) are read with the folder.
Web app 1.9.0 to 1.11.0
- People and roles (1.9.0), the time work took (1.10.0), and one layout, the thread layout (1.11.0). The Playbooks page is gone from Library.
Phone
- The phone app is 1.6.0.
2.5.0 — Ask works with files and the rest of Ysra#
9 October 2026 Released with 2.4.0. The short version is in What's new.
- Spreadsheets can be attached:
.xlsxand.csv, wherever PDF and Word files are, read sheet by sheet and searchable. Older.xlsfiles are refused, with a line saying to save as.xlsxor.csv. - A spreadsheet in the conversation, made earlier or attached, can be changed: charts, rows or sheets are added and everything else is kept.
- The request sets the depth of research: a number such as "50 companies", or reading each one's website, is the scope. The answer says how many it reached.
- Hand to Build and Automate this say what they would do for each answer, or that it doesn't fit.
- A routine drafted from an answer gets a name, a job description and a schedule, and stays linked to the conversation both ways. It can open the conversation's files and update a spreadsheet among them; each run starts from the last run's version.
- A Build thread started from an answer gets the contents of the conversation's files.
@mentions point at a file, an Ask conversation, a Build thread, a routine or a colleague. They're read, never run, and reach only your own things.- See Ask.
2.4.0 — credits, plans and billing#
9 October 2026 Desktop 1.5.0 CLI 1.5.0 Web app 1.8.0 Mobile 1.6.0
The short version is in What's new.
Credits
- Credits are the one unit for usage: threads, routines, Machines and Ask all use them. A new account gets 500 free credits once its email address is verified, once per person.
- The Usage page shows credits left, a daily chart split by kind of work, and
what used them;
ysra usageand/usagein the terminal (/costis the older name). - A warning shows at 10% or less left. When credits run out, work pauses before its next step, keeps everything, and continues when you tell Ysra to.
- See Credits and usage.
Billing
- Plans: Starter, Pro, Max, and Team by the seat, each with monthly credits. A bigger plan is charged the difference and applies at once; a smaller one starts at the next renewal. Cancelling keeps the plan until its end date, and Resume plan undoes it.
- Credit packs add extra credits, kept until used.
- Several payment methods, with a default; Make default and Remove.
- Automatic top-ups, off by default, with a threshold, a pack and a monthly limit, and an email for every charge.
- Invoices for every payment, each with a PDF.
- One person pays for an organisation; everyone else sees the usage.
- Everything is paid inside the web app, or in a secure window of the desktop app. The phone shows billing without changing it.
- A paused account says so in every app, with the address to write to.
- See Plans and billing.
Ask
- Answers can be spreadsheets, as an Excel workbook or a CSV. See Spreadsheets.
Account
- Signed in on lists Support access: each time Ysra support viewed the account, read-only. See Support access.
2.3.0 — signing in from the browser, and editing routines#
7 October 2026 Desktop 1.4.0 CLI 1.4.0 Web app 1.7.0 Mobile 1.6.0
The short version is in What's new.
Signing in
- The desktop app and the CLI sign in from your browser; you choose Allow
in the web app and they never see your password. Over SSH,
ysra loginprints a code to enter in the web app. A password remains the fallback. - Signed in on lists every app signed in to your account in the web app,
the desktop app and the phone, with Sign out and Sign out
everywhere;
ysra sessionsandysra logoutin the terminal. - Forgot password? mails a one-hour, one-use link; resetting signs every app out. New accounts verify their email with a link that lasts 24 hours.
- After several wrong passwords, sign-in for that address pauses for a while.
- See Sign in and where you're signed in.
Routines
- Routines can be edited after creation in the web app, the desktop app and the phone. Each save is a new version, and runs already started keep their instructions. See Edit a routine.
Colleagues
- A new colleague starts with all nine capabilities, in every app.
On your phone
- The option chips — Build or Plan first, model, effort and colleague — at the start and inside a thread, remembered for each workspace.
- Start Build work on a device's shared folder from Folder or repository.
CLI
- A second install with its own
YSRA_HOMEhas its own sign-in, device identity and saved state.
2.2.0 — machines, gateways and deploying#
7 October 2026 Desktop 1.3.0 CLI 1.3.0 Web app 1.6.0 Mobile 1.5.0
Ysra now looks after fleets of machines and puts work live on your own servers. The short version is in What's new.
Machines and gateways
- "Targets" are now machines. A machine is a computer you manage through a
gateway. Commands move from
ysra target …toysra machines …; the older name still works, and the file~/.ysra/targets.jsonkeeps its name. See Machines. - Gateways: one always-on device inside a network holds the machines it
reaches; addresses, users and keys stay on it. Add many at once with
ysra machines import. See Machines and gateways. - A Machines page lists every machine in a workspace, with groups, tags and its last status. See Machines.
- A Machines panel in threads: a health bar, search by kind, status, group, site or tag, selecting many machines at once, and a run sheet that checks whether a signed approval covers the run. See The Machines panel.
Approvals and automatic runs
- Signed approvals: allow kinds of action on named machines ahead of time, until a date at most 90 days away, signed with a key that stays on your computer. The gateway's owner decides whether they count. See Approvals and automatic runs.
- Runbooks on a schedule, with a dry run on each machine first.
- Investigate and fix: when a check fails in an automatic run, Ysra looks at that machine and fixes it only from a source it cites, then offers to add the fix to the step's If it fails.
- Gateways that run on their own ask for a signed approval instead of waiting for a click.
Putting work live
- Deploy a folder to a machine, with the whole file tree on the card, a list of what is left out on purpose, and the previous version kept. See Deploy a folder to a machine.
- Write a file on a machine, approving the diff. See Write a file on a machine.
- Ysra decides where to deploy from what you said and what the project has, asks when it isn't clear, and never asks for passwords. See Deploy a site to your server.
nginx -tandnginx -vcount as looking; reloading nginx is a service action.
The desktop app
- A new sidebar: Devices at the top of Build, Time, Folder and Device views, and New thread on… (Cmd+N). Runbooks has its own mode (Cmd+7).
- Settings is a page, with new Approvals and Appearance sections. Engines & accounts is now Accounts.
- The colleague chip in a thread's header, changeable mid-thread.
- Copy on every message, answer, code block and output, and a file view with a folder tree.
- The autonomy choice (Governed or Max) is gone; every thread works the same way.
Also
- When Ysra ends on a question, the thread waits for your answer (Needs your input) instead of stopping.
- Continue on a device folder picks up from the same starting point, and never touches files you changed.
- Commands can't read secret stores in your folder or your home folder, and leave nothing behind in your folder.
- The web app has a Runbooks page and can start a thread on a device's folder; the phone has a Machines sheet and lists approvals.
Desktop 1.1.1 and CLI 1.1.1#
4 October 2026 Desktop 1.1.1 CLI 1.1.1
Fewer interruptions on Windows when you aren't using WSL.
- Safe read-only commands run without a card: listing and reading files,
reading Git (
git status,git diff,git log…), version checks andnpm ls. Anything with redirection, a shell, a recursive search, a secret file or a path outside the folder still asks. - "Allow for this session" covers the whole program: allowing
npmcovers everynpmcommand in that session. It is never offered for shells or inline code, and pushing, publishing, deploying, sign-in and Git remote changes always ask. - Run commands without asking, per session: let commands run without
asking for the rest of a session — its own chip in the desktop app's message
box, and part of
/auto onin the CLI. That part is never remembered: a new session asks again. A warning appears when you turn it on. Pushing, publishing, deploying, paths outside the folder and shells still ask. - The timeline says how each command ran: without asking (safe read) or without asking (auto).
See Ysra Desktop on Windows and Ysra CLI on Windows.
Desktop 1.1.0 and CLI 1.1.0#
4 October 2026 Desktop 1.1.0 CLI 1.1.0
Ysra now works on Windows, in the desktop app and in the terminal.
The CLI on Windows
- Install from PowerShell with
irm https://ysra.ai/install.ps1 | iex. No administrator rights are needed, and the download is checked before it is installed.ysra updateandysra uninstallwork there too, and your sign-in is stored encrypted. See Ysra CLI on Windows.
Commands on Windows ask first
- Windows has no way to contain a command to your folder, so every command shows the exact command and folder and waits: run it once, allow that command for the session, or refuse. Shells and inline code are never allowed for a whole session, a refused command isn't retried, and no answer counts as no.
Contained commands with WSL
- If you have WSL, commands can run inside it, contained as on Linux, with no
card for each one. Turn it on with
ysra wsl, or in the desktop app under Settings → General. Ysra never installs WSL itself. See Ysra Desktop on Windows.
Also on Windows
- Files keep their line endings, stopping ends everything a command started, and names Windows treats specially are refused.
- The Windows installers aren't signed yet, so SmartScreen still warns on first run.
2.0.0#
3 October 2026 Desktop 1.0.0 CLI 1.0.0
Ysra now works where your work lives: on a folder on your own computer, on a server or edge device you sign in, and on remote machines you approve — always asking before anything leaves the folder. This release introduces the desktop app and the CLI.
Work on your own folders
- Open a folder in the desktop app or the CLI and ask a question or describe a change. Reading, editing, running your checks, previews and review all happen on your machine. A folder without Git works too. See Work in a folder.
- Commands run in a contained space: they can write only inside the folder you opened, and anything that reaches outside your computer — a deploy, a publish — asks first, every time.
Commit, push and your CI
- Git changes happen only when you ask. Commit on a new or an existing branch without your folder being switched or overwritten; a push always asks, and is never forced.
- After a push, your repository's own CI is read back and reported in the conversation. See Commit, push and undo.
Undo
- Undo puts back exactly what one task changed, with or without Git, and refuses if you have edited those files since.
Getting your machine ready, with your OK
- A missing tool, a stopped service or a tool that isn't signed in pauses the task with one specific proposal: your package manager, an official download with a verified checksum, starting the app, or steps for you to take. Side effects are shown before you agree.
- Docker is allowed per session, asked once, and your registry sign-ins are never read. See Tools, setup and Docker.
Devices
- Sign in a server or edge device with a short code, share folders from it, and work on them from your own computer. Devices start in observe mode; camera and GPU access is asked per session. A device's sign-in reaches only that device's own work. See Devices.
Remote targets and runbooks
- Work on machines where nothing can be installed, over your own SSH or command-line sign-in. Fixed rules can only raise a command's risk, every change is approved on the exact command, and destructive steps on production need the target's name typed.
- Runbooks run a written procedure step by step and stop at the first failed check, showing its recovery step. Where your targets are never reaches Ysra's servers. See Targets.
No budget prompts
- Starting work no longer asks you to authorise a spending ceiling. Sessions draw from your wallet, and the only money message is that your balance is low.
Faster and steadier
- A large review copy on your machine no longer stalls other work, and a client that disconnects in the middle of a command pauses the task instead of letting it continue unseen.
1.4.0#
26 September 2026 Backward compatible
Answers in Knowledge are kept safe when they stop early, research shows its progress, routines can search the web and Gmail, and Developer sessions no longer get stuck at the end.
Knowledge
- Your question is kept even when an answer is cancelled or fails, and a question shows whether it is waiting or being answered.
- Research shows its steps while it runs: searching, reading pages and PDFs, and writing the report.
- A link straight to a PDF is read as a document.
- PDF reports come with a short review of how they look. It never holds the report back.
Routines
- Routines can search the public web and a connected Gmail mailbox, once you allow it. Gmail access creates drafts only; nothing is sent.
- Routines can be paused, resumed and archived; each edit is a new version; waiting and running runs can be cancelled.
Developer
- A session no longer gets stuck on a Continue that does nothing. Its work is kept, marked as not verified, and picked up on your next message.
Nothing to do on your side
Existing sessions, routines and settings carry over unchanged.
1.2.2#
23 September 2026
- Developer sessions can use third-party APIs you have approved. Your keys never reach the repository or the workspace.
- Every outside call respects the session's network setting.
start previewin a conversation shows the work you already have instead of starting new paid work.
Earlier releases are summarised in the product's release notes.