Add workspace support: create/link into a workspace, workspace list, workspace move

[netanelgilad]

Note

Description

Adds first-class workspace (organization) support to the Base44 CLI. Introduces a new base44 workspace command group (list, get, move) and lets create/link target a specific workspace via --workspace/--org, defaulting to the caller's personal workspace. Workspace selection is server-authoritative: the CLI passes IDs straight through and surfaces the backend's authorization errors rather than pre-validating roles client-side.

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

• New base44 workspace command group wired into the program: list (with a --role filter), get <workspace-id>, and move [workspace-id] (with --disconnect-integrations and -y/--yes).
• New core/workspace SDK module with listWorkspaces, getWorkspace, and moveAppToWorkspace, plus Zod schemas that transform the server's snake_case payload to camelCase. The first workspace returned is flagged isPersonal.
• create and link gain -w/--workspace <id> (with a hidden --org alias) and a shared resolveWorkspaceId helper: pass an explicit ID through, prompt interactively when the user belongs to more than one workspace, otherwise default to the personal workspace with no extra API call.
• createProject now accepts an organizationId and sends organization_id only when targeting a specific workspace.
• New getApp API + AppDetailSchema to resolve an app's current workspace for the interactive move flow.
• Extracted toJsonStdout into a shared cli/utils/json.ts so sandbox and workspace commands share one --json serializer; all workspace commands honor the global --json flag.
• Added integration tests for the new commands and flows, plus workspace fixtures/handlers in TestAPIServer.

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (npm test)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated docs/ (AGENTS.md) if I made architectural changes

Additional Notes

Move and workspace-targeted creation are intentionally server-authoritative — the CLI does not filter by role but relies on the backend to authorize and return clear block reasons, matching the web builder. getWorkspace is backed by listWorkspaces since there is no per-workspace GET the CLI principal is authorized for.

---

_{🤖 Generated by Claude | 2026-07-15 15:07 UTC | a56c290}

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.1.4-pr.567.a56c290

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.1.4-pr.567.a56c290"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.1.4-pr.567.a56c290"
  }
}

• 📦 Preview Package: @base44-preview/cli@0.1.4-pr.567.a56c290
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}