Choose the right part of Ysra
Which part of Ysra to use for which job — Ask, Learn, colleagues, colleagues with a public link, routines, Code on your computer or in the cloud, and Mayz — where each runs, what it can use and what it costs.
On this page
Ysra has a few parts, each made for one kind of job. This page helps you pick the right one before you start: what each is for, where it runs and what it costs. Each part has its own pages for the rest.
When to use what#
| Part | Best for | Not for | Where it runs | Cost |
|---|---|---|---|---|
| Ask | A question answered from the web, your files and your connected tools, with sources; a chart or an interactive View; a Word file, deck or PDF. | Changing code (use Code); a job that repeats (use a routine). | Web app, desktop app, phone. | Credits for the model; a deep dive reads more. |
| Learn | Studying a course from your own files, with cards, practice exams and a tutor; or learning a new topic step by step. | A quick answer: use Ask. | Web app, desktop app. | Guides, cards and exams a few credits each; reviewing cards is free. |
| Colleague | A kind of question you ask often, answered the same way from the same sources. | A one-off question: plain Ask is enough. | Wherever Ask runs. | Same as Ask. |
| Public colleague | Answering people outside your team, through a link or a chat on your website, from files you choose. | Anything that sends or changes something, or reads your connected tools: it never does. | Its own page (no account needed) or your website. | Paid by the colleague’s owner, inside limits you set. |
| Routine | A job done again and again: a Monday report, a site check, draft replies to new mail. | A one-off job: ask it in Ask. | Ysra’s servers, started from Ask in the web or desktop app. | Capped at 200 credits a run by default. |
| Code on your computer | Changing code in a folder on your computer, with your own tools and commands. | Questions about documents (use Ask); work that must go on while the computer is off (use the cloud). | Desktop app or CLI, in your folder or on a device. | The model only: your computer does the running. |
| Code in the cloud | A GitHub repository, or a new cloud project with no repository, worked on while your computer is closed. | Work that needs internet beyond the code host and package registries; accounts without a plan (no plan, no cloud). | A cloud machine, started from the web app, the desktop app or the phone. | The model plus about 41 credits an hour for a standard machine. |
| Mayz | An independent review: what is wrong, how sure, what to fix first. | Making the fixes: Mayz changes nothing (use Code). | Your computer (desktop app, ysra mayz), or a cloud thread from the web, desktop or phone app. |
Usually 100–300 credits; a review stops at 300. |
Not sure? Start with Set up with Ysra
Set up with Ysra is a short, free talk about your company that proposes colleagues, a colleague with a public link, routines and build ideas, and creates only what you keep. It opens by itself the first time a new account signs in.
Where each app fits#
| App | What it has |
|---|---|
| Web app | Ask, Learn, colleagues (colleagues with a public link included), routines, the Library and your account: settings, integrations, credits and billing. Code in Ysra’s cloud, and Mayz reviews of cloud threads. Voice. |
| Phone (iOS, Android) | Ask and colleagues; starting and following Code threads (a GitHub repository, a folder on one of your computers, or a new cloud project) and Mayz reviews; voice; answering what routines are waiting on. Connecting tools, permissions and billing stay in the web and desktop apps. See Mobile app. |
| Desktop app (macOS, Windows, Linux) | Code on a folder on your computer or in the cloud, with review and approvals in a window. Ask, Learn, colleagues and routines too. See Ysra Desktop. |
| CLI (macOS, Linux, Windows) | Code from your terminal, in scripts and CI, and on servers and edge devices. See Ysra CLI. |
| VS Code and Cursor | Code threads on the open folder, with changes in the editor's diff view. See VS Code and Cursor. |
What each part can use#
One list decides which part may use which tool. 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. Every tool, with examples and costs: What Ysra can do.
| Part | Can use | Not here |
|---|---|---|
| Ask | Web search, reading pages, a real browser, PDFs from a link, your files, connected tools, Ysra’s docs, memory, your images, making and saving images, route links, PDF reports, spreadsheets. Proposes emails, posts and Jira changes for your approval; hands work to Code or a routine. | Changing code, or sending anything itself. |
| Colleague | What Ask can, as far as its owner’s capabilities allow (Web browser and Images are switched per colleague). | The same as Ask. |
| Public colleague | The files you publish, route links to your business, and web search and page reading if you allow it. | Your connected tools, memory, actions, the real browser, making images, visitors’ photos. |
| Code task | Project files, commands, previews, its own app test browser, Watch, screenshots of the app it built, web search, reading pages, a real browser, PDFs from a link, Ysra’s docs, route links, connected tools, making up to 6 images and saving web images. Publishes and deploys when you approve. | Memory across threads. |
| Code reply (answering in the thread) | Read-only: the project’s files, web search, reading pages, a real browser, PDFs from a link, Ysra’s docs, connected tools. | Changing anything: that starts a task. |
| Mayz | A private copy of the project, running and testing the app, Watch, web search and page reading for public lookups. | Changing your code, or acting outside its copy. |
| Routine | What it was given when it was set up: web search, reading pages, a real browser (with Watch), PDF reports, spreadsheets, images, connected tools. Emails and posts wait for your approval. | Starting other work, or publishing apps. |
| Voice | The tools of the thread it speaks in. | Anything that thread can’t do. |
| Set up with Ysra | Web search to find your site (it asks before reading it), reading your site in a real browser, saving its logo and photos. | Your connected tools. |
Related#
- Start here: examples — things to ask in each part, with what real runs cost.
- Quickstart — a first answer and a first code change.
- How Ysra works — the stages of every job.
- Limits and costs — what uses credits, and every cap.
- Walkthrough — two real runs, end to end.