Skip to content

fix(desktop): keep Enterprise activation isolated - #3185

Merged
reachjalil merged 4 commits into
different-ai:devfrom
reachjalil:feature/enterprise-activation-first
Jul 27, 2026
Merged

fix(desktop): keep Enterprise activation isolated#3185
reachjalil merged 4 commits into
different-ai:devfrom
reachjalil:feature/enterprise-activation-first

Conversation

@reachjalil

@reachjalil reachjalil commented Jul 27, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • keep explicit bootstrap files supported while isolating them from unrelated legacy activation state
  • make the immutable Enterprise artifact authoritative over bootstrap activation opt-outs in Electron and the renderer
  • render Enterprise activation before sign-in and keep runtime/session commands blocked until activation completes
  • keep the verified openwork://connect activation consumer available while locked
  • preserve organization app name, logo, and icon from signed or HTTPS exchange activation claims
  • persist branding and completed Enterprise activation atomically, apply the desktop icon, then start the runtime
  • preserve Public and Cloud bootstrap behavior

Verification

  • node --test apps/desktop/electron/desktop-distribution.test.mjs apps/desktop/electron/workspace-store.test.mjs (35/35 passed)
  • bun test apps/app/tests/enterprise-activation.test.ts (10/10 passed)
  • node --test apps/desktop/electron/connect-link.test.mjs apps/desktop/electron/desktop-distribution.test.mjs (19/19 passed)
  • git diff --check

Order of operation

  1. Read the configured bootstrap file and immutable packaged distribution.
  2. Enterprise shows activation before sign-in.
  3. The Den activation page opens a one-time openwork://connect exchange link.
  4. Electron verifies the exact HTTPS Den claims while other desktop commands stay blocked.
  5. The confirmation dialog shows the organization and its HTTPS logo/icon.
  6. On approval, Electron persists server plus branding plus completed activation, applies the desktop icon, and starts the runtime.
  7. The activation gate clears; only then can the sign-in gate render.

Risk

Scoped to desktop activation precedence and the existing verified connect-link handoff. Default migration remains unchanged; explicitly configured bootstrap files remain readable; Public and Cloud defaults remain unchanged.

@vercel

vercel Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openwork-app Ready Ready Preview, Comment Jul 27, 2026 2:18pm
openwork-den Ready Ready Preview, Comment Jul 27, 2026 2:18pm
openwork-den-worker-proxy Ready Ready Preview, Comment Jul 27, 2026 2:18pm
openwork-landing Ready Ready Preview, Comment, Open in v0 Jul 27, 2026 2:18pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
openwork-diagnostics Skipped Skipped Jul 27, 2026 2:18pm

@vercel
vercel Bot temporarily deployed to Preview – openwork-diagnostics July 27, 2026 13:38 Inactive
@vercel

vercel Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

@reachjalil is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.

@benjaminshafii benjaminshafii left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

test

@reachjalil
reachjalil force-pushed the feature/enterprise-activation-first branch from e324dee to 5f94a9a Compare July 27, 2026 14:17
@reachjalil
reachjalil merged commit d7e295a into different-ai:dev Jul 27, 2026
6 of 10 checks passed
@reachjalil
reachjalil deleted the feature/enterprise-activation-first branch July 27, 2026 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants