Skip to content

Releases

v0.1.0-beta.16

Choose a tag to compare

@github-actions github-actions released this 17 Nov 10:36

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

Fixed

  • On macOS, opening a Session, starting its terminals, and deleting or renaming a Session no longer fail now and then. When Orchbee let go of a file lock just as it started another program, the next step could find the lock still taken: a Session was reported as in use, its terminals did not start, or a delete or rename was refused, though nothing else was using it. Orchbee now releases every lock before it closes the file. Windows was not affected.
  • A terminal font that isn't installed falls back to a monospace font. In the window, when the font typed in Settings is missing, terminals and the preview use a monospace font instead of the system's default text font.

Known limits

  • Windows x64, and macOS 13 or later on Apple silicon and Intel. Linux follows.
  • On macOS, Orchbee is not notarized by Apple yet. The first time you open a copy downloaded in a browser, macOS says it cannot check Orchbee for malicious software. Click Done, open System Settings › Privacy & Security, click Open Anyway next to Orchbee, confirm with your password or Touch ID, and click Open. Installing from a terminal with curl -fsSL https://orchbee.com/install.sh | sh skips this.
  • On macOS, a copy installed only by dragging it from the disk image does not update itself yet, and About says updates are not available for this installation. A copy installed with the terminal command updates itself. A fix for disk-image installs is on the way.
  • On macOS, remembered SSH passwords ask again for Keychain access after each update, until Orchbee is signed.
  • On macOS, when only the Session's server process crashes while terminals run, Orchbee refuses to open that Session again ("recovery-required") until its terminal process ends. Quit orchbee-terminal-host in Activity Monitor, which ends those terminals, or log out; the next start works.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.

v0.1.0-beta.15

Choose a tag to compare

@github-actions github-actions released this 17 Nov 08:31

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

New

  • Terminals keep running when the process that serves them crashes. Orchbee starts a new one that takes over your running terminals and Agents, usually within a second or two. Meanwhile each terminal shows Reconnecting and ignores typing, then carries on where it was. Orchbee tries this at most three times in ten minutes; after that, terminals show Can't reconnect, and the window offers Quit All.
  • Settings has an About page with the version and Check for updates, in the window and in the terminal interface.
  • orchbee status says whether your terminals are Ready, Reconnecting or Can't reconnect. orchbee server stop and orchbee session stop say how many terminals they will end before they ask you to confirm.

Fixed

  • The terminal interface keeps its connection through more faults. When it could not confirm whether a layout change ran, or briefly lost its view of the focused terminal, it ended its whole connection. Now it settles that one change or terminal and carries on.
  • A terminal that cannot use its updates stops alone. In the window and the terminal interface, it is redrawn from a fresh copy; after three failures in a row only that terminal stops, and it reads Disconnected. Before, the window reopened it without end and the terminal interface dropped its connection.
  • A window that keeps crashing no longer reloads in a loop. It reloads once; after a second crash within a minute, Orchbee asks whether to reopen or close it.
  • The process that serves your terminals no longer stops on a request it cannot read, such as one from a newer version. It refuses that request and carries on.
  • A custom command run from a Panel whose program has exited now says so, instead of "Command was refused or failed."

Known limits

  • Windows x64, and macOS 13 or later on Apple silicon and Intel. Linux follows.
  • On macOS, Orchbee is not notarized by Apple yet. The first time you open a copy downloaded in a browser, macOS says it cannot check Orchbee for malicious software. Click Done, open System Settings › Privacy & Security, click Open Anyway next to Orchbee, confirm with your password or Touch ID, and click Open. Installing from a terminal with curl -fsSL https://orchbee.com/install.sh | sh skips this.
  • On macOS, a copy installed only by dragging it from the disk image does not update itself yet, and About says updates are not available for this installation. A copy installed with the terminal command updates itself. A fix for disk-image installs is on the way.
  • On macOS, remembered SSH passwords ask again for Keychain access after each update, until Orchbee is signed.
  • On macOS, when only the Session's server process crashes while terminals run, Orchbee refuses to open that Session again ("recovery-required") until its terminal process ends. Quit orchbee-terminal-host in Activity Monitor, which ends those terminals, or log out; the next start works.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.

v0.1.0-beta.14

Choose a tag to compare

@github-actions github-actions released this 17 Nov 04:23

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

macOS

This is the first release for macOS 13 or later, on Apple silicon and Intel. Intel Macs are tested in CI only.

Install from a terminal. The second command also installs the desktop app, into /Applications when you can write to it, otherwise into ~/Applications:

curl -fsSL https://orchbee.com/install.sh | sh
curl -fsSL https://orchbee.com/install.sh | sh -s -- --desktop

The command is linked at ~/.local/bin/orchbee. When your PATH lacks that folder, as zsh's does on a new Mac, the installer prints this line. Add it to ~/.zshrc and open a new terminal:

export PATH="$HOME/.local/bin:$PATH"

Or download Orchbee-0.1.0-beta.14-macos-aarch64.dmg (Apple silicon) or Orchbee-0.1.0-beta.14-macos-x86_64.dmg (Intel) above, open it and drag Orchbee to Applications. Terminals inside Orchbee find orchbee; for other terminals, run the first command above.

Orchbee is not notarized by Apple yet. The first time you open a copy downloaded in a browser, macOS says it cannot check Orchbee for malicious software. Click Done, open System Settings › Privacy & Security, click Open Anyway next to Orchbee, confirm with your password or Touch ID, and click Open. The terminal install skips this.

Known limits on macOS:

  • Remembered SSH passwords: macOS asks again for Keychain access after each update, until Orchbee is signed.
  • Images in terminals show in terminals that speak the Kitty graphics protocol, such as Ghostty and kitty; iTerm2 and Terminal.app show a coarser cell picture.
  • When only the Session's server process crashes while terminals run, Orchbee refuses to open that Session again ("recovery-required") until its terminal process ends. Quit orchbee-terminal-host in Activity Monitor, which ends those terminals, or log out; the next start works.
  • A Claude Code conversation resumes after a restart only with the Orchbee integration turned on.

New

  • Orchbee updates itself. A minute after it starts, and then every hour, it looks for a new version and installs it in the background. When it is ready, Update appears to the right of Settings, in the window and in the terminal interface. One click moves the window and the terminal interface to the new version at once, while your terminals and Agents keep running. The background Session moves to the new version by itself once no terminal is running. If a new version fails to start, Orchbee goes back to the one before. Turn it off with Automatic updates in Settings. This is the first version that updates itself: coming from an older one, run orchbee update once.
  • Settings is a large dialog over your workspace, in the window and in the terminal interface alike. Its gear sits at the sidebar's bottom-left. Changed settings are marked after their titles. The question-mark Shortcuts button is gone: its key, Search and Settings › Keyboard still open the list of shortcuts.
  • Pick the terminal font from the fonts installed on your computer, and step its size up and down. The terminal text and the terminal theme preview as you change them.

Fixed

  • A bad message is contained. On a single message it could not use, the process that serves your terminals could stop and take every terminal with it. It now refuses only that message, request or terminal, and keeps serving the rest.
  • One fault no longer takes down the window or the terminal interface. An error in one message, request or view now stays with its own terminal or view, and the window's main process keeps running. When the terminal process refuses one input or resize, the window and the terminal interface keep control of the terminal and tell you.
  • An action whose outcome is unknown no longer drops the connection. When Orchbee could not confirm whether one action ran, the window ended its whole connection. Now that one action is reported as unknown, and everything else carries on.
  • On Windows, a custom command's Panel is titled with its program, as on macOS, instead of "Windows PowerShell".
  • A Session whose terminal process was lost can be stopped on Windows. When the process that serves your terminals had exited, the Session could not be stopped. orchbee server stop now stops it, as on macOS.
  • A stuck network drive no longer holds up your terminals. Checking a folder on an unresponsive drive could stall the process that serves your terminals. It now gives up after 2 seconds.
  • Agents started through a version manager are recognized. An Agent launched through a shim, such as mise's, now shows in the sidebar as that Agent.
  • Gemini CLI shows as Gemini CLI in the sidebar, instead of its status title.
  • A worktree whose branch has its folder's name shows the folder in its location line, instead of the name twice.

Known limits

  • Windows x64, and macOS 13 or later on Apple silicon and Intel. Linux follows.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.

v0.1.0-beta.9

Choose a tag to compare

@github-actions github-actions released this 16 Nov 02:33

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

Fixed

  • A program that prints a very large number of links no longer risks closing every terminal. After a program printed tens of thousands of linked characters, such as a long listing of linked file names, scrolling part of its screen could stop the process that runs terminals, and every terminal closed with it. The oldest links on the screen now drop out instead: their text stays, and every terminal keeps running. Links come back for text that scrolls past that point.

Known limits

  • Windows x64 only. macOS and Linux follow.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.

v0.1.0-beta.8

Choose a tag to compare

@github-actions github-actions released this 16 Nov 00:28

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

Fixed

  • A program that ends in the middle of a screen update no longer closes every terminal. If a program exited while it was drawing (inside a synchronized update), or left an image animation running, the process that runs terminals could stop moments later, and every terminal it ran closed with it. Now only that terminal settles, and the others keep running.
  • Narrowing the window after a long list of links no longer closes every terminal. After a program printed many links, such as about a thousand linked file names, making the window narrower could stop the process that runs terminals. The oldest lines now lose their links, their text stays, and every terminal keeps running.
  • A wide character cut at the screen's edge no longer blanks a terminal. When a full-screen program narrowed its screen through a wide character, such as a Chinese character or an emoji, every window refused that terminal's screen and showed nothing. The cut character now shows as a narrow one.
  • The window's minimize, maximize and close buttons match the other icons in the top bar. Their symbols were drawn in the strongest text color, so they stood out next to the New Tab button. They now take the top bar's own icon color in every theme, named color themes included.

Known limits

  • Windows x64 only. macOS and Linux follow.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.

v0.1.0-beta.13

Choose a tag to compare

@github-actions github-actions released this 16 Nov 11:05

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

Fixed

  • Opening a terminal no longer stalls the others. The process that runs terminals started each new terminal's program on the same thread that serves every terminal, so a program that was slow to start held up typing, output and resizing everywhere. New terminals now start on a thread of their own.
  • A picture shown in the terminal can no longer freeze it. When a program shows a picture from a file (the Kitty graphics protocol), Orchbee now reads the file in the background and drops the picture if the file takes longer than 2 seconds or is larger than 32 MiB. Temporary picture files the program hands over are removed even when the picture is dropped.
  • Security: picture files are opened only from local drives. A program in the terminal could name a network share or a device as its picture file, and opening a network path on Windows can hand that computer a hash of your Windows sign-in (NTLM). Orchbee now refuses every path that is not on a local drive.
  • Stopping no longer hangs while a terminal is starting. The process that runs terminals waits up to 5 seconds for a terminal still being created, then exits.

Known limits

  • Windows x64 only. macOS and Linux follow.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.

v0.1.0-beta.12

Choose a tag to compare

@github-actions github-actions released this 16 Nov 09:03

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

Fixed

  • Installing no longer stops at "Setting up the orchbee command" on some computers (#1). When Windows let another account into your user folders, the installer refused to set up the orchbee command. Orchbee now makes its own folders private to you, SYSTEM and Administrators, and leaves your user folders unchanged. If the installer stopped there before, run this installer again; there is no need to uninstall first.

Known limits

  • Windows x64 only. macOS and Linux follow.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.

v0.1.0-beta.11

Choose a tag to compare

@github-actions github-actions released this 16 Nov 05:34

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

Fixed

  • Clearing the screen can no longer close every terminal. In rare cases, a program that cleared the screen while the scrollback history was full could stop the process that runs terminals, and every terminal closed with it. Ghostty's fix for this lands in a later version; until then Orchbee avoids the faulty path itself.
  • The Agent you are looking at now resumes after a restart too. After Orchbee restarted, the Agent in the Panel on screen could stay at an empty prompt instead of resuming its conversation, while the others resumed. It now resumes like the rest.

Known limits

  • Windows x64 only. macOS and Linux follow.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.

v0.1.0-beta.10

Choose a tag to compare

@github-actions github-actions released this 16 Nov 04:10

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

Fixed

  • Resizing a busy terminal no longer risks freezing every terminal. On Windows, resizing a terminal many times in a row while its program printed a lot of output could stop the process that runs terminals from responding, and every terminal froze with it. Resizes now reach the console in the background, so no other terminal waits for them.

Known limits

  • Windows x64 only. macOS and Linux follow.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.

v0.1.0-beta.7

Choose a tag to compare

@github-actions github-actions released this 15 Nov 19:57

Install

The .feed.json, .sig, orchbee-desktop-*.zip and .tgz files serve updates and npm; SHA256SUMS holds the checksums.

Fixed

  • Clearing or resetting a busy terminal no longer closes every terminal. When Clear terminal or Reset terminal ran while the terminal was printing, the process that runs terminals could stop, and every terminal it ran closed with it. It now keeps the newer output and keeps running.

Known limits

  • Windows x64 only. macOS and Linux follow.
  • Remote machines need Orchbee installed on the remote by hand.
  • On the remote computer, a Session started as administrator refuses remote connections. Stop it in an administrator terminal with orchbee server stop, and the remote connection starts its own.

Updating

Update with orchbee update. Running terminals and Agents are not interrupted: they keep the old version until they are restarted. Open Orchbee again to use the new one.

0.1.0-beta.1 has no update command. Coming from it, install this version once by hand: run the installer again, or npm install -g orchbee. Close the terminals you opened from the Orchbee window before you run the installer.