The open alternative to Salesforce, designed for AI.
TypeScript crmcrm-systemcustomergood-first-issuegraphqlhacktoberfestjavascriptmarketingmonoreponestjsopen-sourcepostgresqlreactreactjssalestypescriptweb
Clean up remaining legacy SDK CLI references (#28721)
Weiko0438ddfed089
diff --git a/.github/workflows/ci-agent-skills-drift.yaml b/.github/workflows/ci-agent-skills-drift.yamlindex 271c31f191d..dbf34cdab90 100644--- a/.github/workflows/ci-agent-skills-drift.yaml+++ b/.github/workflows/ci-agent-skills-drift.yaml@@ -83,7 +83,7 @@ jobs:see fit. Only these kinds of changes are skill-relevant:- CLI commands, subcommands, flags, defaults, or help text- (`packages/twenty-cli/src/commands/**`, `packages/twenty-sdk/src/cli/commands/**`)+ (`packages/twenty-cli/src/commands/**`)- `define*` function signatures, config properties, validation rules,or their warnings (`packages/twenty-sdk/src/sdk/define/**`)- Enum / string-union values and manifest types@@ -92,12 +92,9 @@ jobs:`twenty-client-sdk` package.json, or in their public entry points- Front-component runtime hooks and host API(`packages/twenty-sdk/src/sdk/front-component/**`)- - Scaffold templates (`packages/twenty-cli/app-template/**`,- `packages/create-twenty-app/src/constants/template/**`)+ - Scaffold templates (`packages/twenty-cli/app-template/**`)and scaffolder flags/prompts (`packages/twenty-cli/src/commands/app/init/**`,- `packages/twenty-cli/src/app/create-app-project.ts`,- `packages/create-twenty-app/src/cli.ts`,- `packages/create-twenty-app/src/create-app.command.ts`)+ `packages/twenty-cli/src/app/create-app-project.ts`)- Environment variables injected into logic functions or front components- Error codes surfaced to app developers- Default ports and instance URLs used during development@@ -112,7 +109,7 @@ jobs:| Source area | Skill content ||---|---|- | CLI commands (`twenty-cli/src/commands`, `twenty-sdk/src/cli/commands`) | `references/manage-app/cli-and-sync.md`, `skills/manage-app/SKILL.md`, `references/concepts/operating-rules.md` |+ | CLI commands (`twenty-cli/src/commands`) | `references/manage-app/cli-and-sync.md`, `skills/manage-app/SKILL.md`, `references/concepts/operating-rules.md` || Scaffolder flags, prompts, template | `skills/create-app/SKILL.md`, `references/develop-app/app-structure.md` || `defineObject`/`defineField`/relations/indexes | `references/develop-app/data-model.md` || `defineApplication`/roles/install hooks/variables | `references/concepts/how-apps-work.md`, `references/publish-app/prepare-for-app-store.md` |diff --git a/.github/workflows/ci-app-docs-drift.yaml b/.github/workflows/ci-app-docs-drift.yamlindex 74fd306ceb5..5caabfafb24 100644--- a/.github/workflows/ci-app-docs-drift.yaml+++ b/.github/workflows/ci-app-docs-drift.yaml@@ -71,7 +71,7 @@ jobs:see fit. Only these kinds of changes are documentation-relevant:- CLI commands, subcommands, flags, defaults, or help text- (`packages/twenty-cli/src/commands/**`, `packages/twenty-sdk/src/cli/commands/**`)+ (`packages/twenty-cli/src/commands/**`)- `define*` function signatures, config properties, validation rules,or their warnings (`packages/twenty-sdk/src/sdk/define/**`)- Enum / string-union values and manifest types@@ -80,12 +80,9 @@ jobs:`twenty-client-sdk` package.json, or in their public entry points- Front-component runtime hooks and host API(`packages/twenty-sdk/src/sdk/front-component/**`)- - Scaffold templates (`packages/twenty-cli/app-template/**`,- `packages/create-twenty-app/src/constants/template/**`)+ - Scaffold templates (`packages/twenty-cli/app-template/**`)and scaffolder flags/prompts (`packages/twenty-cli/src/commands/app/init/**`,- `packages/twenty-cli/src/app/create-app-project.ts`,- `packages/create-twenty-app/src/cli.ts`,- `packages/create-twenty-app/src/create-app.command.ts`)+ `packages/twenty-cli/src/app/create-app-project.ts`)- Environment variables injected into logic functions or front components- Error codes surfaced to app developers@@ -98,13 +95,13 @@ jobs:| Source area | Docs pages ||---|---|- | CLI commands (`twenty-cli/src/commands`, `twenty-sdk/src/cli/commands`) | `operations/cli.mdx`, `getting-started/quick-start.mdx`, `operations/sync-and-recovery.mdx`, `getting-started/local-server.mdx`, `getting-started/scaffolding.mdx` |+ | CLI commands (`twenty-cli/src/commands`) | `operations/cli.mdx`, `getting-started/quick-start.mdx`, `operations/sync-and-recovery.mdx`, `getting-started/local-server.mdx`, `getting-started/scaffolding.mdx` || `defineObject`/`defineField`/relations/indexes | `data/*.mdx` || `defineApplication`/roles/install hooks/variables | `config/*.mdx` || Logic functions, triggers, connections, agents/skills | `logic/*.mdx` || Views, navigation, page layouts, front components, command menu | `layout/*.mdx` || Publish/install/deploy, versioning, engines | `operations/publishing.mdx`, `operations/sync-and-recovery.mdx` |- | Testing APIs (`twenty-sdk/cli` operations) | `operations/testing.mdx` |+ | App test helpers (`twenty-cli/app-template/src/__tests__`) | `operations/testing.mdx` || Scaffold template | `getting-started/project-structure.mdx`, `getting-started/quick-start.mdx`, `operations/testing.mdx`, `operations/publishing.mdx` || client SDK (`core`/`metadata`/`rest`/`generate`) | `logic/logic-functions.mdx`, `layout/front-components.mdx`, `operations/cli.mdx` || Enum value sets (FieldType, ViewType, availabilityType, NavigationMenuItemType, ...) | the page documenting that value set (search for the enum name) |diff --git a/CLAUDE.md b/CLAUDE.mdindex e2a9a4e6a4b..2826c72e54e 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -1,6 +1,6 @@# CLAUDE.md-Twenty is an open-source CRM — an Nx / Yarn 4 monorepo. Main packages: `twenty-front` (React 18, Jotai, Linaria, Vite), `twenty-server` (NestJS, TypeORM, PostgreSQL, Redis, GraphQL), `twenty-shared` (isomorphic types/utils), `twenty-ui`, `twenty-sdk` (application SDK + CLI), `twenty-e2e-testing` (Playwright).+Twenty is an open-source CRM — an Nx / Yarn 4 monorepo. Main packages: `twenty-front` (React 18, Jotai, Linaria, Vite), `twenty-server` (NestJS, TypeORM, PostgreSQL, Redis, GraphQL), `twenty-shared` (isomorphic types/utils), `twenty-ui`, `twenty-sdk` (application definitions and runtime), `twenty-cli` (standalone CLI), `twenty-e2e-testing` (Playwright).Match the surrounding code — the adjacent files in the directory you are editing beat any written rule, including for file naming, which varies by area.diff --git a/README.md b/README.mdindex e6137b5c569..4ae7858d549 100644--- a/README.md+++ b/README.md@@ -39,7 +39,10 @@ The fastest way to get started. Sign up at [twenty.com](https://twenty.com) andScaffold a new app with the Twenty CLI:```bash-npx create-twenty-app my-app+npm install -g twenty+twenty app init my-app+cd my-app+yarn install```Define objects, fields, and views as code:@@ -63,7 +66,8 @@ export default defineObject({Then ship it to your workspace:```bash-npx twenty app:publish --private+twenty auth login --url https://your-workspace.twenty.com+twenty app publish --private```See the [app development guide](https://docs.twenty.com/developers/extend/apps/getting-started) for objects, views, agents, and logic functions.diff --git a/packages/create-twenty-app/README.md b/packages/create-twenty-app/README.mdindex 1a956664e94..3142b061987 100644--- a/packages/create-twenty-app/README.md+++ b/packages/create-twenty-app/README.md@@ -1,18 +1,3 @@-# create-twenty-app is retired+# create-twenty-app-Install the standalone Twenty CLI and create your app:--```sh-npm install -g twenty-twenty app init my-app-cd my-app-yarn install-twenty auth login --url https://your-workspace.twenty.com-twenty app dev --create-```--For existing apps, keep `twenty-sdk` as an application dependency. Install `twenty` globally and replace `yarn twenty ...` scripts with the corresponding `twenty app ...` commands.--This package only prints migration instructions and exits with code 1. It no longer creates files, installs dependencies, starts servers, or authenticates.--See the [CLI reference](https://docs.twenty.com/developers/extend/apps/operations/cli).+This package is retired. See the [Twenty CLI reference](https://docs.twenty.com/developers/extend/apps/operations/cli) for app creation.diff --git a/packages/twenty-agent-skills/.codex-plugin/plugin.json b/packages/twenty-agent-skills/.codex-plugin/plugin.jsonindex 2f3d30722f3..982ffba18c9 100644--- a/packages/twenty-agent-skills/.codex-plugin/plugin.json+++ b/packages/twenty-agent-skills/.codex-plugin/plugin.json@@ -11,7 +11,6 @@"license": "AGPL-3.0","keywords": ["twenty",- "create-twenty-app","mcp","oauth","crm",@@ -29,11 +28,7 @@"longDescription": "Scaffold, develop, deploy, and publish Twenty apps end-to-end. Five focused skills cover app creation, entity development (objects, fields, logic, layouts, front components), remote/sync/deploy operations, marketplace publishing assets, and workspace data retrieval via MCP. The bundled Twenty docs MCP server keeps guidance current, and the setup helper wires per-user workspace MCP with OAuth in one command.","developerName": "Twenty PBC","category": "Coding",- "capabilities": [- "Interactive",- "Read",- "Write"- ],+ "capabilities": ["Interactive", "Read", "Write"],"websiteURL": "https://twenty.com/","privacyPolicyURL": "https://twenty.com/privacy-policy","termsOfServiceURL": "https://twenty.com/terms",diff --git a/packages/twenty-agent-skills/SMOKE-TEST.md b/packages/twenty-agent-skills/SMOKE-TEST.mdindex 3664c56178c..83cfa9e04d5 100644--- a/packages/twenty-agent-skills/SMOKE-TEST.md+++ b/packages/twenty-agent-skills/SMOKE-TEST.md@@ -13,7 +13,7 @@ npx nx run twenty-agent-skills:buildnpx skills add ./packages/twenty-agent-skills/dist --skill create-app develop-app manage-app```-After the first successful publish from `main`, the same distribution is available at `https://github.com/twentyhq/twenty/tree/agent-skills`. Record the source revision and installation method with each new run. The recorded run below predates the distribution migration and documents the app workflow only.+After the first successful publish from `main`, the same distribution is available at `https://github.com/twentyhq/twenty/tree/agent-skills`. Record the source revision and installation method with each new run.## 1. Bring up a self-hosted instance@@ -27,24 +27,27 @@ npx nx start twenty-serverWait for `http://localhost:3000/healthz` to return 200. This instance is self-hosted for the purposes of the test: a non-`twenty.com` host, over plain HTTP, on a port the user chose.-## 2. Authenticate a remote+## 2. Install the CLI and authenticate a remote-The scaffolder reuses an existing remote's credentials when one matches the target URL, which is what makes the rest of the run non-interactive. Add one with an API key from the instance's settings:+Install the standalone CLI. Create an API key in the target instance's settings, then pass it through standard input:```bash-yarn twenty remote:add --url http://localhost:3000 --api-key <api-key> --as selfhosted+npm install -g twenty+printf '%s' "$TWENTY_API_KEY" | twenty auth login --with-token --url http://localhost:3000 --name selfhosted```-`DEV_API_KEY` in `twenty-sdk` does not work here. It is signed for the `twenty-app-dev` Docker image's `APP_SECRET`, so a locally built server with its own secret rejects it as `Token invalid`.+Use a key issued by this instance, not credentials from another test server. For browser sign-in, omit `--with-token` and the pipe.## 3. Scaffold, following `create-app````bash-npx create-twenty-app@latest smoke-crm --url http://localhost:3000 \- --name smoke-crm --display-name "Smoke CRM" --description "Self-hosted smoke test app"+twenty app init smoke-crm --display-name "Smoke CRM" --description "Self-hosted smoke test app"+cd smoke-crm+yarn install+twenty app apply --create --remote selfhosted```-Expect `Authenticating -> Reusing existing credentials`, then `Application created successfully`. Confirm the app registered on the instance rather than only on disk:+`app init` only creates local files. The first `app apply --create` registers and installs the app. Confirm the app exists on the instance:```sqlselect id, "universalIdentifier", version from core.application;@@ -54,13 +57,14 @@ One row must carry the `APPLICATION_UNIVERSAL_IDENTIFIER` from the generated `sr## 4. Develop, following `develop-app`+From the generated app directory:+```bash-cd smoke-crm-yarn twenty dev:add object # interactive; needs a TTY-yarn twenty apply+twenty app add object --name ticket --name-plural tickets --create-view --create-navigation-menu-item --create-page-layout --no-input+twenty app apply --remote selfhosted```-`apply` prints a plan and then `Synced <app name>`. Confirm the entity reached the instance:+Confirm the apply command succeeds and the entity reached the instance:```sqlselect "nameSingular", "namePlural" from core."objectMetadata" where "nameSingular" = 'ticket';@@ -68,15 +72,3 @@ select table_schema || '.' || table_name from information_schema.tables where ta```Both must return a row. The second proves the workspace migration ran and the physical table exists, which a successful sync message alone does not.--## Recorded run--Executed against a locally built server on `http://localhost:3000`, Node 24.16.0:--- Scaffold reused the `selfhosted` remote credentials, no browser OAuth, and reported `Application created successfully`.-- `core.application` carried the scaffolded identifier `e606ca1a-4035-4c20-87ac-f49e5af6f05c` at `0.1.0`.-- `dev:add object` generated `src/objects/ticket.ts` plus its view, record-page fields, navigation menu item, and record page layout.-- `yarn twenty apply` reported `Plan: 50 to add, 0 to change, 0 to destroy` and `Synced Smoke CRM (5 files)`.-- `core."objectMetadata"` held `ticket` / `tickets`, `core."navigationMenuItem"` held `ticket`, and the physical table `_ticket` existed in the workspace schema.--Note for whoever runs this next: `create-twenty-app` still calls `yarn twenty dev --once` internally during its install step, while the skills direct agents to `yarn twenty apply`. That is the scaffolder's own behavior, not skill guidance.diff --git a/packages/twenty-agent-skills/assets/screenshots/README.md b/packages/twenty-agent-skills/assets/screenshots/README.mdindex 17d6a748503..0d6687abe8b 100644--- a/packages/twenty-agent-skills/assets/screenshots/README.md+++ b/packages/twenty-agent-skills/assets/screenshots/README.md@@ -6,8 +6,8 @@ The Codex marketplace listing for the Twenty plugin requires ≥ 1 screenshot shThree screenshots, all PNG, at marketplace resolution (preferably 1600×1000 or higher, 16:10):-1. **`01-create-app.png`** — `create-app` mid-flow: user prompt asking to scaffold a new Twenty app, the agent asking for the instance URL, and the `create-twenty-app` output visible.-2. **`02-develop-and-sync.png`** — `develop-app` adding an entity through `yarn twenty dev:add`, followed by `yarn twenty apply` syncing successfully.+1. **`01-create-app.png`** — `create-app` mid-flow: user prompt asking to scaffold a new Twenty app, the agent asking for the instance URL, and the `twenty app init` output visible.+2. **`02-develop-and-sync.png`** — `develop-app` adding an entity through `twenty app add`, followed by `twenty app apply` syncing successfully.3. **`03-use-twenty-mcp.png`** — `use-twenty-mcp` retrieving a workspace records table where the record-name column is rendered as a linked Markdown table.## After Adding the Files@@ -26,4 +26,4 @@ Three screenshots, all PNG, at marketplace resolution (preferably 1600×1000 or## What Not to Include-No customer data, real workspace URLs, real API keys, or unreleased confidential content. Use the bundled local Docker instance or a dedicated demo workspace for captures.+No customer data, real workspace URLs, real API keys, or unreleased confidential content. Use a disposable local server or a dedicated demo workspace for captures.diff --git a/packages/twenty-agent-skills/references/concepts/operating-rules.md b/packages/twenty-agent-skills/references/concepts/operating-rules.mdindex 2c5636c81de..5fa3ce4bbaa 100644--- a/packages/twenty-agent-skills/references/concepts/operating-rules.md+++ b/packages/twenty-agent-skills/references/concepts/operating-rules.md@@ -18,7 +18,7 @@ This file is the single source of truth for the cross-skill rules. Harness-specitwenty app add front-component --name invoice-panel --no-input```- 2. **The CLI is missing**: install the standalone `twenty` package, or ask the user to install it when their environment requires that. The SDK no longer provides a fallback CLI.+ 2. **The CLI is missing**: install the standalone `twenty` package, or ask the user to install it when their environment requires that.3. **The entity type is unsupported**: use the corresponding `define*` export directly. The standalone CLI currently generates objects, fields, logic functions and front components.4. **Otherwise, write the file by hand.** Follow the example on the matching docs page (append `.md` to its URL), or an existing file of the same kind in the app, check it against the types exported by `twenty-sdk/define`, and generate every identifier with `crypto.randomUUID()` instead of inventing one.diff --git a/packages/twenty-agent-skills/skills/create-app/SKILL.md b/packages/twenty-agent-skills/skills/create-app/SKILL.mdindex 168555e059b..8383f41a9e9 100644--- a/packages/twenty-agent-skills/skills/create-app/SKILL.md+++ b/packages/twenty-agent-skills/skills/create-app/SKILL.md@@ -22,11 +22,11 @@ cd <app-name>yarn install```-`app init` only writes files. It does not install dependencies, initialize Git, start Docker, authenticate, or perform an initial sync. `create-twenty-app` is retired.+`app init` only writes files. It does not install dependencies, initialize Git, start Docker, authenticate, or perform an initial sync.Use `--path <directory>` for a different destination and `--display-name` or `--description` for metadata. The positional name is the package name.-Twenty Cloud and self-hosted instances are supported. Ask for the existing Twenty workspace URL when connection is needed. If the user wants a local server, use the documented Docker or repository development environment; the CLI has no `docker:*` commands.+Twenty Cloud and self-hosted instances are supported. Ask for the existing Twenty workspace URL when connection is needed. If the user wants a local server, use the documented Docker or repository development environment.```bashtwenty auth login --url <twenty-instance-url> --name devdiff --git a/packages/twenty-apps/examples/media-notes/README.md b/packages/twenty-apps/examples/media-notes/README.mdindex 6a3095e1ce4..418e52786c1 100644--- a/packages/twenty-apps/examples/media-notes/README.md+++ b/packages/twenty-apps/examples/media-notes/README.md@@ -23,7 +23,7 @@ on. Serve the front build from the server rather than on its own port:```sh# from the repo root-npx nx build twenty-sdk+npx nx build twenty-cliNODE_ENV=production npx nx build twenty-frontnpx nx build twenty-servercp -r packages/twenty-front/build packages/twenty-server/dist/front@@ -31,7 +31,9 @@ cp -r packages/twenty-front/build packages/twenty-server/dist/front# start:ci, not start: the watch target would rimraf dist and delete the frontnpx nx start:ci twenty-server &-node packages/twenty-sdk/dist/cli.cjs app:publish --private && node packages/twenty-sdk/dist/cli.cjs app:install+node packages/twenty-cli/dist/cli.cjs auth login --url http://localhost:3000 --name local+node packages/twenty-cli/dist/cli.cjs app publish --private --path packages/twenty-apps/examples/media-notes --remote local+node packages/twenty-cli/dist/cli.cjs app install --path packages/twenty-apps/examples/media-notes --remote local# then, from this directoryFRONT_BASE_URL=http://localhost:3000 npx playwright test --project=setup --project=chromiumdiff --git a/packages/twenty-apps/public/fireflies/src/__tests__/twenty-fireflies.integration-test.ts b/packages/twenty-apps/public/fireflies/src/__tests__/twenty-fireflies.integration-test.tsindex 7f4d9e2db70..f5190559ad3 100644--- a/packages/twenty-apps/public/fireflies/src/__tests__/twenty-fireflies.integration-test.ts+++ b/packages/twenty-apps/public/fireflies/src/__tests__/twenty-fireflies.integration-test.ts@@ -28,7 +28,7 @@ describe('App installation', () => {});// The published twenty-client-sdk types only export CoreApiClient/CoreSchema;-// the enum exports appear at runtime after dev:generate-client regenerates the+// the enum exports appear at runtime after twenty app generate-client regenerates the// client against the server, hence the cast and the runtime guard.type GeneratedCoreSchemaRuntime = {enumCallRecordingStatusEnum?: Record<string, string>;diff --git a/packages/twenty-client-sdk/src/core/generated/index.ts b/packages/twenty-client-sdk/src/core/generated/index.tsindex 7d78c8941d7..50f0f5f616f 100644--- a/packages/twenty-client-sdk/src/core/generated/index.ts+++ b/packages/twenty-client-sdk/src/core/generated/index.ts@@ -11,7 +11,7 @@ export class CoreApiClient {constructor(_options?: TwentyClientOptions) {throw new Error('CoreApiClient was not generated. ' +- 'Install this app on a Twenty instance or run `yarn twenty dev`.',+ 'Run `twenty app generate-client` against your workspace to generate the client.',);}}diff --git a/packages/twenty-client-sdk/src/core/generated/schema.ts b/packages/twenty-client-sdk/src/core/generated/schema.tsindex 040312c36cf..ef58679fe1e 100644--- a/packages/twenty-client-sdk/src/core/generated/schema.ts+++ b/packages/twenty-client-sdk/src/core/generated/schema.ts@@ -1,2 +1,2 @@-// Stub — overwritten by `twenty dev:build` or `twenty dev`+// Stub, overwritten by `twenty app generate-client`.export type CoreSchema = {};diff --git a/packages/twenty-docs/developers/extend/apps/getting-started/local-server.mdx b/packages/twenty-docs/developers/extend/apps/getting-started/local-server.mdxindex 1aca82fd74c..8a2a15b90f7 100644--- a/packages/twenty-docs/developers/extend/apps/getting-started/local-server.mdx+++ b/packages/twenty-docs/developers/extend/apps/getting-started/local-server.mdx@@ -4,7 +4,7 @@ description: Connect the standalone CLI to a local Twenty server.icon: 'server'----The standalone CLI connects to a running Twenty server. It does not start or manage Docker containers, and the SDK's `docker:*` commands have been removed.+The standalone CLI connects to a running Twenty server. It does not start or manage Docker containers.Use the [self-hosting guide](/developers/self-host/self-host) to run Twenty with Docker. In a Twenty repository checkout, the existing development environment also works:@@ -28,6 +28,6 @@ Use a separate disposable server or workspace. Integration test setup installs aThe generated CI workflow provisions an isolated instance through `twentyhq/twenty/.github/actions/spawn-twenty-app-dev-test@main` and installs the standalone CLI separately.-## Existing projects+## Project dependencies-Keep `twenty-sdk` and `twenty-client-sdk` installed per project. Install the `twenty` CLI globally, then run `twenty app typecheck`, `twenty app build`, and `twenty app apply` from the app directory.+Install `twenty-sdk` and `twenty-client-sdk` as project dependencies. Install the `twenty` CLI globally, then run `twenty app typecheck`, `twenty app build`, and `twenty app apply` from the app directory.diff --git a/packages/twenty-docs/developers/extend/apps/getting-started/quick-start.mdx b/packages/twenty-docs/developers/extend/apps/getting-started/quick-start.mdxindex 359a40eda7a..9dd4e77a221 100644--- a/packages/twenty-docs/developers/extend/apps/getting-started/quick-start.mdx+++ b/packages/twenty-docs/developers/extend/apps/getting-started/quick-start.mdx@@ -48,8 +48,6 @@ twenty app apply`plan` previews changes. `apply` uploads and synchronizes once. Use `--no-delete` to keep remote entities missing from source, or `--yes` to permit object and field deletions without a prompt. All three commands require an authenticated remote and registration ownership.-`create-twenty-app` and the SDK's bundled CLI are retired. See the [CLI migration guide](/developers/extend/apps/operations/cli#migrating-from-the-sdk-cli).-## What you can buildApps are composed of **entities** — each defined as a TypeScript file with a single `export default`:diff --git a/packages/twenty-docs/developers/extend/apps/operations/cli.mdx b/packages/twenty-docs/developers/extend/apps/operations/cli.mdxindex bf71f843ed0..16e5a70e4ef 100644--- a/packages/twenty-docs/developers/extend/apps/operations/cli.mdx+++ b/packages/twenty-docs/developers/extend/apps/operations/cli.mdx@@ -21,13 +21,6 @@ npm install -g twentytwenty --version```-<Warning>- Older versions of `twenty-sdk` include a legacy `twenty` binary. In apps- still using those versions, `npx twenty` can run that local binary.- Use `npx twenty@latest` to select the standalone CLI explicitly. The current- SDK no longer includes a CLI binary.-</Warning>-The examples below use `twenty`. Prefix them with `npx twenty@latest` if you did not install it globally. Run `twenty commands` for the full command list and `twenty <command> --help` for the options of one command.| Command | What it does |@@ -173,12 +166,6 @@ twenty doctor --offlineBuild output belongs to the CLI. Do not read `.twenty/output/manifest.json` or import internal build code; read `data.manifest` from `twenty app build --json`.-## Migrating from the SDK CLI--The SDK's `twenty` binary, `twenty-sdk/cli`, and `twenty-sdk/build` are removed. `create-twenty-app` is retired; use `twenty app init`, then `yarn install` and `twenty auth login`. Keep `twenty-sdk` installed for application definitions and runtime helpers.--Replace colon commands with the commands above. The standalone CLI does not provide `docker:*` or `dev:catalog-sync`; manage servers through Docker or the repository dev environment. If your app still uses an older SDK version, run `twenty doctor` to diagnose its legacy binary shadowing the global CLI.-## Full referenceThe [command reference](https://github.com/twentyhq/twenty/blob/main/packages/twenty-cli/docs/commands.md) covers every flag, permission, output format and exit code.diff --git a/packages/twenty-docs/developers/extend/apps/operations/testing.mdx b/packages/twenty-docs/developers/extend/apps/operations/testing.mdxindex d3131f01151..d682430ae17 100644--- a/packages/twenty-docs/developers/extend/apps/operations/testing.mdx+++ b/packages/twenty-docs/developers/extend/apps/operations/testing.mdx@@ -149,7 +149,7 @@ it('installs the app', async () => {});```-The SDK's programmatic CLI/build exports have been removed. For a manifest, read `data.manifest` from `twenty app build --json`. For deployed function tests, use the metadata client's `executeOneLogicFunction` mutation with a user token. Resolve the function within the installed application's ID before invoking it.+For a manifest, read `data.manifest` from `twenty app build --json`. For deployed function tests, use the metadata client's `executeOneLogicFunction` mutation with a user token. Resolve the function within the installed application's ID before invoking it.## Running testsdiff --git a/packages/twenty-docs/getting-started/core-concepts/apps.mdx b/packages/twenty-docs/getting-started/core-concepts/apps.mdxindex d49859f7b10..ace421331e3 100644--- a/packages/twenty-docs/getting-started/core-concepts/apps.mdx+++ b/packages/twenty-docs/getting-started/core-concepts/apps.mdx@@ -1,10 +1,9 @@---title: Apps-icon: "cube"+icon: 'cube'description: Extend Twenty with code — custom objects, server-side logic, UI components, and AI agents, all as TypeScript packages.----Most CRMs give you a config panel. Twenty gives you a platform. Apps are how developers extend Twenty beyond what the UI offers — defining data models, server-side logic, UI components, and AI capabilities as code, then deploying them to one or more workspaces.## Why apps exist@@ -17,13 +16,13 @@ Apps let you build these as first-class extensions — not brittle scripts talkiAn app is a TypeScript package that declares **entities** using the `twenty-sdk`:-| Entity | What it does |-|--------|-------------|-| **Objects & Fields** | New data tables and fields on existing objects — same treatment as built-in ones |-| **Logic Functions** | Server-side TypeScript triggered by HTTP routes, cron schedules, or database events |-| **Front Components** | Sandboxed React components that render inside Twenty's UI (side panel, widgets, command menu) |-| **Skills & Agents** | AI capabilities — reusable instructions and autonomous assistants |-| **Views & Navigation** | Pre-configured list views and sidebar menu items |+| Entity | What it does |+| ---------------------- | --------------------------------------------------------------------------------------------- |+| **Objects & Fields** | New data tables and fields on existing objects — same treatment as built-in ones |+| **Logic Functions** | Server-side TypeScript triggered by HTTP routes, cron schedules, or database events |+| **Front Components** | Sandboxed React components that render inside Twenty's UI (side panel, widgets, command menu) |+| **Skills & Agents** | AI capabilities — reusable instructions and autonomous assistants |+| **Views & Navigation** | Pre-configured list views and sidebar menu items |Everything is detected via AST analysis at build time — no config files, no registration boilerplate. Put a `export default defineObject(...)` in any `.ts` file and the SDK picks it up.@@ -35,8 +34,12 @@ Everything is detected via AST analysis at build time — no config files, no re## The developer experience-You write your app as a TypeScript project on your machine. The CLI watches your source files and live-syncs them to a running Twenty server — edit a file, see the change in the UI within a second. The typed API client regenerates automatically when the schema changes. When you're ready, `yarn twenty app:publish --private` pushes to a production server, or `yarn twenty app:publish` lists your app on npm and the Twenty marketplace.+You write your app as a TypeScript project on your machine. The CLI watches your source files and live-syncs them to a running Twenty server — edit a file, see the change in the UI within a second. The typed API client regenerates automatically when the schema changes. When you're ready, `twenty app publish --private` pushes to a production server, or `twenty app publish` lists your app on npm and the Twenty marketplace.-<Card title="Build your first app" icon="arrow-right" href="/developers/extend/apps/getting-started/quick-start">+<Card+ title="Build your first app"+ icon="arrow-right"+ href="/developers/extend/apps/getting-started/quick-start"+>Three-phase walkthrough — scaffold, run a local server, sync your changes.</Card>diff --git a/packages/twenty-sdk/README.md b/packages/twenty-sdk/README.mdindex a35ec10c1df..90152a512d1 100644--- a/packages/twenty-sdk/README.md+++ b/packages/twenty-sdk/README.md@@ -14,7 +14,7 @@The application authoring and runtime SDK for [Twenty CRM](https://twenty.com).-Use `twenty-sdk/define` to declare app entities, `twenty-sdk/front-component` for UI helpers, and `twenty-sdk/logic-function` for server-side helpers. The `billing` and `utils` exports remain available.+Use `twenty-sdk/define` to declare app entities, `twenty-sdk/front-component` for UI helpers, and `twenty-sdk/logic-function` for server-side helpers. The SDK also provides `billing`, `utils`, and renderer integration exports.## Quick start@@ -31,25 +31,6 @@ twenty app dev --createKeep `twenty-sdk` installed in each app. The global `twenty` package owns scaffolding, builds, authentication, sync, and publishing.-## Migration from the SDK CLI--The SDK no longer ships the `twenty` binary, `twenty-sdk/cli`, `twenty-sdk/build`, or the build descriptor. `create-twenty-app` is retired and prints migration instructions.--| Previous entry point | Replacement |-| ------------------------------------- | -------------------------------------- |-| `create-twenty-app` | `twenty app init`, then `yarn install` |-| `yarn twenty dev` | `twenty app dev` |-| `yarn twenty apply` / `plan` / `pull` | `twenty app apply` / `plan` / `pull` |-| `yarn twenty dev:build` | `twenty app build` |-| `yarn twenty dev:typecheck` | `twenty app typecheck` |-| `yarn twenty dev:generate-client` | `twenty app generate-client` |-| `yarn twenty app:publish` | `twenty app publish` |-| Programmatic CLI/build imports | Spawn the standalone CLI with `--json` |--Use `twenty auth login` to configure a remote. For scripts, set `TWENTY_API_URL` and `TWENTY_API_KEY`. The standalone CLI does not use the SDK's `config.test.json` file. Run `twenty doctor` if an older SDK binary still shadows your global CLI.--The SDK's renderer integration exports remain available for the Twenty platform.-## Documentation- [CLI reference](https://docs.twenty.com/developers/extend/apps/operations/cli)diff --git a/packages/twenty-sdk/src/sdk/define/connection-providers/__tests__/define-connection-provider.spec.ts b/packages/twenty-sdk/src/sdk/define/connection-providers/__tests__/define-connection-provider.spec.tsindex a2574de727f..83fea8f0627 100644--- a/packages/twenty-sdk/src/sdk/define/connection-providers/__tests__/define-connection-provider.spec.ts+++ b/packages/twenty-sdk/src/sdk/define/connection-providers/__tests__/define-connection-provider.spec.ts@@ -37,9 +37,6 @@ describe('defineConnectionProvider', () => {});it('rejects a non-UUID universalIdentifier', () => {- // Catches the most common mistake: copy-pasting a slug or generated id- // string instead of running `uuidgen`. Server-side throws too — this- // arm of the check just shifts the error to `twenty deploy` time.const result = defineConnectionProvider({...baseValidConfig,universalIdentifier: 'linear-provider',diff --git a/packages/twenty-server/scripts/build-seed-front-components.ts b/packages/twenty-server/scripts/build-seed-front-components.tsindex 5893ba7ac95..cbeaaac80ad 100644--- a/packages/twenty-server/scripts/build-seed-front-components.ts+++ b/packages/twenty-server/scripts/build-seed-front-components.ts@@ -1,6 +1,3 @@-// Script to build seed front component .tsx files into .mjs using the same-// esbuild pipeline as the twenty-sdk CLI (Remote DOM + JSX wrapping).-//// Usage: npx tsx scripts/build-seed-front-components.tsimport * as esbuild from 'esbuild';diff --git a/packages/twenty-server/src/engine/core-modules/application/application-manifest/utils/__tests__/assert-flat-application-is-exportable.util.spec.ts b/packages/twenty-server/src/engine/core-modules/application/application-manifest/utils/__tests__/assert-flat-application-is-exportable.util.spec.tsindex 5a468113ecf..763c3183aa3 100644--- a/packages/twenty-server/src/engine/core-modules/application/application-manifest/utils/__tests__/assert-flat-application-is-exportable.util.spec.ts+++ b/packages/twenty-server/src/engine/core-modules/application/application-manifest/utils/__tests__/assert-flat-application-is-exportable.util.spec.ts@@ -51,13 +51,13 @@ describe('assertFlatApplicationIsExportable', () => {);});- it('should point a packaged application at app:install', () => {+ it('should point a packaged application at twenty app install', () => {expect(() =>assertFlatApplicationIsExportable(buildFlatApplication({sourceType: ApplicationRegistrationSourceType.NPM,}),),- ).toThrow(/app:install/);+ ).toThrow(/twenty app install/);});});diff --git a/packages/twenty-server/src/engine/core-modules/application/application-manifest/utils/assert-flat-application-is-exportable.util.ts b/packages/twenty-server/src/engine/core-modules/application/application-manifest/utils/assert-flat-application-is-exportable.util.tsindex b1ac86fdb56..b38fcf19fe3 100644--- a/packages/twenty-server/src/engine/core-modules/application/application-manifest/utils/assert-flat-application-is-exportable.util.ts+++ b/packages/twenty-server/src/engine/core-modules/application/application-manifest/utils/assert-flat-application-is-exportable.util.ts@@ -32,7 +32,7 @@ export const assertFlatApplicationIsExportable = (case ApplicationRegistrationSourceType.NPM:case ApplicationRegistrationSourceType.TARBALL:throw new ApplicationException(- `Application "${flatApplication.name}" was installed from a ${flatApplication.sourceType} package and cannot be exported. Its published version can be reinstalled with app:install.`,+ `Application "${flatApplication.name}" was installed from a ${flatApplication.sourceType} package and cannot be exported. Its published version can be reinstalled with twenty app install.`,ApplicationExceptionCode.APPLICATION_NOT_EXPORTABLE,);case ApplicationRegistrationSourceType.OAUTH_ONLY: