Capabilities
The models Jade works with, the tools it can use, what always asks first, and what it can’t do.
Models
Jade works with the model you choose, from several places at once.
| Kind | Talks to | Sign-in |
|---|---|---|
| OpenAI | OpenAI’s chat API (/v1/chat/completions) | API key |
| Anthropic | Anthropic’s Messages API | API key |
| OpenAI-compatible | OpenRouter, Groq, Together, LM Studio and others | Key, if the server wants one |
| Anthropic-compatible | Any server that speaks Anthropic’s format | Key, if the server wants one |
| Ollama | A model server on your own network | None |
| On-device | A model that runs on the phone | None |
| Jade AI | Models Jade provides, at four levels: Auto, Fast, Expert, Ultra | A Jade Pro or Jade Max plan (Ultra: Jade Max) |
- Fallback. When a model fails, Jade tries the next one, starting with other models from the same provider. Ultra is never used as a fallback.
- Per chat. Each chat can use a different model.
- Keys are kept in the Keychain and are never in an export or a log.
Tools
Tools are what lets Jade do things instead of only talk. A model picks the tools; Jade decides whether to ask first.
- Web
- Search the web and read pages. Pages and results are treated as data, not instructions.
- Browser
- Open pages, read them, follow links and fill in forms in a browser of its own. Passwords are typed from stand-ins, and a CAPTCHA hands over to you.
- Files and documents
- A workspace of files inside the app. Read and write files, save the reports and tables a task makes. Files from the Files app and share sheet are copied in.
- Terminal
- A sandboxed shell over the app’s own file workspace (ls, cat, grep, find, pipes and more). No process is started, so it can’t reach anything else on the device.
- Running code
- Python (with pip packages) and JavaScript (with npm packages from esm.sh), in a sandbox. Each run asks first unless you set Always allow.
- Code workspace
- Copy a repository, run commands, and send back a patch, in a throwaway workspace (on a Jade Cloud with the code service). Tools come from Homebrew (
brew install jq), plus pip and npm. There is no sudo or apt. - Memory
- Remember things between chats, and notes about websites it has used.
- Pictures
- Ask for a picture in a chat and it shows up in the reply (Jade AI Images, with a plan).
- Voice
- Dictation, voice calls and spoken replies.
- Your device
- Calendar, Reminders, Contacts, Notes and Shortcuts, plus other Apple apps. Each has its own switch and its own read and write permission, on top of the system’s prompt.
- Services (MCP)
- Any remote MCP server: GitHub, Linear, Stripe, your company’s own tools. See MCP.
- Skills
- Code Jade wrote for itself and saved after you read and approved it. A skill runs in the same sandbox as other code.
- Script apps
- Apps from the marketplace: small scripts that run on your device and show up as tools. They ask for each kind of access.
Cards
A reply can contain a card instead of plain text. Jade has cards for charts, weather, calendar events, maps, links, documents, JSON, SVG and HTML. If you keep asking for the same kind of answer, Jade designs a card for it and saves it (Settings → Apps & tools → Cards). Script apps can bring cards of their own, and a card’s page runs with no network access.
Tasks and routines
- Plans you can edit. A task is written as steps. You can reword, add or take off a step while it runs.
- Retries and fallbacks. A failed step is tried another way. Steps that can’t be done are skipped, not fatal, and the result says what is missing.
- Results with sources. The write-up links to what it used and flags what you should check.
- Routines. A prompt on a schedule, like every weekday at 8. Each run is a task.
- Webhooks. Another service can start a task through a private address. What it sends is treated as outside content.
- Live Activities. Progress and approvals on the Lock Screen and in the Dynamic Island.
What always asks
Three layers decide whether something runs. A tool can be allowed, asked about or blocked. A connection can be switched off. And changes to Jade’s own settings always ask.
- Spending money, sending messages, deleting things, running code, and clicking or typing on websites ask first.
- A tool from an MCP server counts as high risk unless it only reads. The server can say so, or you can (“It only reads”).
- In a task, anything that came from outside (a web page, an MCP result, a webhook body) makes high-risk tools ask again, even ones you always allow. A tool whose name suggests it can spend money always asks.
- An assistant that changes a setting shows the change and asks, every time, and you can undo it.
Plans and limits
| Free | Jade Pro | Jade Max | |
|---|---|---|---|
| Price | $0 | $4.99 a month | $12.99 a month |
| Models | Your own keys, or on-device | Jade AI (Auto, Fast, Expert) | Jade AI, plus Ultra |
| Where tasks run | On the phone, while iOS allows | Jade Cloud | Jade Cloud |
| Task time | — | 5 hours a week, 100 new tasks a day | 3 times as much |
| Pictures | — | Included, with a weekly count | 3 times as many |
Prices are from the App Store and vary by country. Pro and Max have a 1-week trial. A Jade Cloud that you host yourself has no plan limits.
What Jade can’t do
Some limits come from iOS, not from Jade.
- Run in the background forever
- iOS pauses an app soon after it is closed. A task on the phone carries on for a short grace period. For more, Jade Cloud runs it on a server.
- Use local servers over stdio
- MCP servers that start as a local process can’t run on iOS. Run the server somewhere and connect to it over HTTP.
- Run a real shell
- The terminal is a safe stand-in over the app’s own files. It can’t reach other apps or system files.
- Read Mail or Messages
- iOS gives apps no way to. Jade can open a draft in the system’s compose sheet, and you tap Send.
- Reach Health data
- Not offered.
- Control other apps
- Only through what iOS offers: Shortcuts, App Intents, the share sheet and the document picker. Notes works through two shortcuts you make.
- Use device data from the cloud
- Calendar, reminders, contacts, on-device models and the app’s file workspace stay on the phone. A task on a server can’t use them.
- Solve CAPTCHAs
- It stops and hands over to you.