---
title: Cloud Workspaces Out of Beta and Chrome Extensions in the Browser
date: 2026-11-08
image: /changelog/2026-11-08-cloud-hero.png
version: 2.0.6
highlights:
- icon: cloud
title: Cloud workspaces are out of beta
description: On Team and Ultra, with port forwarding, resizing and your own agent sign-in
- icon: shield
title: Chrome extensions in the browser
description: Install from the Chrome Web Store and sign in with 1Password or LastPass, passkeys included
- icon: message
title: The chat interface is out of Experimental
description: Pick Terminal or Chat during onboarding, or switch in Settings → General
---
## Cloud Workspaces Are Out of Beta
Cloud workspaces run your agents on a cloud machine, so they keep working when your laptop sleeps. They are now part of the Team and Ultra plans .
- **Forward ports to your computer** - click **Forward** in the Share popover to open a cloud dev server on localhost
- **Manual sign-in** - keep Claude Code or Codex signed in with your own script, in **Settings → Agents**
- **Reach your own machines** - turn on **Settings → Hosts → Cloud workspaces** to let cloud agents use a host you own
Resize a workspace or list its forwards from the CLI :
```bash
superset ws update --machine-size xlarge
superset ports list
```
Pick **Cloud** as the host when you create a workspace. Docs: [Cloud Workspaces](https://docs.paradev.com/cloud-workspaces).
## Chrome Extensions in the Browser
The browser pane now runs Chrome extensions. Install them from the Chrome Web Store, pin them to the toolbar, and sign in with 1Password or LastPass, passkeys included. Contributed by [@serhii-kucherenko](https://github.com/serhii-kucherenko).
- 1Password talks to its desktop app, ad blockers like uBlock Origin Lite block ads, and Vimium and Google Translate work
- Agents get their own browser without your extensions, and every install asks you first
- Machines with more memory keep more pages open in the background, and a page that plays audio or holds a half-filled form is never closed
Open a browser pane with ⌘⇧B and click the puzzle icon. From the CLI: `superset browser extensions list` .
## The Chat Interface Is Out of Experimental
Chat runs your agent as a conversation instead of a terminal. New users pick **Terminal** or **Chat** during onboarding .

- Chips above the composer show running subagents and background tasks
- A chat cut off by a quit or crash asks to resume on the next launch
- New chats keep each agent's last model, effort and mode
Turn it on in **Settings → General → Chat interface**. Docs: [Chat interface](https://docs.paradev.com/chat).
## Paradev Is MIT Licensed
Paradev moved from the Elastic License to MIT, so you can use and change the code however you want.
## Improvements
- **Import from other tools** - onboarding finds worktrees left by Conductor, T3 Code, Orca and others and imports them
- **Archive automations** - archiving replaces delete and has Undo. Restore or delete permanently from the **Archived** tab
- **Same workspace for automations** - every run can reuse one workspace, and **Continue** picks up the last conversation
- **Set up a workspace from the keyboard** - type `#` in the new-workspace composer to pick project, host, environment and size
- **Several GitHub organizations** - connect more than one GitHub organization to one Paradev organization
- **Pages** - share a page with **Can edit**, and pinned pages show in the sidebar
- **New plugins** - Inngest, Supabase, Firecrawl and Wispr Flow
- **Tribute ringtone** - the train whistle Conductor played when a workspace finished, in **Settings → Ringtones**
- **`.paradev` folders** - app data moves to `~/.paradev` by itself, and repos keep working from `.superset/`
---
**Bug fixes**
- Copy in cloud workspace terminals reaches your clipboard
- Narrow panes and small windows no longer paint text over text
- Pull request lists show rows before their checks load
- Schedules whose hours wrap past midnight fire every slot
- Chats keep their permission mode across resume and fork, and prompts queue while a turn waits
- Chats started from the CLI or mobile open as tabs
- A failed plugin connect says why, and plugin accounts connect in more than one organization
- Only organization admins can connect a GitHub account