Skip to content

Releases

v1.9.1

Choose a tag to compare

@github-actions github-actions released this 03 Sep 21:30

iOS 1.9.1 (15)

The ad-hoc build 1.9.1 (15) was produced by
this workflow run from commit
534c87b.

Commit 534c87bd6f40885d92fc2f2e05b59280d19ec351
Marketing version 1.9.1
iOS build number 15
EAS build 301a49f0-792d-4a0a-baa4-0e05f107e112
Ad-hoc IPA, SHA-256 e353712fae05c674889cab5d496eb3119dad90295bf2829debaaa271c96c5fca
JS bundle, SHA-256 55efae3770fe07c6985f06236ad0ce9831581371f7d92ebdebb2f8195aa4b979
Built at 2026-09-03T21:30:39Z

Verifying this release

Both artifacts carry a Sigstore attestation signed by
GitHub's identity for this workflow — not by the maintainer. A release published by
hand cannot carry one:

gh attestation verify main.jsbundle --repo oogxdd/coderoamer

The IPA is signed for the iPhones included in the EAS-managed ad-hoc provisioning
profile. Open the linked EAS build page on an eligible iPhone and tap Install.
main.jsbundle is the JavaScript extracted from that exact IPA, so it can be read and
compared against the source at 534c87b.

What this does not prove

This is provenance, not a reproducible build. You are trusting GitHub and Expo — but not
the maintainer's laptop. Nothing here lets you verify the copy after installation: iOS
gives you no way to extract and hash it. What you can check is that the published IPA
came from this public commit through this public workflow run.

v1.3.0 — First Release

Choose a tag to compare

@oogxdd oogxdd released this 10 Jul 16:33

🎉 First published release of Sprites Manager.

Run Claude Code inside a Fly.io Sprite (a cloud dev VM) and drive it from your phone. Set up a sprite once on your computer, then start, watch, and guide coding sessions from anywhere — close the app and pick the same session back up later.

Quick start

  1. Create a sprite — tap + on the dashboard, or use the Sprites CLI on your computer.
  2. Add an SSH key so the sprite can reach GitHub.
  3. Clone your repo into the sprite.
  4. Connect from the phone. Open the sprite, set the session working directory to your repo, type a prompt, and send.
  5. Come back anytime. Reopen the app and pick the same session back up.

The same flow is in-app under Guides.

Where this build came from

This is the first release published as a GitHub Release, but it isn't the first version of the app — it folds in everything built so far:

  • v1.0.0–v1.1.0 — sprite-screen redesign (conversation-list-first hub), per-sprite account connect, SQLite chat storage, terminal scrollback/copy/paste/gestures.
  • v1.2.0 — Codex app-server chat transport, a direct streaming connection to the native Codex integration.
  • v1.3.0 (this release) — chat reliability: auto-reconnect to in-flight runs with backoff/probing, one-tap retry for sends that never launched, message queueing while a turn streams, one-tap Continue on max-turns, reconciliation of stale Running flags, process-group kill for Stop, optional ntfy push on turn completion, token-level streaming for Claude, incremental crash-safe persistence, and unit-tested chat helpers.

Personal project against the Sprites API. Focused on Claude Code today; other agents later.