OpenTeam v0.0.5

This release puts OpenTeam in the iPhone share sheet, has a Bot's new reply already in place when you open its chat, and shows chat previews as plain text. It also lets an administrator turn on text replies for iMessage (SSH).

Before you update

• Nothing to prepare. There are no database changes, and the server and apps can be updated in any order. The 0.0.5 desktop and iPhone apps work with a 0.0.4 server.
• iMessage (SSH) moves to 1.3.2 when the server starts. If its bridge runs on the server host, openteam update refreshes the bridge too. Connections stay read-only. Sending only turns on when an administrator enables it (see below).
• Coming from 0.0.2 or earlier? Read the 0.0.3 notes first. Their plugin, iMessage (SSH) and Google steps still apply.

New

• Share to Bots from any iPhone app. Choose OpenTeam in the share sheet to send a link, text, photos, videos or files (up to six) to one or more Bots or group chats without leaving the app you're in.
  • Bots and groups are listed most recently active first. You can search them and pick more than one.
  • A shared link or snippet fills the message, which you can edit before sending. Photos, videos and documents become attachments.
  • Bots you message also appear in the share sheet's suggestion row, next to your Messages contacts.
  • Attachments follow the server's limits (25 MB, or 200 MB for videos). Sharing needs a connection; the sheet shows an error while you're offline.
• iMessage (SSH) can send text replies (opt-in). An administrator can let Bots reply to existing Messages conversations, including Apple Business Messages chats, over the same SSH connection. The Mac doesn't need the OpenTeam desktop app.
  • To turn it on, run bridge.py --enable-send for that Mac on the server host, restart the bridge, and reconnect the plugin. The setup guide has the exact commands. This adds a separate, restricted sending key; existing read-only keys keep their restrictions.
  • Once enabled, Bots can check whether macOS allows them to control Messages without sending anything.
  • Only text replies to existing conversations are supported. Bots can't start new conversations or send attachments or reactions.

Improvements

• New replies are already there when you open a chat (desktop and iPhone). Opening a chat from a notification or the chat list used to show the old messages first, then animate the reply in.
  • Desktop: chats with new replies are read in the background as the replies land, along with up to three unread chats you haven't opened yet.
  • iPhone: chats are read during live sync and when a notification arrives. After you tap a notification, the chat waits briefly for the reply instead of opening without it.
• Faster chat switching. On desktop, returning to a chat you've opened before no longer shows a blank pane for a moment. On iPhone, a saved chat opens as soon as it's laid out instead of after a fixed delay.
• Chat previews read as plain text (desktop sidebar and iPhone chat list). Previews show the first line of the latest message as a reader sees it, without Markdown link syntax, bold markers, headings, list markers, table pipes or HTML tags. Attachment-only messages read like "Sent 1 image" or "Sent 3 files · 2 images, 1 PDF". On desktop, the hover card shows the same text.
• "Working in the background" animates on its own (desktop). The caption under a reply now shimmers for as long as the background task runs, instead of only while you hover over it. With Reduce motion turned on in macOS, it stays still.

Fixes

• iPhone: links in messages you send are readable again. They were invisible on the black bubble in light mode and on the blue accent bubble. Now they use the bubble's text color and are underlined.

Install or update

• Server: run openteam update on the server host. It backs up the database first and rolls back if the new version doesn't start. To install fresh, see Installation.
• Desktop: update from Settings → Updates, or download OpenTeam-0.0.5-mac-arm64.dmg (macOS, Apple silicon) or OpenTeam-0.0.5-linux-x86_64.AppImage (Linux x64) below. Windows and Intel Mac builds aren't available yet.
• iPhone: update in TestFlight. Build 0.0.5 (51) adds the share sheet, plain-text previews, readable links, and replies that are there when you open a chat. It reaches public testers once Apple's beta review finishes.
• 0.0.4 desktop and iPhone apps still work with a 0.0.5 server.

The CLI binaries, Compose file, and AppImage come with Sigstore signatures (.sigstore.json), and their checksums are in SHA256SUMS and DESKTOP_SHA256SUMS. The macOS app is signed and notarized by Apple.

Full changelog: v0.0.4...v0.0.5

OpenTeam v0.0.4

This release keeps chats in order and following new replies on desktop and iPhone, makes switching chats faster on desktop, and lets bots enter the sign-in and two-factor codes they can already reach. It also stops the desktop app from signing you out while the server restarts.

Before you update

• Nothing to prepare. There are no database or plugin changes, and the server and apps can be updated in any order. The 0.0.4 desktop and iPhone apps work with a 0.0.3 server. Chats load less data once the server is on 0.0.4.
• Coming from 0.0.2 or earlier? Read the 0.0.3 notes first. Their plugin, iMessage (SSH) and Google steps still apply.

New

• Bots can enter the codes they can reach. When a task hits a sign-in or two-factor step, a bot can now look up the password or current code in your connected sources, such as 1Password, email, iMessage or SMS, and type it into that site's sign-in. Before, the browser worker refused to type a code it had found, for example on DocuSign, and the bot asked you to enter it instead. Bots still ask you when the value isn't available to them.

Improvements

• Messages stay in order (desktop and iPhone). Coming back to a chat, returning to the iPhone app, reconnecting, or a bot sending several messages at once could show the newest message first and insert the earlier ones above it a moment later. Messages now appear together, in order.
• Chats keep following new replies.
  • Desktop: scrolling up a few pixels no longer stops the chat from following, so the next reply no longer lands behind the composer with no sign of it. Replies that arrive near the end glide into view.
  • iPhone: replies keep coming into view when you're near the end, and swiping down to dismiss the keyboard returns to the latest message. The latest-messages button shows how many replies arrived below.
• Faster chat switching on desktop. Chat history shows as soon as it arrives, eight recent chats stay loaded instead of three, and a chat no longer jumps after it opens. Chats with diagrams don't redraw them on every visit.
• Smoother chats.
  • Messages that arrive while a chat or the desktop window is hidden appear without replaying their entrance animation.
  • A sent image keeps its preview while it uploads.
  • Answering a question card closes it smoothly instead of shifting the chat.
  • On iPhone, chats with tables and diagrams open faster the first time.

Fixes

• Desktop: the app no longer signs you out when the server briefly returns an error, for example while it restarts for an update behind a proxy. Only a rejected session signs you out.
• Desktop: a bot message whose only formatting is a table now shows as a table instead of raw | text, and code and diagram messages no longer flash raw Markdown before they render.

Install or update

• Server: run openteam update on the server host. It backs up the database first and rolls back if the new version doesn't start. To install fresh, see Installation.
• Desktop: update from Settings → Updates, or download OpenTeam-0.0.4-mac-arm64.dmg (macOS, Apple silicon) or OpenTeam-0.0.4-linux-x86_64.AppImage (Linux x64) below. Windows and Intel Mac builds aren't available yet.
• iPhone: update in TestFlight. Build 0.0.4 (50) keeps chats in order and following new replies. It reaches public testers once Apple's beta review finishes.
• 0.0.3 desktop and iPhone apps still work with a 0.0.4 server.

The CLI binaries, Compose file, and AppImage come with Sigstore signatures (.sigstore.json), and their checksums are in SHA256SUMS and DESKTOP_SHA256SUMS. The macOS app is signed and notarized by Apple.

Full changelog: v0.0.3...v0.0.4

OpenTeam v0.0.3

This release gives bots their own email inboxes, sends Gmail from reviewed draft cards, and adds Google Docs, Sheets and Slides. Bots also get better at slide decks and other office files, and the plugins that ship with OpenTeam now update with it.

Before you update

• Update the server before the desktop app. The new draft card's approval menu and Gmail sending need a 0.0.3 server.
• Plugins update with the server. When the 0.0.3 server starts, the plugins that ship with OpenTeam (Gmail, Google Calendar, Google Drive, Slack, Slack (stealth), GitHub, Linear and iMessage (SSH)) move to their new versions, and their connected accounts reconnect in the background. No account needs to sign in again. Granola, Notion and plugins you uploaded yourself still update through Apply reviewed update.
• iMessage (SSH): if its bridge is installed on the server host, openteam update refreshes the bridge too, and the first message lookup upgrades the reader on your Mac. If the refresh fails, the update still completes, the plugin keeps using the old bridge, and its Activity says why. Run openteam update --force on the server host to retry.
• Coming from 0.0.1 or 0.0.0? Read the 0.0.2 notes first.

New

• Email inboxes for bots. The new Email plugin connects a mailbox you already have, such as a Gmail, Google Workspace, iCloud or Fastmail address, with an app password. OpenTeam finds the mail servers from the address, including custom domains. Bots can search and read conversations and attachments, and reading never marks mail as read. Ask a bot for a routine to have it act when mail arrives, for example "when my accountant emails, read it and reply in the same thread." By default, only mail whose sender passes DMARC starts a routine. Outlook.com and Microsoft 365 can't be used because Microsoft only allows OAuth sign-in for mail apps. See Email.
• Reviewed email, including Gmail. When a bot writes an email, it shows up in the chat as a draft card titled New email or Reply, with From, To, Cc, Subject and the message. Edit it, then choose Send or Discard. Replies stay in their thread. Gmail drafts can now be sent this way: the From menu lists your verified Send mail as addresses, and your Gmail signature is added. Bots still can't send email any other way.
  • The card's approval menu sets how that bot's later drafts are handled. Always allow lets it email those recipients without asking, Needs approval takes that back, and Disable drafts for Bot sends all of its emails and Slack messages without review. Bot settings show the Review drafts switch and the allowed recipients, each with Remove. Bots can't change these settings themselves.
  • When you ask a bot to "draft" something, or say you want to review it first, the card waits for you even when the recipient is allowed.
• Google Docs, Sheets and Slides. Three new plugins let bots edit files that already exist, not just create new ones. Docs can insert, replace and style text, lists, tables and images. Sheets can write and append values, format cells, and add charts, filters and validation, so a bot can keep a spreadsheet up to date over time. Slides can build and arrange slides and render them as images to check how they look. Enable the Docs, Sheets or Slides API in the Google Cloud project you use for the other Google plugins, then add the plugin in Marketplace. See Google.
• Slide decks and office files. Bots hand decks, spreadsheets and documents to a new office worker. For a deck, the bot asks where it's going (Google Slides, PowerPoint or another app), outlines it, and offers two designs to choose from. It then builds the deck and checks each slide's rendered image before sending it back. A finished .pptx, .docx or .xlsx can be uploaded to Google Drive as a native Google Slides, Docs or Sheets file.

Improvements

• Google Drive can now move, rename, share, export and trash files, and read, add and reply to comments. Bots can export Google files as PDF and other formats.
• Google Calendar can use your calendar's default reminders and set Google Workspace working locations, down to the building, floor and desk. Unless you name other dates, event lists cover the next seven days in your time zone.
• iMessage (SSH) now has the same read tools as the desktop Messages integration. Bots can see what just arrived across every chat, search your whole history (including messages that plain-text search used to miss), look up names from your Mac's Contacts, and open attachments. HEIC photos are converted to JPEG.
• Bots read the skills that come with plugins, such as the Google and Slack skills, when a task needs them, and pass them along to the background workers that do the work.
• Bots can see what your other bots have been up to: when you last talked, their open to-dos, and questions still waiting on you.
• Desktop: while a background task is still working after a bot's reply, the chat shows Working in the background until the task finishes.
• Desktop and iPhone: sending a message or choosing Latest glides to the newest message instead of jumping, and new replies no longer end up under the composer. With Reduce Motion on, it still jumps.

Fixes

• Images returned by plugin tools, such as slide previews, now reach the bot as images. Before, they arrived as text the bot couldn't see, and large ones were cut off.
• Connect now saves the values you entered before connecting, so iMessage (SSH) and Slack (stealth) can be connected from their setup screens on desktop and iPhone. Before, it failed with "… is required".
• Desktop: on a message with an image and text, the react, reply and more buttons now sit next to the text instead of far to one side.

Install or update

• Server: run openteam update on the server host. It backs up the database first and rolls back if the new version doesn't start. To install fresh, see Installation.
• Desktop: update from Settings → Updates, or download OpenTeam-0.0.3-mac-arm64.dmg (macOS, Apple silicon) or OpenTeam-0.0.3-linux-x86_64.AppImage (Linux x64) below. Windows and Intel Mac builds aren't available yet.
• iPhone: update in TestFlight. Build 0.0.3 (49) has the new draft card, smoother scrolling and the setup fix. It reaches public testers once Apple's beta review finishes.
• 0.0.2 desktop and iPhone apps still work with a 0.0.3 server, but without the new draft card and its approval menu.

The CLI binaries, Compose file, and AppImage come with Sigstore signatures (.sigstore.json), and their checksums are in SHA256SUMS and DESKTOP_SHA256SUMS. The macOS app is signed and notarized by Apple.

Full changelog: v0.0.2...v0.0.3

OpenTeam v0.0.2

This release keeps Gmail, Google Calendar, and other accounts working through updates, stops your iPhone and Mac from showing the same alerts, and adds managed Tailscale HTTPS. It also fixes expired Google sign-ins and invisible tables in desktop chat.

Before you update

• Your iPhone stays quiet while you're using your Mac. This is on by default once the server and the Mac app are both on 0.0.2. iPhone alerts resume after five minutes without activity on the Mac, or when the Mac locks, sleeps, or quits OpenTeam. To get alerts on both devices as before, turn off Pause alerts on other devices while I'm active in Settings → General → Notifications. Alerts paused this way aren't sent later, but their messages stay unread.
• If you've turned off OpenTeam notifications in macOS System Settings, turn this setting off too. The Mac app can't always tell that macOS is hiding its alerts, so your iPhone could stay quiet while you use the Mac.
• Update the server before the desktop app. The new notification setting and the Tailscale HTTPS controls need a 0.0.2 server.
• Coming from 0.0.0? Read the 0.0.1 notes first. Their 1Password and macOS install steps still apply.

New

• Fewer duplicate alerts. While you're using your Mac, OpenTeam doesn't also alert your iPhone. When OpenTeam is open on your iPhone, the iPhone takes priority and the Mac stays quiet. One setting controls this for both devices, and you can change it in either app. The iPhone side needs TestFlight build 0.0.2 (47).
• Tailscale HTTPS. openteam setup now offers Tailscale HTTPS as its own connection choice, and you can pick the HTTPS port. After setup, run openteam tailscale enable [--https-port <port>], openteam tailscale status, or openteam tailscale disable on the server host. When the desktop app runs on the server host, it has the same controls in Settings → Server → Remote access. For a remote server, it shows the commands to run there. OpenTeam checks that HTTPS works before switching and restores your previous settings if it doesn't. It removes only the Serve routes it created and never turns on Funnel. See Tailscale HTTPS.
  • If setup already configured Tailscale HTTPS for you in 0.0.0 or 0.0.1, it keeps working as Use my existing HTTPS setup. To manage it with the new commands, run openteam tailscale enable. It reuses your current address and port.

Improvements

• openteam setup always shows the Connection step, so you no longer need --advanced to change how your apps connect. --advanced still adds the server, model, and performance settings.
• New installs no longer start with GPT-5.6 Sol selected. After you connect a provider, its first available model is selected for you to save. Existing model choices don't change.
• When an account a bot needs isn't available, the bot now gets the reason, for example "MCP process exited. Reconnect to try again." It can tell you which account to reconnect.

Fixes

• Accounts keep working after an update or restart. Gmail, Google Calendar, Google Drive, iMessage (SSH), and custom local connectors used to show an error after every update until you clicked Reconnect on each one. They now start again the next time a bot uses them. Accounts that broke this way before you updated recover on their own. A connector that crashed, or one that was waiting for you to sign in when the restart happened, still needs Reconnect.
• Expired Google sign-ins. When Google rejects a saved sign-in for Gmail, Google Calendar, or Google Drive, the account now shows Sign-in needed instead of Connected. Sign in opens Google sign-in instead of retrying the rejected credentials. This also fixes accounts already stuck with a connection error. In the 0.0.1 desktop app, use Reauthorize in the account's settings for those. The sign-in setup steps for these accounts now explain that Google ends sign-ins after seven days while your Google Cloud app's publishing status is Testing.
• Gmail attachments. Bots can now save files attached to your emails, such as a PDF quote, and read them. Before, every attachment download through the Gmail connection failed with "Attachment does not belong to this message", so bots fell back to opening Gmail in the browser, which needs a separate Google sign-in.
• Files for background work. When a bot hands a task to a background helper, the helper can now download files from your connected Gmail and Google Drive accounts itself. Before, only the main bot could, so a helper reviewing an email couldn't open its attachment. Helpers still can't upload files to your accounts.
• Desktop: markdown tables in bot replies were invisible. They now show with their column alignment, and wide tables scroll sideways. Single line breaks in replies are kept, as they are on iPhone.
• iOS: tables no longer split words and amounts across lines. They keep their column alignment and scroll sideways when they don't fit. This is in TestFlight build 0.0.2 (47).

Install or update

• Server: run openteam update on the server host. It backs up the database first and rolls back if the new version doesn't start. To install fresh, see Installation.
• Already running 0.0.2? Builds published before this one don't include the Gmail attachment and background-helper download fixes. Run openteam update --force on the server host to get them. The desktop and iPhone apps are unchanged.
• Desktop: update from Settings → Updates, or download OpenTeam-0.0.2-mac-arm64.dmg (macOS, Apple silicon) or OpenTeam-0.0.2-linux-x86_64.AppImage (Linux x64) below. Windows and Intel Mac builds aren't available yet.
• iPhone: update in TestFlight. Build 0.0.2 (47) reaches public testers once Apple's beta review finishes.
• 0.0.1 desktop and iOS apps still work with a 0.0.2 server, but they don't pause alerts on other devices.

The CLI binaries, Compose file, and AppImage come with Sigstore signatures (.sigstore.json), and their checksums are in SHA256SUMS and DESKTOP_SHA256SUMS. The macOS app is signed and notarized by Apple.

Full changelog: v0.0.1...v0.0.2

OpenTeam v0.0.1

This release replaces 1Password autofill with a 1Password plugin, adds read-only iMessage access, and fixes plugin sign-ins and updates that could get stuck.

Before you update

• Set up 1Password again. The 1Password token saved in 0.0.0 is deleted when the server updates and isn't carried over. To keep using it, add the 1Password plugin from Marketplace and paste a service account token. See 1Password setup.
• macOS desktop: quit the app to install this update. In 0.0.0, Restart to install hides the window and doesn't install. Once the update downloads, quit OpenTeam (⌘Q) and open it again. Later updates install normally.
• Updating a remote server from the 0.0.0 desktop app fails with openteam: command not found if openteam isn't on the server's non-interactive PATH. If that happens, run openteam update on the server.

New

• 1Password plugin. Bots can sign in to websites with logins and one-time codes from a vault shared with a 1Password service account. Browser and computer workers can use it too, so they can complete sign-in pages themselves. It replaces saved-login autofill, which checked 1Password often enough to use up a service account's daily request limit.
• iMessage (SSH) plugin. Bots can find, read, and search iMessage and SMS history on a Mac over SSH. It's read-only: it can't send messages, download attachments, or show contact names. Your server administrator must set it up once on the server host first, using packages/plugins/imessage-ssh/connector/install-host.py (Linux with Docker and systemd). The installer doesn't do this step yet.

Improvements

• When a bot needs you to connect an account, it now sends you a link to sign in from OpenTeam.
• Pending plugin sign-ins have a Start again button. You can now cancel sign-ins that got stuck in 0.0.0.
• Update errors now show the full message right away. Failed updates point you to update.log.
• If Docker runs out of network address pools, openteam setup, start, and update now explain how to fix it.
• Desktop: you can drag the window from anywhere on the chat header. Scrolling over the header no longer scrolls the conversation.
• Desktop: the full-window computer view shows a larger screen with less empty space above it.
• Marketplace: removed eight category filters that had no plugins in them.
• iOS: chat history scrolls smoothly without jumping, including when you open a chat from a notification. This is in TestFlight build 0.0.1 (46).

Fixes

• macOS: Restart to install now quits, installs the update, and reopens the app. This applies to updates after 0.0.1.
• Desktop: server updates over SSH work when openteam is installed in ~/.local/bin but isn't on the non-interactive PATH.
• Desktop: copies built from source no longer fail to check for updates with ENOENT … app-update.yml. They link to the latest download instead.

For plugin developers

• A plugin setup field can set environment to give its secret to every bot's processes as an environment variable.
• A plugin skill can list agents so subagents get it too, such as the browser and computer workers. Skills without agents still go only to the main agent. See the plugin reference.

Install or update

• Server: run openteam update on the server host. It backs up the database first and rolls back if the new version doesn't start. To install fresh, see Installation.
• Desktop: update from Settings → Updates, or download OpenTeam-0.0.1-mac-arm64.dmg (macOS, Apple silicon) or OpenTeam-0.0.1-linux-x86_64.AppImage (Linux x64) below. Windows and Intel Mac builds aren't available yet.
• 0.0.0 desktop and iOS apps still work with a 0.0.1 server. The desktop app will suggest updating.

The CLI binaries, Compose file, and AppImage come with Sigstore signatures (.sigstore.json), and their checksums are in SHA256SUMS and DESKTOP_SHA256SUMS. The macOS app is signed and notarized by Apple.

Full changelog: v0.0.0...v0.0.1

OpenTeam v0.0.0

OpenTeam v0.0.0 rebuilt from 814544b23b787aff6ded528eeeb9550f97f66512 on main.

Includes the committed local desktop inspector edits, ignores launch artifacts, and prepares native iOS 0.0.0 build 45 for TestFlight. Slack (managed) preserves the existing app-authorized connection; Slack (stealth) provides app-free browser-session authentication with nine tools and precompiled Linux executables.

Includes four runtime images for Linux x64 and ARM64, pinned by digest; five signed CLI binaries; a signed Linux AppImage; and a Developer ID signed and notarized macOS installer. The macOS and Linux desktop downloads are rebuilt from the same commit. Windows desktop packaging is not included.