Skip to main content

v0.4.18 Local Workspaces and Team Collaboration

Release date: 2026-09-27

Local workspaces​

  • A new personal workspace prepares its own local database and user identity on this computer. Creating one while signed in to a platform account uses the same local flow. Platform account details are managed separately from the current local member identity.
  • If the local workspace list is temporarily unavailable, the app keeps the existing selection. After an interrupted startup or creation, it checks the identity and database state before opening the workspace or offering recovery.
  • Databases in the legacy installation path move to an isolated directory with a pre-upgrade backup. Older clients must upgrade before they can establish sessions, write data, or use real-time collaboration with a new team host.

Team collaboration​

  • You can enable LAN team collaboration from an existing personal workspace and keep its data. New local teams have no license expiry or team/member count limit; member identity and role permissions still apply. Verified existing local teams can continue local collaboration after their old commercial authorization expires.
  • Members can use device invitation codes to join from another computer and manage their devices. Team owners can review member devices, revoke unused devices, and review or cancel unused invitations.
  • Members can leave a team from Settings. This revokes only their own member credentials and device sessions; it does not delete team data. Owners retain the team management identity. If the result is unclear, the app offers a status check before another submission.
  • When team enablement or recovery is interrupted, the app checks the existing data and operation record so it can reconcile steps already committed.

Accounts and AI​

  • When switching a local workspace, member, or platform account, conversations, approvals, references, translation, and background runs remain bound to their original workspace and account.
  • General AI uses the current platform account's subscription and quota. Background runs retain the original consumer account, and usage is counted only after completion is confirmed. Retrying after a lost response does not count the same completion twice. Bring-your-own-key use still follows local settings.
  • Platform registration, profile management, and renewal no longer rely on automatic creation of a cloud personal workspace. The related account and quota features require the matching cloud service version.

See the in-app release notes for the complete change list.