Pacenote

News › Release

Releasev0.2.0 · Oct 9, 2026

Pacenote v0.2.0

Verda is now Orbly, and a team hub lets several people share one Slack app.

brew update && brew upgrade

The tap renames the verda cask to orbly, so the upgrade quits Verda (the bot gets up to 20 seconds to finish its requests, and the rest resume on the next start) and installs Orbly.app in its place. New installs use brew install --cask orbly. If brew keeps listing verda, run brew uninstall --cask verda && brew install --cask orbly.

Verda is now Orbly

"Verda" collided with another company in the same AI infrastructure space, so the project has a name of its own: Orbly, your orbiting assistant. The repository moved to Ashon/orbly, and old links redirect.

Your setup keeps working:

  • While ~/.orbly does not exist, Orbly uses ~/.verda as it is, and VERDA_* settings are read as their ORBLY_* names. The bot log says so, with how to move: stop the bot, mv ~/.verda ~/.orbly, rename the VERDA_* keys in .env. Nothing is moved for you.
  • An old Verda and the new Orbly never run a bot at the same time; each sees the other's.
  • Run history and logs from Verda show as they are.

After upgrading:

  • The sandbox images and containers are now named orbly-*. In Settings > Sandbox, run "Build sandbox images" and "Restart proxy" (and "Recreate broker" if you use ops tools). The old verda-* images and containers can then be removed. If your .env names verda-reasoner, verda-renderer or verda-sandbox, remove those lines first.
  • The broker opens pull requests from orbly/* branches. The k8s account defaults to orbly-ro in the orbly namespace (sandbox/k8s/orbly-ro.yaml); to keep the old one, set OPS_K8S_SA=verda-ro and OPS_K8S_SA_NAMESPACE=verda.
  • macOS sees Orbly as a new app, so the theme and the run list width start from their defaults once.

Team hub

For a team in one workspace: a hub server holds the Slack app, and each member's Orbly answers that member's own mentions with their own CLI login, sandbox and tools.

  • The Slack tokens stay on the hub. Desktops get none; their Slack calls go through the hub, which allows only what the thread routed to them needs.
  • Members pair a desktop in Settings > Slack > Team hub: Orbly shows a code, you send @orbly connect <code> in Slack, and confirm your account in Orbly.
  • The hub runs as a Docker container on a server of its own, behind HTTPS (deploy/hub, README "Team hub").

Using Orbly with a Slack app of your own works as before; Settings > Slack now asks which of the two you use.