Private AI, on your phone.

My node on iPhone too, what your machine did at a glance, recipes that run on your node, and the team of agents your machine can now run.

My node on iOS

• Pair your computer in Settings › Providers › + › My node (Invincible). Paste the code, or open the invincible://pair link from the camera.
• Chats, signed receipts and "phone first, then my node" all work as on Android.
• The agent screen. Remote › Agents · my node: tasks on that machine, approval cards, and scheduled tasks.

What your machine did (Android and iOS)

The list button on the agent screen opens the node's Activity, read from its own logs:

• Requests: every request the node answered: who asked, which model, tokens, and whether anything left. Each receipt is checked against the key pinned at pairing.
• Actions: what the agent ran, and who allowed it.
• Memory and skills: what the agent remembered (you can make it forget), and your skills.

Recipes on your node

• Runs on in the recipe editor: this phone, or your node.
• On the node, a recipe runs on its schedule, always on and with no 8-minute limit, on the node's models, with only the recipe's tool groups (web included).
• Your time, wherever the node is. "07:00" means 07:00 where the phone is.
• Results come back as chats in the Recipes folder, with the node's signed receipts and a notification.

A team on your machine

• Team members. When the node's agent has a team, each member's answer shows under its name.
• You know who's asking. An approval says which member wants it ("coder: Run a command?").
• New approval cards for web fetches and MCP tools.

Fixes

• Several CI tests that depended on timing are steadier.

Your own computer as Autobot's next tier: pair a machine running Invincible, chat with its models, hand its agent tasks you approve from the phone, and check what it signed.

My node (Android)

• Pair a computer. Install Invincible on a desktop or VPS (curl -fsSL https://raw.githubusercontent.com/wckdboy/invincible/main/install.sh | sh), run invincible pair, and scan the code with the camera app (or paste it). Settings › Providers › My node (Invincible). No account, no relay: the phone and the node pin each other's keys (Noise).
• Chat with its models like any provider. Connections follow the kill switch (offline refuses them; Tor and SOCKS5 carry them with remote DNS) and show in the Privacy Center's audit log.
• Signed receipts. Every answer from the node is checked against the receipt key pinned when you paired: the receipt line says "kept on studio ✓" when nothing left the node, "studio → 1 host" when it used a cloud model (with the hosts, routes and what it redacted), or "studio unverified".
• Phone first, then my node. With "phone first" on a node chat, this phone answers first and a weak answer goes to your node instead of a cloud model. The node is hardware you own, so a sensitive prompt may go there and "Never" allows it; these turns are marked private, so the node never sends them on to a cloud model.

The agent on your machine (Android)

• REMOTE › Agents · my node. Give the Autobot Agent running on that machine a task: shell commands and file work, on its models. Every command, file write and read outside its working folder comes to the phone as a card first: Allow, Always (this conversation) or Deny.
• Scheduled tasks. The calendar button lists what the agent runs on a schedule (next run, how the last one went), adds tasks (cron, @daily, every 30m) and removes them. Scheduled runs only do what you allowlisted.

Fixes

• Node chats no longer show a REDACT chip: nothing is redacted for hardware you own.
• The streaming check with a real node leaves room for thinking models.

iOS: the pairing and receipt code is shared and tested on CryptoKit; the iOS node connector comes next, so "My node" says "not on iOS yet".

Images come out the shape you pick, a full-screen viewer, recipes that run on their own, phone-first answers and a panic PIN.

Images (both platforms)

• 16:9 means 16:9. Picking a wide or tall shape could still give a square: on-device models compiled for one size (Core ML on iOS, QNN on Android) quietly swapped your size for theirs. They now render their square and return your shape cut from it, and Tune says "compiled for 1024² · other shapes are cut from the square".
• The resolution is a pixel budget. 16:9 at 1024 is about a million pixels in that shape (1368×768), so wide images keep the detail of the square. Every shape chip names the exact size it makes, and the picker remembers your choice instead of snapping back to 512.
• Picking a model keeps your shape instead of resetting to its square. MNN sizes round to the nearest 64 instead of always down.
• A server that sends back a square anyway is cut to your shape (Android) or named in a notice (iOS), and the gallery records the size it really got.
• Full-screen viewer. Tap a result, a gallery image or an image in chat: pinch or double-tap to zoom, pan, swipe through the batch, swipe down to close. The info sheet shows the real pixel size and every setting used.
• Do more with an image: use it for img2img (prompt and settings carried over, strength showing), inpaint, vary, reuse settings, same seed, upscale 4× (when an upscaler is installed), share, save, copy settings, favorite, delete.
• The agent's generate_image takes an aspect ratio and keeps the shape when given one side.
• img2img without an input image now says so instead of quietly running as text-to-image; Tune says when a model can't apply your LoRAs.

Recipes (both platforms)

• On-device agents on a schedule. Settings → Recipes: a prompt, a schedule, a model and the tools it may use. Runs in the background on the phone (WorkManager on Android, background processing on iOS), once for a missed time, safe across daylight-saving changes.
• A private notification opens the result chat after the app lock. While the phone is locked, iOS says "Unlock to run <name>". Recipe data is encrypted and goes with a wipe.

Phone first (both platforms)

• The phone answers first. Off by default. Settings → Privacy → Phone first (ask / auto / never) and a chip per chat: in a cloud chat the installed on-device model answers, and

Cleaner prints, a faster start, and dictation that keeps up: a polish release.

Cleaner ink (both platforms)

• No more doubled dots. On Android, the paper behind the Image screen, chat, voice, Models, Gallery and the lock drew every dot twice, with a faint copy a few pixels off. Paper is one plate again.
• Prints land on their own dots. When a result printed, its colour plate started half a dot away and read as a second grid. It now starts as a thin rim on the same dots and settles.
• Pictures print in where they show. A wide image in a square chat thumbnail or a Studio chip no longer prints a stretched copy next to the cropped one.
• One dot field per screen: the voice panel, the empty Models search and empty chat no longer stack a second field under the first, and image proofs sit on whole pixels.
• iOS: a halftone preview always matches its own image. A new image could pick up an old image's dots.

Faster (both platforms)

• Android starts sooner. The app now ships a Baseline Profile, so startup code runs precompiled even on a sideloaded install. On the emulator: 13–17% less time to the first real screen and about 20% less main-thread work.
• iOS starts sooner. Fonts and device checks load in the background, about 90 ms earlier to the first frame in the simulator.
• Live dictation shows words sooner and more often. Partial passes only encode the audio heard so far, 2–4× less work. Stopping usually has nothing left to transcribe.
• Faster draft-model checks. Each speculative step costs less, a draft that failed to load is retried later, and a failed check carries on without the draft instead of ending the answer.
• Image model warm-up. It loads again ahead of Generate after it was freed, switching models no longer loads both, and on Android it stays loaded while the Image screen is open.
• Smoother lists: the iOS chat list scrolls with fewer hitches, and Android's Models list only redraws rows that changed. Catalog previews and parsed chat text have a memory limit on iOS.

Fixed

• Read-aloud no longer cuts off the last words before the assistant uses a tool.
• Talking over a spoken answer no longer triggers by itself when the voice resumes after a pause.
• iOS: the last words you say before tapping stop are no longer lost from dictation.
• A quick double tap on the mic starts one dictation, not two.
• The Image scree