DocsJade Cloud

Jade Cloud

The server that keeps tasks, routines and webhooks running when the app is closed.

On this page
What Jade Cloud isPlansPairing and accountsSharing a serverCode workspacesThe cloud browserWhat can’t move to the server

What Jade Cloud is

Jade Cloud is a server that runs Jade’s agent. An iPhone is asleep most of the time, and iOS stops background work soon after an app is left. A task on the server doesn’t care: it carries on with the phone locked, off, or out of signal, and the phone picks the result up when it next opens.

Tasks
Started on the phone, then moved to the server when Jade closes (a setting), or started on the server directly. The plan, the steps and the approvals are the same as on the phone.
Routines and webhooks
Run on a schedule or when a web address is called. See Routines and webhooks.
Browser
A real browser the agent drives to open pages, read them and fill forms. The phone can watch the page while a task runs.
Code workspaces
A folder with a shell for coding tasks: clone a repository, run commands and tests, read and write files. See below.
Jade AI
Models that come with a plan, so no API key is needed. Levels: Auto, Fast, Expert, and Ultra with Jade Max. Pictures and natural voices too, within weekly allowances.
Live Activities
Progress on the Lock Screen and in the Dynamic Island, by push, even if the app isn’t running.

Plans

PlanPriceIncludes
Free$0Own keys or on-device models. Tasks run on the iPhone while iOS allows. All connections, tools and the browser on the device.
Jade Pro$4.99 a month, or $49.99 a year (1-week trial)Tasks, routines and webhooks in Jade Cloud. 5 hours of task time a week, 100 new tasks a day. Jade AI (Auto, Fast, Expert) and pictures.
Jade Max$12.99 a month, or $129.99 a year (1-week trial)Three times Pro’s task time, tasks and pictures. Jade AI Ultra, a model from another provider (it asks for agreement to that provider’s privacy policy first).
Own serverFreeRun Jade Cloud with Docker. No plan limits. See Self-hosting.

Prices come from the App Store and vary by country. Allowances reset weekly (task time, Jade AI tokens, pictures, voices) or daily (new tasks). When one runs out, the error says which and when it resets, and tasks can still run on the iPhone.

Pairing and accounts

There are two ways in. Both end with a device token that the app keeps in the Keychain.

  • A subscription. On the hosted server, the app sends the signed App Store transaction. The server verifies it with Apple’s certificates, makes an account (a random id, with no name or email) and pairs the device. Renewals, expiry and refunds arrive as App Store notifications.
  • A pairing code. On a server of one’s own, jade pair prints a one-time code (valid for 15 minutes, once). “Have a pairing code?” in the app takes it, or the link it prints opens the app on the phone.

More devices can join the same account with another code (jade pair --account ID) or from a paired device (POST /v1/pairing-codes). The account holds the tasks, files and settings, and every paired device sees the same ones.

Sharing a server

A server’s owner can give others access without a subscription, and limit it:

jade pair --plan pro                          # Jade Pro's limits, no subscription
jade pair --plan max --percent 25 --days 7    # a quarter of Max's limits, ends in 7 days
jade set-plan ACCOUNT pro --days 30           # change an existing account
jade accounts                                 # who has what
  • Each account is separate: its own tasks, files and settings, and its own sealed data.
  • --percent N scales the plan’s limits (1 to 99). --days N ends access N days after the code is used. When access ends, the app gets a plain message and the account’s data stays until it is deleted.
  • The code is the approval: whoever has it pairs. Keep it private, and use jade unpair to remove a device.

Code workspaces

For coding tasks, Jade Cloud gives each task a workspace in a separate container. The agent has tools to clone a repository, run shell commands, read and write files and use git, and the workspace is deleted when the task ends. A patch can be sent back to the app, which applies it in the code chat.

  • Tools in the box: git, Python, Node and the usual shell tools. Homebrew is there too, so brew install works for anything else. It runs on a separate helper behind a short list of allowed commands, so a task can add software without any way to change the container itself.
  • Network. A workspace has no route to the internet of its own. Its commands reach the web through the same filtering proxy as the browser, which refuses private addresses.
  • Isolation. Each workspace runs as a different user, and can’t read another task’s files.
  • Limits. Commands time out (30 minutes at most), and output is cut at a size that fits a model’s context.
  • GitHub. A token from Settings is sent to the workspace only to clone and push, and isn’t left in the repository’s config.
  • On a server of one’s own, jade code checks the whole path, including the proxy and Homebrew.

The cloud browser

Chromium in its own container, with no route out except the filtering proxy. Pages load, scripts run, forms are filled, and the agent sees a text version of the page. The app can show a small live picture of the page while a task runs (GET /v1/tasks/<id>/browser). Signed-in sites work when the app has sent its cookies (PUT /v1/browser/cookies) or a saved sign-in is allowed for Cloud tasks. A CAPTCHA stops the task and hands over to the phone.

What can’t move to the server

Anything that needs the phone: Calendar, Reminders, Contacts, Notes and Shortcuts, on-device models, and script apps that run on the device. A task on the server can’t use them, and says so when a step needs one. Remote MCP servers work from the server as well, with the token sent for that.

The data question is covered in Privacy and security.