Skip to main content
Version: 3.1

Release v3.1.9

3.1.9 refreshes Operaide Studio and fixes two failures that a single broken app or role could cause: a server that kept restarting at boot, and app settings dialogs that would not open.

For Users​

  • App launch links open in a new tab: Clicking an app on the home page (All Your Apps list or favorite cards) navigated the current tab away from the platform. Apps now open in a new tab and the home page stays open.
  • Cyclic role bundles no longer break the app configuration: A composite role that contained itself (creatable through the role editor) crashed the permission evaluation in the browser, so app settings dialogs failed to open for affected users. The evaluation now tolerates such cycles, and a database migration repairs the stored role bundles automatically.

For Developers​

Studio​

  • Clickable terminal links: Links printed in the Studio terminal are now rendered as clickable links.
  • Operaide look by default: The Operaide theme with a branded status bar is the default look, and the claude/codex installer shims ship with the platform.
  • Editor options per organization: Operators can opt into webview origin patterns, and organization admins can set editor options through the Studio Environment connection. See Studio.

Bug fixes​

  • A broken app can no longer take the server down at boot: An app composition that references itself while it is being built creates a cycle in its Aktor graph. Computing the deployment settings of such an app, at server start or when opening the settings dialog, ran in circles until the server ran out of memory and restarted, over and over. All settings computations now detect the cycle, log a warning naming the position in the graph, and report the broken deployment as an error for that app while the server keeps running. The defaults are also computed once per Reaktor instead of once per deployment, so a broken app produces one clear error instead of many.