Skip to content

feat: rebrand OpenWork to Micx Work (A1) + enterprise self-host readiness (A2) + server domain fix - #3573

Open
hackeshackes wants to merge 19 commits into
different-ai:devfrom
hackeshackes:micx-rename-enterprise-a1-a2
Open

feat: rebrand OpenWork to Micx Work (A1) + enterprise self-host readiness (A2) + server domain fix#3573
hackeshackes wants to merge 19 commits into
different-ai:devfrom
hackeshackes:micx-rename-enterprise-a1-a2

Conversation

@hackeshackes

Copy link
Copy Markdown

Summary

Per the Micx Work enterprise platform plan (plan/01-micx-work-enterprise-platform-design.md), this PR lands the first two deliverable tracks in one coordinated merge, plus a correctness fix surfaced during runtime verification:

A1 — Brand/namespace deep rename OpenWork → Micx Work (18 commits)

  • Deterministic codemod (scripts/rename/rename.mjs + verify-rename.mjs, zero brand residual; verify-rename exit 0)
  • Renamed: 27 workspace scopes (@openwork/*@micx/*, @openwork-ee/*@micx-ee/*), unscoped packages, OPENWORK_*MICX_* env, openwork://micx:// deep-links, x-openwork-*x-micx-* headers, openwork-*.extmicx-*.ext filenames, Helm chart openwork-eemicx-ee, README/CI/packaging/evals content
  • Data-compatible by design: typeid PK prefixes, den-db table/column names, den_/DEN_ control-plane prefix, OPENCODE_* engine vars, MySQL openwork_den name, and external published URLs all preserved

A2 — private-deploy readiness baseline

  • docs/enterprise/self-hosted-install-guide.md + initialization-guide.md (single-tenant self-host end-to-end incl. SSO/SCIM and break-glass recovery)
  • Production Helm values.example.yaml + Docker Compose docker-compose.prod.yml deploy templates (honest: only Helm documented as production path; compose production asset is new, not claimed pre-existing)
  • Cross-links added to the helm README

fix — point Micx Connect defaults back to production *.openworklabs.com domains

  • The A1 codemod over-reached by renaming the hosted infra endpoints too. The real deployed API/app/models still run at openworklabs.com, so apps/server's default trusted-origin allowlist and production model-catalog URL pointed at non-existent micxlabs.com hosts; live-endpoint tests would fail.
  • Reverts only the hosted runtime domains (app/api/models.openworklabs.com) in agent-context-cloud-probe, opencode-models-url, and the Micx capabilities-knowledge plugin, keeping the brand/package/identifier rename intact. Adjusts connect-gating test expectation order.

Files touched (by area)

  • scripts/rename/* — codemod + verify (new)
  • packages/*, apps/* — scope + identifier rename; git-mv of openwork-*micx-*
  • ee/{apps,packages}/* — EE scope + brand strings
  • packaging/{helm/micx-ee,docker} — chart rebrand + production deploy templates
  • docs/enterprise/*, docs/**, README, translated_readmes/**, .github/workflows/**, evals/**
  • apps/server/src/{agent-context-cloud-probe,opencode-models-url,opencode-plugins/micx-capabilities-knowledge}.{ts,test.ts} + related — domain revert

Intentionally preserved (data/runtime compatibility)

Marked no-change in review: typeid PK prefixes, den-db schema table/columns, den_/DEN_ control-plane, OPENCODE_*, MySQL db openwork_den, and already-published external URLs (github.com/different-ai/openwork, *.openworklabs.com, ttl.sh/...).

Test Plan

  • node scripts/rename/verify-rename.mjsOK: 仓内无 openwork 残留(白名单外) (exit 0)
  • pnpm buildexit 0 (28 workspace projects; app Vite build + Electron bridge OK)
  • apps/server bun test affected files → 152 pass / 0 fail (Node 22.23 + bun 1.3.13; 6 direct domain files + reconcile.e2e + gating)
  • Server smoke: bun src/cli.tsGET /health 200, {"ok":true,"version":"0.18.14","opencodeVersion":"1.17.11"}
  • (known flake, pre-existing, unrelated) full 168-file server suite shows FS/order flake in workspace-init.test.ts (passes standalone + with this PR's files); tracked for follow-up
  • (TODO) CI re-run on this branch to confirm ci-no-new-eval-flows + warden + codecov gates pass
  • (TODO) Reviewer confirmation that A3+ (auth/audit/model governance) is intentionally out of scope

Notes

  • Monorepo-wide mechanical rename + doc/deploy assets; no functional behavior changes beyond restoring correct production endpoints.
  • Merge intent: rebase-merge or squash at reviewer discretion; keep 19 commits or squash to a readable set.

hackeshackes and others added 19 commits August 5, 2026 20:35
- @openwork/* -> @micx/*, @openwork-ee/* -> @micx-ee/*, unscoped
  openwork-server/openwork-bootstrap/openwork-ui-mcp -> micx-*
- Apply codemod across apps/, packages/, ee/ manifests + root package.json
  (workspace --filter refs, deps, repo metadata)
- pnpm-workspace.yaml unchanged (package globs contain no openwork token)
- Excludes plan/
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…abs domains

The A1 codemod renamed every openwork token to micx, including the
hosted infrastructure domains referenced by apps/server defaults and tests.
But the actual deployed endpoints still run at *.openworklabs.com, so the
server's trusted-origin allowlist and production model catalog default would
point at non-existent micxlabs.com hosts and the live-endpoint tests would fail.

Revert only the *hosted runtime domains* to openworklabs.com (app/api/models)
in agent-context-cloud-probe, opencode-models-url, and the micx capabilities
knowledge plugin, keeping the micx brand/package/identifier renaming intact.
Adjust connect-gating test expectation ordering accordingly.
@vercel

vercel Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

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

A member of the Team first needs to authorize it.

@vercel

vercel Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated (UTC)
openwork-landing Ready Ready Preview, v0 Aug 6, 2026 3:24am

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.

1 participant