Vyre 0.2.2

Vyre 0.2.2 fixes four things people hit on a new server: surfaces locking each other out, a session with no Vyre tools, "no account" with one sign-in, and a message that looked unsent.

Fixed

• Your own phone, Deck and Mac are one participant in a conversation. They no longer lock each other out of typing, and another holder's lock cannot be joined by a tool or a hook that is not a person. (#38)
• A Claude session on a box now gets Vyre's tools even when the account has no ~/.vyre folder of its own. (#40)
• A provider's only account is its default, so starting a session never finds "no account" after one sign-in. An account name that reads empty right after sign-in is read again 15 seconds later. (#42)
• A message you send shows "Sending…" until the box answers, the box clears at once, and five quick presses of Enter send one message. (#39)

Updating

A Linux server updates from Settings, or with vyre update. The stable channel takes this release. Your data, vault and sign-ins stay as they are.

Vyre 0.2.1

Vyre 0.2.1 fixes Claude sign-in on a new server and lets the phone app be added to your home screen.

Fixed

• Signing in to Claude from Vyre now accepts the code you paste from the Claude page, including the form that ends in a # and more text. Before, that paste was rejected.
• The phone app at app.vyre.run now has a web app manifest, icons and iPhone tags, so Add to Home Screen installs it as an app.

Updating

A Linux server updates from Settings, or with vyre update. The stable channel takes this release. Your data, vault and sign-ins stay as they are.

Vyre 0.2.0

Vyre 0.2.0 puts your assistant on a server you own, with Lumen on your Mac and an app on your phone, and sets it up from a web page.

Set up from vyre.run/setup

• Open vyre.run/setup, say where Vyre will live (a Linux server, or a Mac that stays on), and run the one command the page shows. The page follows the install as it runs and shows the real error if something fails.
• Setup walks you through signing in to Claude, joining Tailscale, and choosing your address: a name such as alex.vyre.run, or your own domain after you add two DNS records. Tailscale is required. When setup finishes you land at your address and the setup page is done.
• The first passkey is made in the browser that started setup, and that browser becomes your first trusted device.
• A phone pairs by QR code. A Windows PC pairs by QR code or by typing a short list of words.
• Servers run on Linux, in Docker, and on a Mac that stays on. A Windows PC is a device, with an app (a tray icon and an Alt+Space panel). A server on Windows runs inside WSL2.

Lumen, the phone and your own server

• Lumen is the command bar on your Mac, renamed from Capsule. Vyre Lumen is its name on the Mac.
• The phone app installs to your home screen from your server's address. The Deck, Chat, Find, approvals and push notifications work there. iPhone and Android app projects are in the source, with steps in apps/RELEASE.md.
• Your sessions, agents, watchers, memory and vault run on your server around the clock. Your devices reach it over your private Tailscale network.
• You can message a session that runs on your Mac, and answer its questions, from the Deck on your server.

Sessions on your own subscriptions

• Sessions run on Claude (through the Claude Agent SDK), on Codex and Grok (through the Agent Client Protocol), and on OpenRouter, using your own accounts and keys.
• One picker in Chat sets the session's provider, account, model and effort. Type @codex or @grok at the start of a message to run that one turn on that account while the session stays where it is.
• Every reply carries the logo of the provider that wrote it. When you switch a session, Chat says "Switched to Codex" and the new model gets the session's memory and files.
• You sign in a Codex or Grok account by asking your assistant to start the sign-in.
• Spend is capped per provider per day. At the cap the session that was spending pauses and tells you how to raise it. vyre spend shows today's figures, and Settings has the same under Spend.

Generated images and video

• Images and video that Codex and Grok make are saved to the project as artifacts, with the model and the prompt that made them. They also appear in a Generated folder in each project's Drive. "Use in" on a media card fills the composer to hand the file to another model for one turn.
• Grok can make video only when the account's privacy switch is off. Vyre shows that choice on the account.

Artifacts

• Documents, reports, dashboards, diagrams, decks, images, video and audio run no script. A page or an app runs its own code in a locked frame and says so: "Runs its own code and can reach the internet". A page can send the browser to another address by itself, so do not let an agent put in one anything you would not send to the internet.
• In Safari, a page that sends itself to your own Vyre address also sends your Vyre session cookie. Its tools cannot be called that way. The fix is in a later release; see Not in this release.

Vyre for Chrome

• Vyre for Chrome lets Claude read a page, fill forms and click in Chrome, Brave, Edge, Chromium, Arc and Dia on your Mac. You load it in chrome://extensions with Developer mode on.
• Anything that sends, posts, pays or deletes is held until you approve it. Passwords, cookies and tokens are masked, and banks, password managers and sign-in pages are never read.
• A script Claude runs in a page can read with your login but not write with it, and Vyre blocks what it can see the script send to a site the page does not already use. It cannot hold a script that builds code from text or starts a worker some other way. The docs say plainly what the guard does not cover.
• It remembers how each site is laid out, never what you typed. This is on by default, and you can see, forget or turn it off.

Agent computers and watchers

• Only you can resume a paused agent computer, and each agent is held to its own computer.
• A watcher belongs to one project. A session or agent sees only its own project's watchers.
• Teammates are named roles in a project, and a teammate can have standing duties. A duty that a model proposed stays off until you turn it on.

GitHub, the vault and memory

• Connect a GitHub account and the commits a session makes carry your name and email, plus a Vyre-Session line saying which session wrote them. You can leave that line out in config.
• The vault releases a value only after Touch ID on your Mac, a passkey in the Deck, or Face ID or a fingerprint on a paired phone. Pairing a device and approving a send, a post or a payment ask the same way.
• Memory keeps facts you can trace to the turn they came from. Recall searches every turn of your Claude Code sessions.

Updates

• Updates are signed. The list of checksums carries an Ed25519 signature from Vyre's release key, and the server images are checked with cosign before anything is changed.
• The stable channel ignores prereleases. Only a server set to the beta channel takes one.
• A Linux server updates from Settings, or with vyre update.

Not in this release

Terminal Touch ID asks, the Safari cookie fix, Chrome routing through a site's own API and working in several tabs, giving one message to two models, per-provider blocks in Chat, Spaces, memory rollover and putting idle sessions to sleep are coming next, not in 0.2.0. Known gaps says what to do today for each.

Vyre 0.2.0-rc.2

This is the second practice prerelease of Vyre 0.2.0. It exists to run the real release pipeline once, end to end, before the real release: the images, the signatures and the update path. (The first one stopped before publishing.)

Do not install it on a server you care about. The stable channel ignores it. Only a box set to the beta channel would take it, and the notes for 0.2.0 will replace this release.

Vyre 0.2.0-rc.1

This is a practice prerelease of Vyre 0.2.0. It exists to run the real release pipeline once, end to end, before the real release: the images, the signatures and the update path.

Do not install it on a server you care about. The stable channel ignores it. Only a box set to the beta channel would take it, and the notes for 0.2.0 will replace this release.

Android android-0.1.0-f6d5af1

The Vyre Android app, UNSIGNED: your box signs it with your own key. android.json has the sha256 of this file.

Vyre 0.1.1

Vyre 0.1.1 is the first stable release of Vyre. Install it on a server with the box installer from vyre.run, or build from this tag. It is not on npm yet.

Already running 0.1.0-rc.1 or later? Run vyre update on your server.

What's new:

• Wink: add your phone by scanning. Settings and onboarding show a ring around your avatar. Point
  the phone at it, check the name and fingerprint it shows, and tap Pair. The ring appears only
  when you tap for it, lasts a few minutes, and disappears once used. The relay only ever holds
  a sealed record.
• Linux and Windows desktops you pair join your tailnet on their own, after a one-time Tailscale
  setup on your server. Macs follow in 0.1.2.
• GitHub: sign in with a short code (no token to paste), start a project from one of your repos,
  or add a repo to an existing project. Each session in a GitHub project gets its own worktree
  and branch. Vyre never deletes a worktree that holds unpushed or uncommitted work. It tells you
  what's at stake instead.
• Avatars for you, your assistant, teammates and projects, in the Deck, on the phone and in the
  Capsule. A chat that isn't in a project yet shows a draft tile, which carries over when you
  make it into a project.
• vyre vitals shows CPU, memory, disk, network and battery, with a per-agent breakdown for
  your computers.
• Sessions from a paired device come to your box only after you turn that device's import on.
  vyre call sync.scan shows what would be sent first.
• The Capsule starts Vyre itself when it's offline, knows the project you're working in, and
  shows your past sessions as hints.
• Teammates: vyre team lists a project's teammates, and vyre team ask gives one a task.

Security:

• The Capsule's presence key now lives in the Mac's Secure Enclave (P-256), with Touch ID on every
  use. After updating, re-enroll the Capsule's key. The old key kind is refused.
• The Capsule pins its own signed build with the box. An ad hoc or unsigned build is refused.
• An agent only reaches the projects it's mapped to, and a module can't claim another module's
  name.
• A Mac can only unpair itself. Only you can unpair any other device.

Known issue:

• In a chat that isn't in a project, "New project from a GitHub repo" says not found for a session that exists only in search history. Starting the project from the repo on the Projects page works. The fix is planned for 0.1.2.

The full engineering notes for this release are in CHANGELOG.md and in release.json.

Vyre 0.1.0-rc.2

Second release candidate for Vyre 0.1.0. This is a pre-release. It is not on npm.

Install on a server with the box installer from vyre.run, or build from this tag.

Security

• Tools that only a person may call are now derived from each module's manifest, and anything a manifest leaves unnamed is refused by default.
• A label taken from a model's shell counts as the model's label, never a person's. There is one list of surfaces, and an agent is named only as mcp:agent or harness:agent.
• vyred's own git calls never run a folder's hooks, filters or config commands.
• The docker-api service needs a bearer that only vyred can read.
• A paired Mac can unpair itself from the server again, and only itself. The Mac now reports an error when the server refuses instead of reporting success.

Vault and mail

• Connecting a key goes through needs.credentials, vault.need and vault.connect, and every account and key is granted per surface.
• Mail can send from any connected account. Every send waits at the Gate for the person.
• Import covers LastPass, Dashlane, Keeper, NordPass, Proton Pass, Enpass, KeePass, Firefox, Apple Passwords and project .env files. Duplicates are found by content, and you see a preview first.
• New: an authenticator, SSH keys with git signing, emergency access, card and address autofill, and passkeys in the browser extension.
• Autofill works on iOS, macOS and Android.

Server and install

• A container replaced by an update no longer finds its own old lock held, and vyre inside the container waits for vyred.
• The package includes packages/module-sdk, so it starts. rc.1 did not. Mac build outputs and gitignored files are left out.
• install-box.sh passes shellcheck and prints a short line while it waits for Docker.
• Capsule questions go through Vyre IQ (memory.ask).

Known gaps

• Adding a mail account from a server terminal that cannot prove presence is refused, as the new person-only rules intend. Add accounts from the Deck or the Capsule.

Full list: CHANGELOG.md at this tag.

Thanks to irfad7.

Android android-0.1.0-ebcb0b0

The Vyre Android app, UNSIGNED: your box signs it with your own key. android.json has the sha256 of this file.

Android android-0.1.0-4469b15

The Vyre Android app, UNSIGNED: your box signs it with your own key. android.json has the sha256 of this file.