fix: respect isNullable for relation FK scalar in create input type

https://sonarly.com/issue/14908?type=bug

The GraphQL create input for relation FK scalars (like `messageId`) is always generated as nullable, allowing records to be created without required foreign keys. The response serialization then fails because the output type correctly marks `messageId` as non-nullable.

Fix: Removed the `nullable: true` override in `generateSimpleRelationFieldCreateOrUpdateInputType` so the FK scalar field (e.g. `messageId`) respects the actual `isNullable` from field metadata.

Commit `ef003fb929f` ("fix blocklist #18332") intended to make only the **connect relation input** optional (since you provide either FK or connect, not both), but accidentally also made the **FK scalar** always optional by overriding `nullable: true`. This let users create records like MessageParticipant without required foreign keys (messageId), which then crashed on response serialization.

The fix passes `typeOptions` unchanged to `applyTypeOptionsForCreateInput` for the FK scalar. When `isNullable: false` (like `message` → `messageId`), the field correctly becomes `GraphQLNonNull` in the create input. When `isNullable: true` (like `person` → `personId`), it stays optional. The connect relation input (`generateConnectRelationFieldInputType`) is untouched and correctly remains always nullable.

.claude/settings.json

@@ -1,7 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "Bash(git stash:*)"
-    ]
-  }
-}

.dockerignore

@@ -1,5 +1,5 @@
 .git
 .env
-**/node_modules
+node_modules
 .nx/cache
 packages/twenty-server/.env

.github/workflows/ci-ai-catalog-sync.yaml

@@ -1,68 +0,0 @@
-name: AI Catalog Sync
-
-on:
-  schedule:
-    - cron: '0 6 * * *' # Daily at 6 AM UTC
-  workflow_dispatch: # Allow manual trigger
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  sync-catalog:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    env:
-      NODE_OPTIONS: '--max-old-space-size=4096'
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          ref: main
-
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-
-      - name: Build dependencies
-        run: npx nx build twenty-shared
-
-      - name: Run catalog sync
-        run: npx nx run twenty-server:ts-node-no-deps-transpile-only -- ./scripts/ai-sync-models-dev.ts
-
-      - name: Check for changes
-        id: changes
-        run: |
-          if git diff --quiet packages/twenty-server/src/engine/metadata-modules/ai/ai-models/ai-providers.json; then
-            echo "changed=false" >> "$GITHUB_OUTPUT"
-          else
-            echo "changed=true" >> "$GITHUB_OUTPUT"
-          fi
-
-      - name: Create pull request
-        if: steps.changes.outputs.changed == 'true'
-        uses: peter-evans/create-pull-request@v7
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          commit-message: 'chore: sync AI model catalog from models.dev'
-          title: 'chore: sync AI model catalog from models.dev'
-          body: |
-            Automated daily sync of `ai-providers.json` from [models.dev](https://models.dev).
-
-            This PR updates pricing, context windows, and model availability based on the latest data.
-            New models meeting inclusion criteria (tool calling, pricing data, context limits) are added automatically.
-            Deprecated models are detected based on cost-efficiency within the same model family.
-
-            **Please review before merging** — verify no critical models were incorrectly deprecated.
-          branch: chore/ai-catalog-sync
-          base: main
-          labels: ai, automated
-          delete-branch: true
-
-      - name: Trigger automerge
-        if: steps.changes.outputs.changed == 'true'
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.TWENTY_INFRA_TOKEN }}
-          repository: twentyhq/twenty-infra
-          event-type: automated-pr-ready

.github/workflows/ci-create-app-e2e.yaml

@@ -100,7 +100,7 @@ jobs:
           create-twenty-app --version
           mkdir -p /tmp/e2e-test-workspace
           cd /tmp/e2e-test-workspace
-          create-twenty-app test-app --exhaustive --display-name "Test App" --description "E2E test app" --skip-local-instance
+          create-twenty-app test-app --exhaustive --display-name "Test App" --description "E2E test app"
 
       - name: Install scaffolded app dependencies
         run: |
@@ -151,24 +151,22 @@ jobs:
           SEED_API_KEY: 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIyMDIwMjAyMC1lNmI1LTQ2ODAtOGEzMi1iODIwOTczNzE1NmIiLCJ1c2VySWQiOiIyMDIwMjAyMC1lNmI1LTQ2ODAtOGEzMi1iODIwOTczNzE1NmIiLCJ3b3Jrc3BhY2VJZCI6IjIwMjAyMDIwLTFjMjUtNGQwMi1iZjI1LTZhZWNjZjdlYTQxOSIsIndvcmtzcGFjZU1lbWJlcklkIjoiMjAyMDIwMjAtNDYzZi00MzViLTgyOGMtMTA3ZTAwN2EyNzExIiwidXNlcldvcmtzcGFjZUlkIjoiMjAyMDIwMjAtMWU3Yy00M2Q5LWE1ZGItNjg1YjUwNjlkODE2IiwidHlwZSI6IkFDQ0VTUyIsImF1dGhQcm92aWRlciI6InBhc3N3b3JkIiwiaWF0IjoxNzUxMjgxNzA0LCJleHAiOjIwNjY4NTc3MDR9.HMGqCsVlOAPVUBhKSGlD1X86VoHKt4LIUtET3CGIdik'
         run: |
           cd /tmp/e2e-test-workspace/test-app
-          npx --no-install twenty remote add --token $SEED_API_KEY --url http://localhost:3000
+          npx --no-install twenty auth:login --api-key $SEED_API_KEY --api-url http://localhost:3000
 
       - name: Build scaffolded app
         run: |
           cd /tmp/e2e-test-workspace/test-app
-          npx --no-install twenty build
+          npx --no-install twenty app:build
           test -d .twenty/output
 
       - name: Execute hello-world logic function
         run: |
           cd /tmp/e2e-test-workspace/test-app
-          EXEC_OUTPUT=$(npx --no-install twenty exec --functionName hello-world-logic-function)
+          EXEC_OUTPUT=$(npx --no-install twenty function:execute --functionName hello-world-logic-function)
           echo "$EXEC_OUTPUT"
           echo "$EXEC_OUTPUT" | grep -q "Hello, World!"
 
       - name: Run scaffolded app integration test
-        env:
-          TWENTY_API_URL: http://localhost:3000
         run: |
           cd /tmp/e2e-test-workspace/test-app
           yarn test

.github/workflows/ci-front.yaml

@@ -151,40 +151,6 @@ jobs:
   #         npx nyc merge coverage-artifacts ${{ env.PATH_TO_COVERAGE }}/coverage-storybook.json
   #     - name: Checking coverage
   #       run: npx nx storybook:coverage twenty-front --checkCoverage=true --configuration=${{ matrix.storybook_scope }}
-  visual-regression-dispatch:
-    needs: front-sb-build
-    if: github.event_name == 'pull_request'
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    steps:
-      - name: Download storybook build
-        uses: actions/download-artifact@v4
-        with:
-          name: storybook-static
-          path: storybook-static
-      - name: Package storybook
-        run: tar -czf /tmp/storybook-twenty-front.tar.gz -C storybook-static .
-      - name: Upload storybook tarball
-        uses: actions/upload-artifact@v4
-        with:
-          name: storybook-twenty-front-tarball
-          path: /tmp/storybook-twenty-front.tar.gz
-          retention-days: 1
-      - name: Dispatch to ci-privileged
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.CI_PRIVILEGED_DISPATCH_TOKEN }}
-          repository: twentyhq/ci-privileged
-          event-type: visual-regression
-          client-payload: >-
-            {
-              "pr_number": "${{ github.event.pull_request.number }}",
-              "run_id": "${{ github.run_id }}",
-              "repo": "${{ github.repository }}",
-              "project": "twenty-front",
-              "branch": "${{ github.head_ref }}",
-              "commit": "${{ github.event.pull_request.head.sha }}"
-            }
   front-task:
     needs: changed-files-check
     if: needs.changed-files-check.outputs.any_changed == 'true'

.github/workflows/ci-merge-queue.yaml

@@ -10,8 +10,8 @@ permissions:
   contents: read
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
+  group: ${{ github.workflow }}-${{ github.event_name == 'merge_group' && github.event.merge_group.base_ref || github.ref }}
+  cancel-in-progress: ${{ github.event_name != 'merge_group' }}
 
 jobs:
   e2e-test:

.github/workflows/ci-ui.yaml

@@ -1,146 +0,0 @@
-name: CI UI
-
-on:
-  pull_request:
-  merge_group:
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-jobs:
-  changed-files-check:
-    if: github.event_name != 'merge_group'
-    uses: ./.github/workflows/changed-files.yaml
-    with:
-      files: |
-        package.json
-        yarn.lock
-        packages/twenty-ui/**
-        packages/twenty-shared/**
-  ui-task:
-    needs: changed-files-check
-    if: needs.changed-files-check.outputs.any_changed == 'true'
-    timeout-minutes: 30
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        task: [lint, typecheck, test]
-    steps:
-      - name: Cancel Previous Runs
-        uses: styfle/[email protected]
-        with:
-          access_token: ${{ github.token }}
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 10
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Run ${{ matrix.task }}
-        run: npx nx ${{ matrix.task }} twenty-ui
-  ui-sb-build:
-    needs: changed-files-check
-    if: needs.changed-files-check.outputs.any_changed == 'true'
-    timeout-minutes: 30
-    runs-on: ubuntu-latest
-    steps:
-      - name: Cancel Previous Runs
-        uses: styfle/[email protected]
-        with:
-          access_token: ${{ github.token }}
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 10
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Build storybook
-        run: npx nx storybook:build twenty-ui
-      - name: Upload storybook build
-        uses: actions/upload-artifact@v4
-        with:
-          name: storybook-twenty-ui
-          path: packages/twenty-ui/storybook-static
-          retention-days: 1
-  ui-sb-test:
-    timeout-minutes: 30
-    runs-on: ubuntu-latest
-    needs: ui-sb-build
-    env:
-      STORYBOOK_URL: http://localhost:6007
-    steps:
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 10
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Build dependencies
-        run: npx nx build twenty-shared
-      - name: Download storybook build
-        uses: actions/download-artifact@v4
-        with:
-          name: storybook-twenty-ui
-          path: packages/twenty-ui/storybook-static
-      - name: Install Playwright
-        run: |
-          cd packages/twenty-ui
-          npx playwright install
-      - name: Serve storybook & run tests
-        run: |
-          npx http-server packages/twenty-ui/storybook-static --port 6007 --silent &
-          timeout 30 bash -c 'until curl -sf http://localhost:6007 > /dev/null 2>&1; do sleep 1; done'
-          npx nx storybook:test twenty-ui
-  visual-regression-dispatch:
-    needs: ui-sb-build
-    if: github.event_name == 'pull_request'
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    steps:
-      - name: Download storybook build
-        uses: actions/download-artifact@v4
-        with:
-          name: storybook-twenty-ui
-          path: storybook-static
-      - name: Package storybook
-        run: tar -czf /tmp/storybook-twenty-ui.tar.gz -C storybook-static .
-      - name: Upload storybook tarball
-        uses: actions/upload-artifact@v4
-        with:
-          name: storybook-twenty-ui-tarball
-          path: /tmp/storybook-twenty-ui.tar.gz
-          retention-days: 1
-      - name: Dispatch to ci-privileged
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.CI_PRIVILEGED_DISPATCH_TOKEN }}
-          repository: twentyhq/ci-privileged
-          event-type: visual-regression
-          client-payload: >-
-            {
-              "pr_number": "${{ github.event.pull_request.number }}",
-              "run_id": "${{ github.run_id }}",
-              "repo": "${{ github.repository }}",
-              "project": "twenty-ui",
-              "branch": "${{ github.head_ref }}",
-              "commit": "${{ github.event.pull_request.head.sha }}"
-            }
-  ci-ui-status-check:
-    if: always() && !cancelled()
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    needs:
-      [
-        changed-files-check,
-        ui-task,
-        ui-sb-build,
-        ui-sb-test,
-      ]
-    steps:
-      - name: Fail job if any needs failed
-        if: contains(needs.*.result, 'failure')
-        run: exit 1

.github/workflows/docs-i18n-pull.yaml

@@ -150,11 +150,3 @@ jobs:
           fi
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Trigger i18n automerge
-        if: github.event_name != 'pull_request' && steps.check_changes.outputs.changes_detected == 'true'
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.TWENTY_INFRA_TOKEN }}
-          repository: twentyhq/twenty-infra
-          event-type: i18n-pr-ready

.github/workflows/i18n-pull.yaml

@@ -138,11 +138,3 @@ jobs:
           fi
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Trigger i18n automerge
-        if: steps.compile_translations.outputs.changes_detected == 'true'
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.TWENTY_INFRA_TOKEN }}
-          repository: twentyhq/twenty-infra
-          event-type: i18n-pr-ready

.github/workflows/i18n-push.yaml

@@ -102,11 +102,3 @@ jobs:
           fi
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Trigger i18n automerge
-        if: steps.check_extract_changes.outputs.changes_detected == 'true' || steps.check_compile_changes.outputs.changes_detected == 'true'
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.TWENTY_INFRA_TOKEN }}
-          repository: twentyhq/twenty-infra
-          event-type: i18n-pr-ready

.mcp.json

@@ -2,8 +2,8 @@
   "mcpServers": {
     "postgres": {
       "type": "stdio",
-      "command": "bash",
-      "args": ["-c", "source packages/twenty-server/.env && npx -y @modelcontextprotocol/server-postgres \"$PG_DATABASE_URL\""],
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-postgres", "${PG_DATABASE_URL}"],
       "env": {}
     },
     "playwright": {

CLAUDE.md

@@ -80,17 +80,6 @@ npx nx run twenty-server:typeorm migration:generate src/database/typeorm/core/mi
 npx nx run twenty-server:command workspace:sync-metadata
 ```
 
-### Database Inspection (Postgres MCP)
-
-A read-only Postgres MCP server is configured in `.mcp.json`. Use it to:
-- Inspect workspace data, metadata, and object definitions while developing
-- Verify migration results (columns, types, constraints) after running migrations
-- Explore the multi-tenant schema structure (core, metadata, workspace-specific schemas)
-- Debug issues by querying raw data to confirm whether a bug is frontend, backend, or data-level
-- Inspect metadata tables to debug GraphQL schema generation or `workspace:sync-metadata` issues
-
-This server is read-only — for write operations (reset, migrations, sync), use the CLI commands above.
-
 ### GraphQL
 ```bash
 # Generate GraphQL types (run after schema changes)

packages/create-twenty-app/README.md

@@ -25,47 +25,47 @@ See Twenty application documentation https://docs.twenty.com/developers/extend/c
 ## Prerequisites
 
 - Node.js 24+ (recommended) and Yarn 4
-- Docker (for the local Twenty dev server)
+- A Twenty workspace and an API key (create one at https://app.twenty.com/settings/api-webhooks)
 
 ## Quick start
 
 ```bash
-# Scaffold a new app — the CLI will offer to start a local Twenty server
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app
 
-# The scaffolder can automatically:
-# 1. Start a local Twenty server (Docker)
-# 2. Open the browser to log in ([email protected] / [email protected])
-# 3. Authenticate your app via OAuth
+# Get help and list all available commands
+yarn twenty help
 
-# Or do it manually:
-yarn twenty server start          # Start local Twenty server
-yarn twenty remote add --local    # Authenticate via OAuth
+# Authenticate using your API key (you'll be prompted)
+yarn twenty auth:login
+
+# Add a new entity to your application (guided)
+yarn twenty entity:add
 
 # Start dev mode: watches, builds, and syncs local changes to your workspace
-yarn twenty dev
+# (also auto-generates typed CoreApiClient — MetadataApiClient ships pre-built with the SDK — both available via `twenty-sdk/clients`)
+yarn twenty app:dev
 
 # Watch your application's function logs
-yarn twenty logs
+yarn twenty function:logs
 
 # Execute a function with a JSON payload
-yarn twenty exec -n my-function -p '{"key": "value"}'
+yarn twenty function:execute -n my-function -p '{"key": "value"}'
 
 # Execute the pre-install function
-yarn twenty exec --preInstall
+yarn twenty function:execute --preInstall
 
 # Execute the post-install function
-yarn twenty exec --postInstall
+yarn twenty function:execute --postInstall
 
 # Build the app for distribution
-yarn twenty build
+yarn twenty app:build
 
 # Publish the app to npm or directly to a Twenty server
-yarn twenty publish
+yarn twenty app:publish
 
 # Uninstall the application from the current workspace
-yarn twenty uninstall
+yarn twenty app:uninstall
 ```
 
 ## Scaffolding modes
@@ -107,27 +107,13 @@ npx create-twenty-app@latest my-app -m
 - `skills/example-skill.ts` — Example AI agent skill definition
 - `__tests__/app-install.integration-test.ts` — Integration test that builds, installs, and verifies the app (includes `vitest.config.ts`, `tsconfig.spec.json`, and a setup file)
 
-## Local server
-
-The scaffolder can start a local Twenty dev server for you (all-in-one Docker image with PostgreSQL, Redis, server, and worker). You can also manage it manually:
-
-```bash
-yarn twenty server start     # Start (pulls image if needed)
-yarn twenty server status    # Check if it's healthy
-yarn twenty server logs      # Stream logs
-yarn twenty server stop      # Stop (data is preserved)
-yarn twenty server reset     # Wipe all data and start fresh
-```
-
-The server is pre-seeded with a workspace and user (`[email protected]` / `[email protected]`).
-
 ## Next steps
 
 - Run `yarn twenty help` to see all available commands.
-- Use `yarn twenty remote add --local` to authenticate with your Twenty workspace via OAuth.
-- Explore the generated project and add your first entity with `yarn twenty add` (logic functions, front components, objects, roles, views, navigation menu items, skills).
-- Use `yarn twenty dev` while you iterate — it watches, builds, and syncs changes to your workspace in real time.
-- `CoreApiClient` (for workspace data via `/graphql`) is auto-generated by `yarn twenty dev`. `MetadataApiClient` (for workspace configuration and file uploads via `/metadata`) ships pre-built with the SDK. Both are available via `import { CoreApiClient, MetadataApiClient } from 'twenty-sdk/clients'`.
+- Use `yarn twenty auth:login` to authenticate with your Twenty workspace.
+- Explore the generated project and add your first entity with `yarn twenty entity:add` (logic functions, front components, objects, roles, views, navigation menu items, skills).
+- Use `yarn twenty app:dev` while you iterate — it watches, builds, and syncs changes to your workspace in real time.
+- `CoreApiClient` (for workspace data via `/graphql`) is auto-generated by `yarn twenty app:dev`. `MetadataApiClient` (for workspace configuration and file uploads via `/metadata`) ships pre-built with the SDK. Both are available via `import { CoreApiClient, MetadataApiClient } from 'twenty-sdk/clients'`.
 
 ## Build and publish your application
 
@@ -135,19 +121,19 @@ Once your app is ready, build and publish it using the CLI:
 
 ```bash
 # Build the app (output goes to .twenty/output/)
-yarn twenty build
+yarn twenty app:build
 
 # Build and create a tarball (.tgz) for distribution
-yarn twenty build --tarball
+yarn twenty app:build --tarball
 
 # Publish to npm (requires npm login)
-yarn twenty publish
+yarn twenty app:publish
 
 # Publish with a dist-tag (e.g. beta, next)
-yarn twenty publish --tag beta
+yarn twenty app:publish --tag beta
 
-# Deploy directly to a Twenty server (builds, uploads, and installs in one step)
-yarn twenty deploy
+# Publish directly to a Twenty server (builds, uploads, and installs in one step)
+yarn twenty app:publish --server https://app.twenty.com
 ```
 
 ### Publish to the Twenty marketplace
@@ -167,9 +153,8 @@ Our team reviews contributions for quality, security, and reusability before mer
 
 ## Troubleshooting
 
-- Server not starting: check Docker is running (`docker info`), then try `yarn twenty server logs`.
-- Auth not working: make sure you're logged in to Twenty in the browser first, then run `yarn twenty remote add --local`.
-- Types not generated: ensure `yarn twenty dev` is running — it auto-generates the typed client.
+- Auth prompts not appearing: run `yarn twenty auth:login` again and verify the API key permissions.
+- Types not generated: ensure `yarn twenty app:dev` is running — it auto‑generates the typed client.
 
 ## Contributing
 

packages/create-twenty-app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-twenty-app",
-  "version": "0.8.0-canary.1",
+  "version": "0.7.0",
   "description": "Command-line interface to create Twenty application",
   "main": "dist/cli.cjs",
   "bin": "dist/cli.cjs",

packages/create-twenty-app/src/cli.ts

@@ -27,10 +27,6 @@ const program = new Command(packageJson.name)
     '--description <description>',
     'Application description (skips prompt)',
   )
-  .option(
-    '--skip-local-instance',
-    'Skip the local Twenty instance setup prompt',
-  )
   .helpOption('-h, --help', 'Display this help message.')
   .action(
     async (
@@ -41,7 +37,6 @@ const program = new Command(packageJson.name)
         name?: string;
         displayName?: string;
         description?: string;
-        skipLocalInstance?: boolean;
       },
     ) => {
       const modeFlags = [options?.exhaustive, options?.minimal].filter(Boolean);
@@ -77,7 +72,6 @@ const program = new Command(packageJson.name)
         name: options?.name,
         displayName: options?.displayName,
         description: options?.description,
-        skipLocalInstance: options?.skipLocalInstance,
       });
     },
   );

packages/create-twenty-app/src/constants/base-application/README.md

@@ -1,11 +1,62 @@
-This is a [Twenty](https://twenty.com) application bootstrapped with [`create-twenty-app`](https://www.npmjs.com/package/create-twenty-app).
+This is a [Twenty](https://twenty.com) application project bootstrapped with [`create-twenty-app`](https://www.npmjs.com/package/create-twenty-app).
 
 ## Getting Started
 
-Run `yarn twenty help` to list all available commands.
+First, authenticate to your workspace:
+
+```bash
+yarn twenty auth:login
+```
+
+Then, start development mode to sync your app and watch for changes:
+
+```bash
+yarn twenty app:dev
+```
+
+Open your Twenty instance and go to `/settings/applications` section to see the result.
+
+## Available Commands
+
+Run `yarn twenty help` to list all available commands. Common commands:
+
+```bash
+# Authentication
+yarn twenty auth:login     # Authenticate with Twenty
+yarn twenty auth:logout    # Remove credentials
+yarn twenty auth:status    # Check auth status
+yarn twenty auth:switch    # Switch default workspace
+yarn twenty auth:list      # List all configured workspaces
+
+# Application
+yarn twenty app:dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
+yarn twenty entity:add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
+yarn twenty function:logs  # Stream function logs
+yarn twenty function:execute  # Execute a function with JSON payload
+yarn twenty app:uninstall  # Uninstall app from workspace
+```
+
+## Integration Tests
+
+If your project includes the example integration test (`src/__tests__/app-install.integration-test.ts`), you can run it with:
+
+```bash
+# Make sure a Twenty server is running at http://localhost:3000
+yarn test
+```
+
+The test builds and installs the app, then verifies it appears in the applications list. Test configuration (API URL and API key) is defined in `vitest.config.ts`.
+
+## LLMs instructions
+
+Main docs and pitfalls are available in LLMS.md file.
 
 ## Learn More
 
-- [Twenty Apps documentation](https://docs.twenty.com/developers/extend/capabilities/apps)
-- [twenty-sdk CLI reference](https://www.npmjs.com/package/twenty-sdk)
-- [Discord](https://discord.gg/cx5n4Jzs57)
+To learn more about Twenty applications, take a look at the following resources:
+
+- [twenty-sdk](https://www.npmjs.com/package/twenty-sdk) - learn about `twenty-sdk` tool.
+- [Twenty doc](https://docs.twenty.com/) - Twenty's documentation.
+- Join our [Discord](https://discord.gg/cx5n4Jzs57)
+
+You can check out [the Twenty GitHub repository](https://github.com/twentyhq/twenty) - your feedback and contributions are welcome!

packages/create-twenty-app/src/create-app.command.ts

@@ -1,16 +1,11 @@
 import { copyBaseApplicationProject } from '@/utils/app-template';
 import { convertToLabel } from '@/utils/convert-to-label';
 import { install } from '@/utils/install';
-import {
-  type LocalInstanceResult,
-  setupLocalInstance,
-} from '@/utils/setup-local-instance';
 import { tryGitInit } from '@/utils/try-git-init';
 import chalk from 'chalk';
 import * as fs from 'fs-extra';
 import inquirer from 'inquirer';
 import kebabCase from 'lodash.kebabcase';
-import { execSync } from 'node:child_process';
 import * as path from 'path';
 import { isDefined } from 'twenty-shared/utils';
 
@@ -27,7 +22,6 @@ type CreateAppOptions = {
   name?: string;
   displayName?: string;
   description?: string;
-  skipLocalInstance?: boolean;
 };
 
 export class CreateAppCommand {
@@ -46,7 +40,6 @@ export class CreateAppCommand {
 
       await fs.ensureDir(appDirectory);
 
-      console.log(chalk.gray('  Scaffolding project files...'));
       await copyBaseApplicationProject({
         appName,
         appDisplayName,
@@ -55,24 +48,11 @@ export class CreateAppCommand {
         exampleOptions,
       });
 
-      console.log(chalk.gray('  Installing dependencies...'));
       await install(appDirectory);
 
-      console.log(chalk.gray('  Initializing git repository...'));
       await tryGitInit(appDirectory);
 
-      let localResult: LocalInstanceResult = { running: false };
-
-      if (!options.skipLocalInstance) {
-        // Auto-detect a running server first
-        localResult = await setupLocalInstance(appDirectory);
-
-        if (localResult.running && localResult.serverUrl) {
-          await this.connectToLocal(appDirectory, localResult.serverUrl);
-        }
-      }
-
-      this.logSuccess(appDirectory, localResult);
+      this.logSuccess(appDirectory);
     } catch (error) {
       console.error(
         chalk.red('Initialization failed:'),
@@ -193,55 +173,22 @@ export class CreateAppCommand {
     appDirectory: string;
     appName: string;
   }): void {
-    console.log(chalk.blue('Creating Twenty Application'));
-    console.log(chalk.gray(`  Directory: ${appDirectory}`));
-    console.log(chalk.gray(`  Name: ${appName}`));
+    console.log(chalk.blue('🎯 Creating Twenty Application'));
+    console.log(chalk.gray(`📁 Directory: ${appDirectory}`));
+    console.log(chalk.gray(`📝 Name: ${appName}`));
     console.log('');
   }
 
-  private async connectToLocal(
-    appDirectory: string,
-    serverUrl: string,
-  ): Promise<void> {
-    try {
-      execSync(
-        `npx nx run twenty-sdk:start -- remote add ${serverUrl} --as local`,
-        {
-          cwd: appDirectory,
-          stdio: 'inherit',
-        },
-      );
-      console.log(chalk.green('Authenticated with local Twenty instance.'));
-    } catch {
-      console.log(
-        chalk.yellow(
-          'Authentication skipped. Run `npx nx run twenty-sdk:start -- remote add --local` manually.',
-        ),
-      );
-    }
-  }
-
-  private logSuccess(
-    appDirectory: string,
-    localResult: LocalInstanceResult,
-  ): void {
+  private logSuccess(appDirectory: string): void {
     const dirName = appDirectory.split('/').reverse()[0] ?? '';
 
-    console.log(chalk.green('Application created!'));
+    console.log(chalk.green('✅ Application created!'));
     console.log('');
     console.log(chalk.blue('Next steps:'));
     console.log(chalk.gray(`  cd ${dirName}`));
-
-    if (!localResult.running) {
-      console.log(
-        chalk.gray(
-          '  yarn twenty remote add --local  # Authenticate with Twenty',
-        ),
-      );
-    }
-
     console.log(
-      chalk.gray('  yarn twenty dev                  # Start dev mode'),
+      chalk.gray('  yarn twenty auth:login  # Authenticate with Twenty'),
     );
+    console.log(chalk.gray('  yarn twenty app:dev     # Start dev mode'));
   }
 }

packages/create-twenty-app/src/utils/__tests__/test-template.spec.ts

@@ -103,6 +103,7 @@ describe('scaffoldIntegrationTest', () => {
 
       expect(content).toContain('TWENTY_API_KEY');
       expect(content).not.toContain('TWENTY_TEST_API_KEY');
+      expect(content).toContain('TWENTY_API_URL');
       expect(content).toContain('setup-test.ts');
       expect(content).toContain('tsconfig.spec.json');
       expect(content).toContain('integration-test.ts');

packages/create-twenty-app/src/utils/app-template.ts

@@ -474,7 +474,7 @@ const createExampleNavigationMenuItem = async ({
   const universalIdentifier = v4();
 
   const content = `import { defineNavigationMenuItem } from 'twenty-sdk';
-import { EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/example-view';
+  import { EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/example-view';
 
 export default defineNavigationMenuItem({
   universalIdentifier: '${universalIdentifier}',
@@ -482,7 +482,6 @@ export default defineNavigationMenuItem({
   icon: 'IconList',
   color: 'blue',
   position: 0,
-  type: 'VIEW',
   viewUniversalIdentifier: EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER,
 });
 `;
@@ -610,9 +609,8 @@ const createPackageJson = async ({
   const devDependencies: Record<string, string> = {
     typescript: '^5.9.3',
     '@types/node': '^24.7.2',
-    '@types/react': '^19.0.0',
-    react: '^19.0.0',
-    'react-dom': '^19.0.0',
+    '@types/react': '^18.2.0',
+    react: '^18.2.0',
     oxlint: '^0.16.0',
     'twenty-sdk': createTwentyAppPackageJson.version,
   };

packages/create-twenty-app/src/utils/setup-local-instance.ts

@@ -1,101 +0,0 @@
-import chalk from 'chalk';
-import { execSync } from 'node:child_process';
-import { platform } from 'node:os';
-
-const DEFAULT_PORT = 2020;
-
-// Minimal health check — the full implementation lives in twenty-sdk
-const isServerReady = async (port: number): Promise<boolean> => {
-  const controller = new AbortController();
-  const timeoutId = setTimeout(() => controller.abort(), 3000);
-
-  try {
-    const response = await fetch(`http://localhost:${port}/healthz`, {
-      signal: controller.signal,
-    });
-
-    const body = await response.json();
-
-    return body.status === 'ok';
-  } catch {
-    return false;
-  } finally {
-    clearTimeout(timeoutId);
-  }
-};
-
-export type LocalInstanceResult = {
-  running: boolean;
-  serverUrl?: string;
-};
-
-export const setupLocalInstance = async (
-  appDirectory: string,
-): Promise<LocalInstanceResult> => {
-  console.log('');
-  console.log(chalk.blue('Setting up local Twenty instance...'));
-
-  if (await isServerReady(DEFAULT_PORT)) {
-    const serverUrl = `http://localhost:${DEFAULT_PORT}`;
-
-    console.log(chalk.green(`Twenty server detected on ${serverUrl}.`));
-
-    return { running: true, serverUrl };
-  }
-
-  // Delegate to `twenty server start` from the scaffolded app
-  console.log(chalk.gray('Starting local Twenty server...'));
-
-  try {
-    execSync('yarn twenty server start', {
-      cwd: appDirectory,
-      stdio: 'inherit',
-    });
-  } catch {
-    console.log(
-      chalk.yellow(
-        'Failed to start Twenty server. Run `yarn twenty server start` manually.',
-      ),
-    );
-
-    return { running: false };
-  }
-
-  console.log(chalk.gray('Waiting for Twenty to be ready...'));
-
-  const startTime = Date.now();
-  const timeoutMs = 180 * 1000;
-
-  while (Date.now() - startTime < timeoutMs) {
-    if (await isServerReady(DEFAULT_PORT)) {
-      const serverUrl = `http://localhost:${DEFAULT_PORT}`;
-
-      console.log(chalk.green(`Twenty server is running on ${serverUrl}.`));
-      console.log(
-        chalk.gray(
-          'Workspace ready — login with [email protected] / [email protected]',
-        ),
-      );
-
-      const openCommand = platform() === 'darwin' ? 'open' : 'xdg-open';
-
-      try {
-        execSync(`${openCommand} ${serverUrl}`, { stdio: 'ignore' });
-      } catch {
-        // Ignore if browser can't be opened
-      }
-
-      return { running: true, serverUrl };
-    }
-
-    await new Promise((resolve) => setTimeout(resolve, 2000));
-  }
-
-  console.log(
-    chalk.yellow(
-      'Twenty server did not become healthy in time. Check: yarn twenty server logs',
-    ),
-  );
-
-  return { running: false };
-};

packages/create-twenty-app/src/utils/test-template.ts

@@ -45,6 +45,7 @@ export default defineConfig({
     include: ['src/**/*.integration-test.ts'],
     setupFiles: ['src/__tests__/setup-test.ts'],
     env: {
+      TWENTY_API_URL: 'http://localhost:3000',
       TWENTY_API_KEY:
         '${SEED_API_KEY}',
     },
@@ -93,7 +94,7 @@ import * as os from 'os';
 import * as path from 'path';
 import { beforeAll } from 'vitest';
 
-const TWENTY_API_URL = process.env.TWENTY_API_URL ?? 'http://localhost:2020';
+const TWENTY_API_URL = process.env.TWENTY_API_URL ?? 'http://localhost:3000';
 const TEST_CONFIG_DIR = path.join(os.tmpdir(), '.twenty-sdk-test');
 
 const assertServerIsReachable = async () => {
@@ -119,13 +120,12 @@ beforeAll(async () => {
   fs.mkdirSync(TEST_CONFIG_DIR, { recursive: true });
 
   const configFile = {
-    remotes: {
-      local: {
+    profiles: {
+      default: {
         apiUrl: process.env.TWENTY_API_URL,
         apiKey: process.env.TWENTY_API_KEY,
       },
     },
-    defaultRemote: 'local',
   };
 
   fs.writeFileSync(

packages/twenty-apps/community/apollo-enrich/README.md

@@ -5,13 +5,13 @@ This is a [Twenty](https://twenty.com) application project bootstrapped with [`c
 First, authenticate to your workspace:
 
 ```bash
-yarn twenty remote add --local
+yarn twenty auth:login
 ```
 
 Then, start development mode to sync your app and watch for changes:
 
 ```bash
-yarn twenty dev
+yarn twenty app:dev
 ```
 
 Open your Twenty instance and go to `/settings/applications` section to see the result.
@@ -21,19 +21,19 @@ Open your Twenty instance and go to `/settings/applications` section to see the
 Run `yarn twenty help` to list all available commands. Common commands:
 
 ```bash
-# Remotes & Authentication
-yarn twenty remote add --local     # Authenticate with Twenty
-yarn twenty remote status         # Check auth status
-yarn twenty remote switch         # Switch default remote
-yarn twenty remote list           # List all configured remotes
-yarn twenty remote remove <name>  # Remove a remote
+# Authentication
+yarn twenty auth:login     # Authenticate with Twenty
+yarn twenty auth:logout    # Remove credentials
+yarn twenty auth:status    # Check auth status
+yarn twenty auth:switch    # Switch default workspace
+yarn twenty auth:list      # List all configured workspaces
 
 # Application
-yarn twenty dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
-yarn twenty add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
-yarn twenty logs  # Stream function logs
-yarn twenty exec  # Execute a function with JSON payload
-yarn twenty uninstall  # Uninstall app from workspace
+yarn twenty app:dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
+yarn twenty entity:add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
+yarn twenty function:logs  # Stream function logs
+yarn twenty function:execute  # Execute a function with JSON payload
+yarn twenty app:uninstall  # Uninstall app from workspace
 ```
 
 ## LLMs instructions

packages/twenty-apps/fixtures/function-execute-app/package.json

@@ -9,9 +9,9 @@
   },
   "packageManager": "[email protected]",
   "scripts": {
-    "dev": "twenty dev",
-    "exec": "twenty exec",
-    "uninstall": "twenty uninstall",
+    "app:dev": "twenty app:dev",
+    "function:execute": "twenty function:execute",
+    "app:uninstall": "twenty app:uninstall",
     "lint": "oxlint -c .oxlintrc.json .",
     "lint:fix": "oxlint --fix -c .oxlintrc.json ."
   },

packages/twenty-apps/fixtures/invalid-app/package.json

@@ -9,16 +9,16 @@
   },
   "packageManager": "[email protected]",
   "scripts": {
-    "remote:add": "twenty remote add --local",
-    "remote:status": "twenty remote status",
-    "remote:switch": "twenty remote switch",
-    "remote:list": "twenty remote list",
-    "remote:remove": "twenty remote remove",
-    "dev": "twenty dev",
-    "add": "twenty add",
-    "logs": "twenty logs",
-    "exec": "twenty exec",
-    "uninstall": "twenty uninstall",
+    "auth:login": "twenty auth:login",
+    "auth:logout": "twenty auth:logout",
+    "auth:status": "twenty auth:status",
+    "auth:switch": "twenty auth:switch",
+    "auth:list": "twenty auth:list",
+    "app:dev": "twenty app:dev",
+    "entity:add": "twenty entity:add",
+    "function:logs": "twenty function:logs",
+    "function:execute": "twenty function:execute",
+    "app:uninstall": "twenty app:uninstall",
     "help": "twenty help",
     "lint": "oxlint -c .oxlintrc.json .",
     "lint:fix": "oxlint --fix -c .oxlintrc.json ."

packages/twenty-apps/fixtures/minimal-app/package.json

@@ -9,16 +9,16 @@
   },
   "packageManager": "[email protected]",
   "scripts": {
-    "remote:add": "twenty remote add --local",
-    "remote:status": "twenty remote status",
-    "remote:switch": "twenty remote switch",
-    "remote:list": "twenty remote list",
-    "remote:remove": "twenty remote remove",
-    "dev": "twenty dev",
-    "add": "twenty add",
-    "logs": "twenty logs",
-    "exec": "twenty exec",
-    "uninstall": "twenty uninstall",
+    "auth:login": "twenty auth:login",
+    "auth:logout": "twenty auth:logout",
+    "auth:status": "twenty auth:status",
+    "auth:switch": "twenty auth:switch",
+    "auth:list": "twenty auth:list",
+    "app:dev": "twenty app:dev",
+    "entity:add": "twenty entity:add",
+    "function:logs": "twenty function:logs",
+    "function:execute": "twenty function:execute",
+    "app:uninstall": "twenty app:uninstall",
     "help": "twenty help",
     "lint": "oxlint -c .oxlintrc.json .",
     "lint:fix": "oxlint --fix -c .oxlintrc.json ."

packages/twenty-apps/fixtures/postcard-app/package.json

@@ -9,16 +9,16 @@
   },
   "packageManager": "[email protected]",
   "scripts": {
-    "remote:add": "twenty remote add --local",
-    "remote:status": "twenty remote status",
-    "remote:switch": "twenty remote switch",
-    "remote:list": "twenty remote list",
-    "remote:remove": "twenty remote remove",
-    "dev": "twenty dev",
-    "add": "twenty add",
-    "logs": "twenty logs",
-    "exec": "twenty exec",
-    "uninstall": "twenty uninstall",
+    "auth:login": "twenty auth:login",
+    "auth:logout": "twenty auth:logout",
+    "auth:status": "twenty auth:status",
+    "auth:switch": "twenty auth:switch",
+    "auth:list": "twenty auth:list",
+    "app:dev": "twenty app:dev",
+    "entity:add": "twenty entity:add",
+    "function:logs": "twenty function:logs",
+    "function:execute": "twenty function:execute",
+    "app:uninstall": "twenty app:uninstall",
     "help": "twenty help",
     "lint": "oxlint -c .oxlintrc.json .",
     "lint:fix": "oxlint --fix -c .oxlintrc.json ."

packages/twenty-apps/fixtures/postcard-app/src/navigation-menu-items/post-card-recipients.navigation-menu-item.ts

@@ -1,10 +1,8 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
-import { POST_CARD_RECIPIENT_UNIVERSAL_IDENTIFIER } from '../objects/post-card-recipient.object';
+import { ALL_POST_CARD_RECIPIENTS_VIEW_ID } from '../views/all-post-card-recipients.view';
 
 export default defineNavigationMenuItem({
   universalIdentifier: 'c1a2b3c4-0003-4a7b-8c9d-0e1f2a3b4c5d',
   position: 2,
-  type: NavigationMenuItemType.OBJECT,
-  targetObjectUniversalIdentifier: POST_CARD_RECIPIENT_UNIVERSAL_IDENTIFIER,
+  viewUniversalIdentifier: ALL_POST_CARD_RECIPIENTS_VIEW_ID,
 });

packages/twenty-apps/fixtures/postcard-app/src/navigation-menu-items/post-cards.navigation-menu-item.ts

@@ -1,10 +1,8 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
-import { POST_CARD_UNIVERSAL_IDENTIFIER } from '../objects/post-card.object';
+import { ALL_POST_CARDS_VIEW_ID } from '../views/all-post-cards.view';
 
 export default defineNavigationMenuItem({
   universalIdentifier: 'c1a2b3c4-0001-4a7b-8c9d-0e1f2a3b4c5d',
   position: 0,
-  type: NavigationMenuItemType.OBJECT,
-  targetObjectUniversalIdentifier: POST_CARD_UNIVERSAL_IDENTIFIER,
+  viewUniversalIdentifier: ALL_POST_CARDS_VIEW_ID,
 });

packages/twenty-apps/fixtures/postcard-app/src/navigation-menu-items/recipients.navigation-menu-item.ts

@@ -1,10 +1,8 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
-import { RECIPIENT_UNIVERSAL_IDENTIFIER } from '../objects/recipient.object';
+import { ALL_RECIPIENTS_VIEW_ID } from '../views/all-recipients.view';
 
 export default defineNavigationMenuItem({
   universalIdentifier: 'c1a2b3c4-0002-4a7b-8c9d-0e1f2a3b4c5d',
   position: 1,
-  type: NavigationMenuItemType.OBJECT,
-  targetObjectUniversalIdentifier: RECIPIENT_UNIVERSAL_IDENTIFIER,
+  viewUniversalIdentifier: ALL_RECIPIENTS_VIEW_ID,
 });

packages/twenty-apps/hello-world/README.md

@@ -5,13 +5,13 @@ This is a [Twenty](https://twenty.com) application project bootstrapped with [`c
 First, authenticate to your workspace:
 
 ```bash
-yarn twenty remote add --local
+yarn twenty auth:login
 ```
 
 Then, start development mode to sync your app and watch for changes:
 
 ```bash
-yarn twenty dev
+yarn twenty app:dev
 ```
 
 Open your Twenty instance and go to `/settings/applications` section to see the result.
@@ -21,19 +21,19 @@ Open your Twenty instance and go to `/settings/applications` section to see the
 Run `yarn twenty help` to list all available commands. Common commands:
 
 ```bash
-# Remotes & Authentication
-yarn twenty remote add --local     # Authenticate with Twenty
-yarn twenty remote status         # Check auth status
-yarn twenty remote switch         # Switch default remote
-yarn twenty remote list           # List all configured remotes
-yarn twenty remote remove <name>  # Remove a remote
+# Authentication
+yarn twenty auth:login     # Authenticate with Twenty
+yarn twenty auth:logout    # Remove credentials
+yarn twenty auth:status    # Check auth status
+yarn twenty auth:switch    # Switch default workspace
+yarn twenty auth:list      # List all configured workspaces
 
 # Application
-yarn twenty dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
-yarn twenty add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
-yarn twenty logs  # Stream function logs
-yarn twenty exec  # Execute a function with JSON payload
-yarn twenty uninstall  # Uninstall app from workspace
+yarn twenty app:dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
+yarn twenty entity:add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
+yarn twenty function:logs  # Stream function logs
+yarn twenty function:execute  # Execute a function with JSON payload
+yarn twenty app:uninstall  # Uninstall app from workspace
 ```
 
 ## Integration Tests

packages/twenty-apps/hello-world/src/__tests__/setup-test.ts

@@ -29,13 +29,12 @@ beforeAll(async () => {
   fs.mkdirSync(TEST_CONFIG_DIR, { recursive: true });
 
   const configFile = {
-    remotes: {
-      local: {
+    profiles: {
+      default: {
         apiUrl: process.env.TWENTY_API_URL,
         apiKey: process.env.TWENTY_API_KEY,
       },
     },
-    defaultRemote: 'local',
   };
 
   fs.writeFileSync(

packages/twenty-apps/hello-world/src/navigation-menu-items/example-navigation-menu-item.ts

@@ -1,6 +1,5 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
-import { EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/example-view';
+  import { EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/example-view';
 
 export default defineNavigationMenuItem({
   universalIdentifier: '10f90627-e9c2-44b7-9742-bed77e3d1b17',
@@ -8,6 +7,5 @@ export default defineNavigationMenuItem({
   icon: 'IconList',
   color: 'blue',
   position: 0,
-  type: NavigationMenuItemType.VIEW,
   viewUniversalIdentifier: EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER,
 });

packages/twenty-apps/internal/call-recording/README.md

@@ -5,13 +5,13 @@ This is a [Twenty](https://twenty.com) application project bootstrapped with [`c
 First, authenticate to your workspace:
 
 ```bash
-yarn twenty remote add --local
+yarn twenty auth:login
 ```
 
 Then, start development mode to sync your app and watch for changes:
 
 ```bash
-yarn twenty dev
+yarn twenty app:dev
 ```
 
 Open your Twenty instance and go to `/settings/applications` section to see the result.
@@ -21,19 +21,19 @@ Open your Twenty instance and go to `/settings/applications` section to see the
 Run `yarn twenty help` to list all available commands. Common commands:
 
 ```bash
-# Remotes & Authentication
-yarn twenty remote add --local     # Authenticate with Twenty
-yarn twenty remote status         # Check auth status
-yarn twenty remote switch         # Switch default remote
-yarn twenty remote list           # List all configured remotes
-yarn twenty remote remove <name>  # Remove a remote
+# Authentication
+yarn twenty auth:login     # Authenticate with Twenty
+yarn twenty auth:logout    # Remove credentials
+yarn twenty auth:status    # Check auth status
+yarn twenty auth:switch    # Switch default workspace
+yarn twenty auth:list      # List all configured workspaces
 
 # Application
-yarn twenty dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
-yarn twenty add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
-yarn twenty logs  # Stream function logs
-yarn twenty exec  # Execute a function with JSON payload
-yarn twenty uninstall  # Uninstall app from workspace
+yarn twenty app:dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
+yarn twenty entity:add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
+yarn twenty function:logs  # Stream function logs
+yarn twenty function:execute  # Execute a function with JSON payload
+yarn twenty app:uninstall  # Uninstall app from workspace
 ```
 
 ## LLMs instructions

packages/twenty-apps/internal/call-recording/src/logic-functions/end-recording.ts

@@ -236,7 +236,7 @@ const handler = async (event: any) => {
     },
   });
 
-  // TODO: remove `as any` after running `yarn twenty dev` to regenerate the typed client
+  // TODO: remove `as any` after running `yarn twenty app:dev` to regenerate the typed client
   const updateSummary = async (markdown: string) => {
     await client.mutation({
       updateCallRecording: {

packages/twenty-apps/internal/call-recording/src/navigation-menu-items/call-recording-navigation-menu-item.ts

@@ -1,12 +1,10 @@
 import { CALL_RECORDING_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/call-recording-view';
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
 
 export default defineNavigationMenuItem({
   universalIdentifier: '5248a62d-7d2e-43a7-ba45-6e8f61876a71',
   name: 'Call recordings',
   icon: 'IconPhone',
   position: 0,
-  type: NavigationMenuItemType.VIEW,
   viewUniversalIdentifier: CALL_RECORDING_VIEW_UNIVERSAL_IDENTIFIER,
 });

packages/twenty-apps/internal/self-hosting/src/navigation-menu-items/self-host-user-navigation-menu-item.ts

@@ -1,5 +1,4 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
 import { UNIVERSAL_IDENTIFIERS } from 'src/constants/universal-identifiers.constant';
 
 export default defineNavigationMenuItem({
@@ -7,7 +6,6 @@ export default defineNavigationMenuItem({
   name: 'Self host user',
   icon: 'IconList',
   position: 1,
-  type: NavigationMenuItemType.VIEW,
   viewUniversalIdentifier:
     UNIVERSAL_IDENTIFIERS.views.selfHostingUserView.universalIdentifier,
 });

packages/twenty-docker/docker-compose.yml

@@ -38,6 +38,7 @@ services:
 
       # EMAIL_FROM_ADDRESS: ${EMAIL_FROM_ADDRESS:[email protected]}
       # EMAIL_FROM_NAME: ${EMAIL_FROM_NAME:-"John from YourDomain"}
+      # EMAIL_SYSTEM_ADDRESS: ${EMAIL_SYSTEM_ADDRESS:[email protected]}
       # EMAIL_DRIVER: ${EMAIL_DRIVER:-smtp}
       # EMAIL_SMTP_HOST: ${EMAIL_SMTP_HOST:-smtp.gmail.com}
       # EMAIL_SMTP_PORT: ${EMAIL_SMTP_PORT:-465}
@@ -91,6 +92,7 @@ services:
 
       # EMAIL_FROM_ADDRESS: ${EMAIL_FROM_ADDRESS:[email protected]}
       # EMAIL_FROM_NAME: ${EMAIL_FROM_NAME:-"John from YourDomain"}
+      # EMAIL_SYSTEM_ADDRESS: ${EMAIL_SYSTEM_ADDRESS:[email protected]}
       # EMAIL_DRIVER: ${EMAIL_DRIVER:-smtp}
       # EMAIL_SMTP_HOST: ${EMAIL_SMTP_HOST:-smtp.gmail.com}
       # EMAIL_SMTP_PORT: ${EMAIL_SMTP_PORT:-465}

packages/twenty-docker/helm/twenty/templates/_helpers.tpl

@@ -89,15 +89,6 @@ password
 {{- end -}}
 {{- end -}}
 
-{{/* Check if using external secret for redis password */}}
-{{- define "twenty.redis.useExternalSecret" -}}
-{{- if and (not .Values.redisInternal.enabled) .Values.redis.external.secretName .Values.redis.external.passwordKey -}}
-true
-{{- else -}}
-false
-{{- end -}}
-{{- end -}}
-
 {{/* Compose Redis URL */}}
 {{- define "twenty.redisUrl" -}}
 {{- if .Values.server.env.REDIS_URL -}}
@@ -108,14 +99,9 @@ false
 {{- else -}}
 {{- $host := .Values.redis.external.host | default "redis" -}}
 {{- $port := .Values.redis.external.port | default 6379 -}}
-{{- if or (eq (include "twenty.redis.useExternalSecret" .) "true") (.Values.redis.external.password) -}}
-{{- $auth := ":$(REDIS_PASSWORD)@" -}}
-{{- printf "redis://%s%s:%v" $auth $host $port -}}
-{{- else -}}
 {{- printf "redis://%s:%v" $host $port -}}
 {{- end -}}
 {{- end -}}
-{{- end -}}
 
 {{/* Compose Server URL from override, ingress, or service */}}
 {{- define "twenty.serverUrl" -}}

packages/twenty-docker/helm/twenty/templates/deployment-redis-internal.yaml

@@ -46,12 +46,12 @@ spec:
           volumeMounts:
             - name: redis-data
               mountPath: /data
-      volumes:
-        - name: redis-data
-          {{- if .Values.redisInternal.persistence.enabled }}
-          persistentVolumeClaim:
-            claimName: {{ .Values.redisInternal.persistence.existingClaim | default (printf "%s-redis" (include "twenty.fullname" .)) }}
-          {{- else }}
-          emptyDir: {}
-          {{- end }}
+    volumes:
+      - name: redis-data
+        {{- if .Values.redisInternal.persistence.enabled }}
+        persistentVolumeClaim:
+          claimName: {{ .Values.redisInternal.persistence.existingClaim | default (printf "%s-redis" (include "twenty.fullname" .)) }}
+        {{- else }}
+        emptyDir: {}
+        {{- end }}
 {{- end }}

packages/twenty-docker/helm/twenty/templates/deployment-server.yaml

@@ -83,16 +83,16 @@ spec:
               psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d postgres -v db="${DBNAME}" -Atc "SELECT 1 FROM pg_database WHERE datname = :'db'" | grep -q 1 || \
               psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d postgres -v db="${DBNAME}" -c 'CREATE DATABASE :"db";'
               echo "Creating app user ${APP_USER} if it doesn't exist..."
-              psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d postgres -v app_user="${APP_USER}" -v app_password="${APP_PASSWORD}" <<'EOSQL'
-              DO
-              $do$
-              BEGIN
-              IF NOT EXISTS (SELECT 1 FROM pg_roles WHERE rolname = :'app_user') THEN
-              EXECUTE format('CREATE USER %I WITH PASSWORD %L', :'app_user', :'app_password');
-              END IF;
-              END
-              $do$;
-              EOSQL
+                psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d postgres -v app_user="${APP_USER}" -v app_password="${APP_PASSWORD}" <<'EOSQL'
+  DO
+  $do$
+  BEGIN
+    IF NOT EXISTS (SELECT 1 FROM pg_roles WHERE rolname = :'app_user') THEN
+      EXECUTE format('CREATE USER %I WITH PASSWORD %L', :'app_user', :'app_password');
+    END IF;
+  END
+  $do$;
+  EOSQL
               echo "Creating core schema and granting permissions..."
               psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d "${DBNAME}" -v app_user="${APP_USER}" -c 'CREATE SCHEMA IF NOT EXISTS core'
               psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d "${DBNAME}" -v db="${DBNAME}" -v app_user="${APP_USER}" -c 'GRANT ALL PRIVILEGES ON DATABASE :"db" TO :"app_user";'
@@ -106,6 +106,31 @@ spec:
               psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d "${DBNAME}" -v app_user="${APP_USER}" -c 'ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL ON SEQUENCES TO :"app_user";'
               echo "Database ${DBNAME} is ready."
         {{- end }}
+        - name: run-migrations
+          {{- $img := include "twenty.server.image" . }}
+          image: {{ include "twenty.image.repository" $img }}:{{ include "twenty.image.tag" $img }}
+          imagePullPolicy: {{ include "twenty.image.pullPolicy" $img }}
+          command:
+            - sh
+            - -c
+            - >-
+              npx -y typeorm migration:run -d dist/database/typeorm/core/core.datasource
+          env:
+            {{- if eq (include "twenty.db.useExternalSecret" .) "true" }}
+            - name: DB_PASSWORD
+              valueFrom:
+                secretKeyRef:
+                  name: {{ include "twenty.dbPassword.secretName" . }}
+                  key: {{ include "twenty.dbPassword.secretKey" . }}
+            - name: PG_DATABASE_URL
+              value: {{ include "twenty.dbUrl.template" . | quote }}
+            {{- else }}
+            - name: PG_DATABASE_URL
+              valueFrom:
+                secretKeyRef:
+                  name: {{ include "twenty.dbUrl.secretName" . }}
+                  key: url
+            {{- end }}
       containers:
         - name: server
           {{- $img := include "twenty.server.image" . }}
@@ -129,16 +154,6 @@ spec:
                   name: {{ include "twenty.dbUrl.secretName" . }}
                   key: url
             {{- end }}
-            {{- if eq (include "twenty.redis.useExternalSecret" .) "true" }}
-            - name: REDIS_PASSWORD
-              valueFrom:
-                secretKeyRef:
-                  name: {{ .Values.redis.external.secretName }}
-                  key: {{ .Values.redis.external.passwordKey }}
-            {{- else if .Values.redis.external.password }}
-            - name: REDIS_PASSWORD
-              value: {{ .Values.redis.external.password | quote }}
-            {{- end }}
             - name: REDIS_URL
               value: {{ include "twenty.redisUrl" . | quote }}
             - name: SIGN_IN_PREFILLED
@@ -156,10 +171,7 @@ spec:
                   key: accessToken
             {{- $storageEnv := (include "twenty.storageEnv" .) }}
             {{- if $storageEnv }}
-            {{- $storageEnv | nindent 12 }}
-            {{- end }}
-            {{- with .Values.server.extraEnv }}
-            {{- toYaml . | nindent 12 }}
+            {{ $storageEnv | nindent 12 }}
             {{- end }}
           ports:
             - name: http-tcp

packages/twenty-docker/helm/twenty/templates/deployment-worker.yaml

@@ -67,16 +67,6 @@ spec:
                   name: {{ include "twenty.dbUrl.secretName" . }}
                   key: url
             {{- end }}
-            {{- if eq (include "twenty.redis.useExternalSecret" .) "true" }}
-            - name: REDIS_PASSWORD
-              valueFrom:
-                secretKeyRef:
-                  name: {{ .Values.redis.external.secretName }}
-                  key: {{ .Values.redis.external.passwordKey }}
-            {{- else if .Values.redis.external.password }}
-            - name: REDIS_PASSWORD
-              value: {{ .Values.redis.external.password | quote }}
-            {{- end }}
             - name: REDIS_URL
               value: {{ include "twenty.redisUrl" . | quote }}
             - name: STORAGE_TYPE
@@ -86,12 +76,9 @@ spec:
                 secretKeyRef:
                   name: {{ include "twenty.secret.tokens.name" . }}
                   key: accessToken
-            {{- with .Values.worker.extraEnv }}
-            {{- toYaml . | nindent 12 }}
-            {{- end }}
             {{- $storageEnv := (include "twenty.storageEnv" .) }}
             {{- if $storageEnv }}
-            {{- $storageEnv | nindent 12 }}
+            {{ $storageEnv | nindent 12 }}
             {{- end }}
           resources:
             {{- toYaml .Values.worker.resources | nindent 12 }}

packages/twenty-docker/helm/twenty/templates/pvc-redis-internal.yaml

@@ -1,20 +0,0 @@
-{{- if and .Values.redisInternal.enabled .Values.redisInternal.persistence.enabled (not .Values.redisInternal.persistence.existingClaim) }}
-apiVersion: v1
-kind: PersistentVolumeClaim
-metadata:
-  name: {{ include "twenty.fullname" . }}-redis
-  namespace: {{ include "twenty.namespace" . }}
-  labels:
-    app.kubernetes.io/name: {{ include "twenty.name" . }}
-    app.kubernetes.io/instance: {{ .Release.Name }}
-    app.kubernetes.io/component: redis
-spec:
-  accessModes:
-{{ toYaml .Values.redisInternal.persistence.accessModes | nindent 4 }}
-  resources:
-    requests:
-      storage: {{ .Values.redisInternal.persistence.size }}
-  {{- if .Values.redisInternal.persistence.storageClass }}
-  storageClassName: {{ .Values.redisInternal.persistence.storageClass }}
-  {{- end }}
-{{- end }}

packages/twenty-docker/helm/twenty/tests/env_mapping_test.yaml

@@ -1,58 +0,0 @@
-suite: env mapping
-templates:
-  - templates/deployment-server.yaml
-  - templates/deployment-worker.yaml
-release:
-  name: my-twenty
-  namespace: default
-tests:
-  - it: renders server extraEnv with plain value
-    template: templates/deployment-server.yaml
-    set:
-      server.extraEnv:
-        - name: FEATURE_X_ENABLED
-          value: "true"
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: FEATURE_X_ENABLED
-            value: "true"
-
-  - it: renders server extraEnv with valueFrom
-    template: templates/deployment-server.yaml
-    set:
-      server.extraEnv:
-        - name: SMTP_PASSWORD
-          valueFrom:
-            secretKeyRef:
-              name: smtp-creds
-              key: password
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: SMTP_PASSWORD
-            valueFrom:
-              secretKeyRef:
-                name: smtp-creds
-                key: password
-
-  - it: renders worker extraEnv with valueFrom
-    template: templates/deployment-worker.yaml
-    set:
-      worker.extraEnv:
-        - name: CUSTOM_SECRET
-          valueFrom:
-            secretKeyRef:
-              name: my-secret
-              key: custom
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: CUSTOM_SECRET
-            valueFrom:
-              secretKeyRef:
-                name: my-secret
-                key: custom

packages/twenty-docker/helm/twenty/tests/redis_auth_test.yaml

@@ -1,89 +0,0 @@
-suite: redis external authentication
-templates:
-  - templates/deployment-server.yaml
-  - templates/deployment-worker.yaml
-release:
-  name: my-twenty
-  namespace: default
-tests:
-  - it: injects REDIS_PASSWORD from external secret into server
-    template: templates/deployment-server.yaml
-    set:
-      redisInternal.enabled: false
-      redis.external.host: redis.example.com
-      redis.external.secretName: redis-creds
-      redis.external.passwordKey: password
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-            valueFrom:
-              secretKeyRef:
-                name: redis-creds
-                key: password
-
-  - it: injects REDIS_PASSWORD from external secret into worker
-    template: templates/deployment-worker.yaml
-    set:
-      redisInternal.enabled: false
-      redis.external.host: redis.example.com
-      redis.external.secretName: redis-creds
-      redis.external.passwordKey: password
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-            valueFrom:
-              secretKeyRef:
-                name: redis-creds
-                key: password
-
-  - it: injects plaintext REDIS_PASSWORD when password set directly in server
-    template: templates/deployment-server.yaml
-    set:
-      redisInternal.enabled: false
-      redis.external.host: redis.example.com
-      redis.external.password: "s3cr3t"
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-            value: "s3cr3t"
-
-  - it: injects plaintext REDIS_PASSWORD when password set directly in worker
-    template: templates/deployment-worker.yaml
-    set:
-      redisInternal.enabled: false
-      redis.external.host: redis.example.com
-      redis.external.password: "s3cr3t"
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-            value: "s3cr3t"
-
-  - it: does not inject REDIS_PASSWORD into server when using internal redis
-    template: templates/deployment-server.yaml
-    set:
-      redisInternal.enabled: true
-    asserts:
-      - notContains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-          any: true
-
-  - it: does not inject REDIS_PASSWORD into worker when using internal redis
-    template: templates/deployment-worker.yaml
-    set:
-      redisInternal.enabled: true
-    asserts:
-      - notContains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-          any: true

packages/twenty-docker/helm/twenty/tests/schema_permissions_test.yaml

@@ -105,3 +105,18 @@ tests:
           path: spec.template.spec.initContainers[?(@.name=="ensure-database-exists")].command[2]
           pattern: ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL ON SEQUENCES
 
+  # TypeORM Migration Tests
+  # ======================
+  # TypeORM migrations are configured to use the core.datasource which targets the
+  # 'core' schema. This ensures the _typeorm_migrations table and all application
+  # tables use the dedicated core schema.
+
+  - it: migrations run against core datasource
+    template: templates/deployment-server.yaml
+    set:
+      db.enabled: true
+    asserts:
+      - matchRegex:
+          path: spec.template.spec.initContainers[?(@.name=="run-migrations")].command[2]
+          pattern: core\.datasource
+

packages/twenty-docker/helm/twenty/tests/server_url_test.yaml

@@ -19,7 +19,7 @@ tests:
             - crm.example.com
     asserts:
       - equal:
-          path: spec.template.spec.containers[0].env[?(@.name=="SERVER_URL")].value
+          path: spec.template.spec.containers[0].env[0].value
           value: "https://crm.example.com:443"
   - it: falls back to service when ingress disabled
     set:
@@ -28,7 +28,7 @@ tests:
       server.env.SERVER_URL: ""
     asserts:
       - matchRegex:
-          path: spec.template.spec.containers[0].env[?(@.name=="SERVER_URL")].value
+          path: spec.template.spec.containers[0].env[0].value
           pattern: ^http://my-twenty-twenty-server\.default\.svc\.cluster\.local:3000$
 ---
 suite: ingress configuration
@@ -66,7 +66,6 @@ tests:
     set:
       server.ingress.acme: true
     asserts:
-      - isSubset:
-          path: metadata.annotations
-          content:
-            cert-manager.io/cluster-issuer: letsencrypt-prod
+      - equal:
+          path: metadata.annotations[cert-manager.io/cluster-issuer]
+          value: letsencrypt-prod

packages/twenty-docker/helm/twenty/values.schema.json

@@ -61,27 +61,12 @@
             "EMAIL_SMTP_NO_TLS": { "type": "boolean" },
             "EMAIL_FROM_ADDRESS": { "type": "string" },
             "EMAIL_FROM_NAME": { "type": "string" },
+            "EMAIL_SYSTEM_ADDRESS": { "type": "string" },
             "IS_EMAIL_VERIFICATION_REQUIRED": { "type": "boolean" },
             "EMAIL_VERIFICATION_TOKEN_EXPIRES_IN": { "type": "string" },
             "PASSWORD_RESET_TOKEN_EXPIRES_IN": { "type": "string" }
           }
         },
-        "extraEnv": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "name": { "type": "string" },
-              "value": { "type": "string" },
-              "valueFrom": { "type": "object" }
-            },
-            "required": ["name"],
-            "oneOf": [
-              { "required": ["value"] },
-              { "required": ["valueFrom"] }
-            ]
-          }
-        },
         "service": {
           "type": "object",
           "properties": {
@@ -157,22 +142,6 @@
             "STORAGE_TYPE": { "type": "string" },
             "DISABLE_DB_MIGRATIONS": { "type": "string" }
           }
-        },
-        "extraEnv": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "name": { "type": "string" },
-              "value": { "type": "string" },
-              "valueFrom": { "type": "object" }
-            },
-            "required": ["name"],
-            "oneOf": [
-              { "required": ["value"] },
-              { "required": ["valueFrom"] }
-            ]
-          }
         }
       }
     },

packages/twenty-docker/helm/twenty/values.yaml

@@ -52,14 +52,6 @@ server:
     SIGN_IN_PREFILLED: "false"
     ACCESS_TOKEN_EXPIRES_IN: "7d"
     LOGIN_TOKEN_EXPIRES_IN: "1h"
-  extraEnv: []
-  # - name: EMAIL_DRIVER
-  #   value: smtp
-  # - name: SMTP_PASSWORD
-  #   valueFrom:
-  #     secretKeyRef:
-  #       name: smtp-creds
-  #       key: password
 
   service:
     type: ClusterIP
@@ -113,8 +105,6 @@ worker:
       cpu: 1000m
       memory: 2048Mi
 
-  extraEnv: []
-
 # PostgreSQL
 db:
   enabled: true
@@ -184,6 +174,3 @@ redis:
   external:
     host: ""
     port: 6379
-    password: ""
-    secretName: ""
-    passwordKey: ""

packages/twenty-docker/twenty-app-dev/Dockerfile

@@ -1,130 +0,0 @@
-ARG APP_VERSION
-
-# === Stage 1: Common dependencies ===
-FROM node:22-alpine AS common-deps
-
-WORKDIR /app
-
-COPY ./package.json ./yarn.lock ./.yarnrc.yml ./tsconfig.base.json ./nx.json /app/
-COPY ./.yarn/releases /app/.yarn/releases
-COPY ./.yarn/patches /app/.yarn/patches
-
-COPY ./packages/twenty-emails/package.json /app/packages/twenty-emails/
-COPY ./packages/twenty-server/package.json /app/packages/twenty-server/
-COPY ./packages/twenty-server/patches /app/packages/twenty-server/patches
-COPY ./packages/twenty-ui/package.json /app/packages/twenty-ui/
-COPY ./packages/twenty-shared/package.json /app/packages/twenty-shared/
-COPY ./packages/twenty-front/package.json /app/packages/twenty-front/
-COPY ./packages/twenty-sdk/package.json /app/packages/twenty-sdk/
-
-RUN yarn && yarn cache clean && npx nx reset
-
-# === Stage 2: Build server from source ===
-FROM common-deps AS twenty-server-build
-
-COPY ./packages/twenty-emails /app/packages/twenty-emails
-COPY ./packages/twenty-shared /app/packages/twenty-shared
-COPY ./packages/twenty-ui /app/packages/twenty-ui
-COPY ./packages/twenty-sdk /app/packages/twenty-sdk
-COPY ./packages/twenty-server /app/packages/twenty-server
-
-RUN npx nx run twenty-server:build
-RUN yarn workspaces focus --production twenty-emails twenty-shared twenty-sdk twenty-server
-
-# === Stage 3: Build frontend from source ===
-# Requires ~10GB Docker memory. To skip, pre-build on host first:
-#   npx nx build twenty-front
-# The COPY below will pick up packages/twenty-front/build/ if it exists.
-FROM common-deps AS twenty-front-build
-COPY --from=twenty-server-build /app/package.json /tmp/.build-sentinel
-
-COPY ./packages/twenty-front /app/packages/twenty-front
-COPY ./packages/twenty-ui /app/packages/twenty-ui
-COPY ./packages/twenty-shared /app/packages/twenty-shared
-COPY ./packages/twenty-sdk /app/packages/twenty-sdk
-RUN if [ -d /app/packages/twenty-front/build ]; then \
-      echo "Using pre-built frontend from host"; \
-    else \
-      NODE_OPTIONS="--max-old-space-size=8192" npx nx build twenty-front; \
-    fi
-
-# === Stage 4: s6-overlay ===
-FROM alpine:3.20 AS s6-fetch
-ARG S6_OVERLAY_VERSION=3.2.0.2
-ARG TARGETARCH
-RUN if [ "$TARGETARCH" = "arm64" ]; then echo "aarch64" > /tmp/s6arch; \
-    else echo "x86_64" > /tmp/s6arch; fi
-RUN S6_ARCH=$(cat /tmp/s6arch) && \
-    wget -O /tmp/s6-overlay-noarch.tar.xz \
-      "https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz" && \
-    wget -O /tmp/s6-overlay-noarch.tar.xz.sha256 \
-      "https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz.sha256" && \
-    wget -O /tmp/s6-overlay-arch.tar.xz \
-      "https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-${S6_ARCH}.tar.xz" && \
-    wget -O /tmp/s6-overlay-arch.tar.xz.sha256 \
-      "https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-${S6_ARCH}.tar.xz.sha256" && \
-    cd /tmp && \
-    NOARCH_SUM=$(awk '{print $1}' s6-overlay-noarch.tar.xz.sha256) && \
-    ARCH_SUM=$(awk '{print $1}' s6-overlay-arch.tar.xz.sha256) && \
-    echo "$NOARCH_SUM  s6-overlay-noarch.tar.xz" | sha256sum -c - && \
-    echo "$ARCH_SUM  s6-overlay-arch.tar.xz" | sha256sum -c -
-
-# === Stage 5: Final all-in-one image ===
-FROM node:22-alpine
-
-# s6-overlay
-COPY --from=s6-fetch /tmp/s6-overlay-noarch.tar.xz /tmp/
-COPY --from=s6-fetch /tmp/s6-overlay-arch.tar.xz /tmp/
-RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz \
- && tar -C / -Jxpf /tmp/s6-overlay-arch.tar.xz \
- && rm /tmp/s6-overlay-*.tar.xz
-
-# Infrastructure: Postgres, Redis, and utilities
-RUN apk add --no-cache \
-    postgresql16 postgresql16-contrib \
-    redis \
-    curl jq su-exec
-
-# tsx for database setup scripts
-RUN npm install -g tsx
-
-# Twenty application (both server and frontend built from source)
-COPY --from=twenty-server-build /app /app
-COPY --from=twenty-front-build /app/packages/twenty-front/build /app/packages/twenty-server/dist/front
-
-# s6 service definitions
-COPY packages/twenty-docker/twenty-app-dev/rootfs/ /
-
-# Data directories
-RUN mkdir -p /data/postgres /data/redis /app/.local-storage \
- && chown -R postgres:postgres /data/postgres \
- && chown 1000:1000 /data/redis /app/.local-storage
-
-ARG REACT_APP_SERVER_BASE_URL
-ARG APP_VERSION=0.0.0
-
-# Tell s6-overlay to preserve container environment variables
-ENV S6_KEEP_ENV=1
-
-# Environment defaults
-ENV PG_DATABASE_URL=postgres://twenty:twenty@localhost:5432/default \
-    SERVER_URL=http://localhost:2020 \
-    REDIS_URL=redis://localhost:6379 \
-    STORAGE_TYPE=local \
-    APP_SECRET=twenty-app-dev-secret-not-for-production \
-    REACT_APP_SERVER_BASE_URL=$REACT_APP_SERVER_BASE_URL \
-    APP_VERSION=$APP_VERSION \
-    NODE_ENV=development \
-    NODE_PORT=3000 \
-    DISABLE_DB_MIGRATIONS=true \
-    DISABLE_CRON_JOBS_REGISTRATION=true \
-    IS_BILLING_ENABLED=false \
-    SIGN_IN_PREFILLED=true
-
-EXPOSE 3000
-VOLUME ["/data/postgres", "/app/.local-storage"]
-
-LABEL org.opencontainers.image.source=https://github.com/twentyhq/twenty
-LABEL org.opencontainers.image.description="All-in-one Twenty image for local development and SDK usage. Includes PostgreSQL, Redis, server, and worker."
-
-ENTRYPOINT ["/init"]

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/init-db/type

@@ -1 +0,0 @@
-oneshot

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/init-db/up

@@ -1 +0,0 @@
-/bin/sh /etc/s6-overlay/scripts/init-db.sh

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/postgres/run

@@ -1,13 +0,0 @@
-#!/bin/sh
-# Initialize PostgreSQL data directory if empty
-if [ ! -f /data/postgres/PG_VERSION ]; then
-  echo "Initializing PostgreSQL data directory..."
-  su-exec postgres initdb -D /data/postgres --auth=trust --encoding=UTF8
-  # Allow local connections without password
-  echo "host all all 127.0.0.1/32 trust" >> /data/postgres/pg_hba.conf
-  echo "host all all ::1/128 trust" >> /data/postgres/pg_hba.conf
-fi
-
-exec su-exec postgres postgres -D /data/postgres \
-  -c listen_addresses=localhost \
-  -c unix_socket_directories=/tmp

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/postgres/type

@@ -1 +0,0 @@
-longrun

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/redis/run

@@ -1,6 +0,0 @@
-#!/bin/sh
-exec redis-server \
-  --dir /data/redis \
-  --maxmemory-policy noeviction \
-  --bind 127.0.0.1 \
-  --protected-mode yes

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/redis/type

@@ -1 +0,0 @@
-longrun

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/twenty-server/run

@@ -1,3 +0,0 @@
-#!/bin/sh
-cd /app/packages/twenty-server
-exec yarn start:prod

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/twenty-server/type

@@ -1 +0,0 @@
-longrun

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/twenty-worker/run

@@ -1,3 +0,0 @@
-#!/bin/sh
-cd /app/packages/twenty-server
-exec yarn worker:prod

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/s6-rc.d/twenty-worker/type

@@ -1 +0,0 @@
-longrun

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/scripts/init-db.sh

@@ -1,56 +0,0 @@
-#!/bin/sh
-set -e
-
-# Wait for PostgreSQL to be ready (timeout after 60s)
-echo "Waiting for PostgreSQL..."
-TRIES=0
-until su-exec postgres pg_isready -h localhost; do
-  TRIES=$((TRIES + 1))
-  if [ "$TRIES" -ge 120 ]; then
-    echo "ERROR: PostgreSQL did not become ready within 60s"
-    exit 1
-  fi
-  sleep 0.5
-done
-echo "PostgreSQL is ready."
-
-# Create role if it doesn't exist
-su-exec postgres psql -h localhost -tc \
-  "SELECT 1 FROM pg_roles WHERE rolname='twenty'" | grep -q 1 \
-  || su-exec postgres psql -h localhost -c "CREATE ROLE twenty WITH LOGIN PASSWORD 'twenty' SUPERUSER"
-
-# Create database if it doesn't exist
-su-exec postgres psql -h localhost -tc \
-  "SELECT 1 FROM pg_database WHERE datname='default'" | grep -q 1 \
-  || su-exec postgres createdb -h localhost -O twenty default
-
-# Run Twenty database setup and migrations
-cd /app/packages/twenty-server
-
-has_schema=$(PGPASSWORD=twenty psql -h localhost -U twenty -d default -tAc \
-  "SELECT EXISTS (SELECT 1 FROM information_schema.schemata WHERE schema_name = 'core')")
-
-if [ "$has_schema" = "f" ]; then
-  echo "Database appears to be empty, running initial setup..."
-  NODE_OPTIONS="--max-old-space-size=1500" tsx ./scripts/setup-db.ts
-fi
-
-# Always run migrations (idempotent — skips already-applied ones)
-yarn database:migrate:prod
-
-yarn command:prod cache:flush
-yarn command:prod upgrade
-yarn command:prod cache:flush
-
-# Only seed on first boot — check if the dev workspace already exists
-has_workspace=$(PGPASSWORD=twenty psql -h localhost -U twenty -d default -tAc \
-  "SELECT EXISTS (SELECT 1 FROM core.workspace WHERE id = '20202020-1c25-4d02-bf25-6aeccf7ea419')")
-
-if [ "$has_workspace" = "f" ]; then
-  echo "Seeding app dev data..."
-  yarn command:prod workspace:seed:dev --light || true
-else
-  echo "Dev workspace already seeded, skipping."
-fi
-
-echo "Database initialization complete."

packages/twenty-docker/twenty/Dockerfile

@@ -30,11 +30,6 @@ COPY ./packages/twenty-ui /app/packages/twenty-ui
 COPY ./packages/twenty-sdk /app/packages/twenty-sdk
 COPY ./packages/twenty-server /app/packages/twenty-server
 
-RUN npx nx run twenty-server:lingui:extract && \
-    npx nx run twenty-server:lingui:compile && \
-    npx nx run twenty-emails:lingui:extract && \
-    npx nx run twenty-emails:lingui:compile
-
 RUN npx nx run twenty-server:build
 
 RUN yarn workspaces focus --production twenty-emails twenty-shared twenty-sdk twenty-server
@@ -48,8 +43,6 @@ COPY ./packages/twenty-front /app/packages/twenty-front
 COPY ./packages/twenty-ui /app/packages/twenty-ui
 COPY ./packages/twenty-shared /app/packages/twenty-shared
 COPY ./packages/twenty-sdk /app/packages/twenty-sdk
-RUN npx nx run twenty-front:lingui:extract && \
-    npx nx run twenty-front:lingui:compile
 RUN npx nx build twenty-front
 
 

packages/twenty-docs/developers/extend/capabilities/apps.mdx

@@ -20,51 +20,19 @@ Apps let you build and manage Twenty customizations **as code**. Instead of conf
 ## Prerequisites
 
 - Node.js 24+ and Yarn 4
-- Docker (for the local Twenty dev server)
+- A Twenty workspace and an API key (create one at https://app.twenty.com/settings/api-webhooks)
 
 ## Getting Started
 
-Create a new app using the official scaffolder. It can automatically start a local Twenty instance for you:
+Create a new app using the official scaffolder, then authenticate and start developing:
 
 ```bash filename="Terminal"
-# Scaffold a new app — the CLI will offer to start a local Twenty server
+# Scaffold a new app (includes all examples by default)
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app
 
 # Start dev mode: automatically syncs local changes to your workspace
-yarn twenty dev
-```
-
-### Local Server Management
-
-The SDK includes commands to manage a local Twenty dev server (all-in-one Docker image with PostgreSQL, Redis, server, and worker):
-
-```bash filename="Terminal"
-# Start the local server (pulls the image if needed)
-yarn twenty server start
-
-# Check server status
-yarn twenty server status
-
-# Stream server logs
-yarn twenty server logs
-
-# Stop the server
-yarn twenty server stop
-
-# Reset all data and start fresh
-yarn twenty server reset
-```
-
-The local server comes pre-seeded with a workspace and user (`[email protected]` / `[email protected]`), so you can start developing immediately without any manual setup.
-
-### Authentication
-
-Connect your app to the local server using OAuth:
-
-```bash filename="Terminal"
-# Authenticate via OAuth (opens browser)
-yarn twenty remote add --local
+yarn twenty app:dev
 ```
 
 The scaffolder supports two modes for controlling which example files are included:

packages/twenty-docs/developers/self-host/capabilities/troubleshooting.mdx

@@ -157,9 +157,7 @@ plugins: [
 
 Run `UPDATE core."user" SET "canAccessFullAdminPanel" = TRUE WHERE email = '[email protected]';` in database container to get access to admin panel.
 
-#### When running workflow, workflow run fails with "Logic function execution is disabled. Set LOGIC_FUNCTION_TYPE to LOCAL or LAMBDA to enable."
 
-In production, logic functions are disabled by default. Set the `LOGIC_FUNCTION_TYPE` environment variable to `LOCAL` or `LAMBDA` to enable them. This can be configured via environment variables or through the admin panel database variables. See the [Logic Functions setup guide](/developers/self-host/capabilities/setup#logic-functions-available-drivers) for details.
 
 ### 1-click Docker compose
 

packages/twenty-docs/docs.json

@@ -175,8 +175,7 @@
                           "user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -622,8 +621,7 @@
                           "l/fr/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/fr/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/fr/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/fr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/fr/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/fr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -1069,8 +1067,7 @@
                           "l/ar/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/ar/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/ar/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ar/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ar/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ar/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -1516,8 +1513,7 @@
                           "l/cs/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/cs/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/cs/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/cs/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/cs/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/cs/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -1963,8 +1959,7 @@
                           "l/de/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/de/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/de/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/de/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/de/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/de/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -2410,8 +2405,7 @@
                           "l/es/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/es/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/es/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/es/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/es/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/es/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -2857,8 +2851,7 @@
                           "l/it/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/it/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/it/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/it/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/it/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/it/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -3304,8 +3297,7 @@
                           "l/ja/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/ja/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/ja/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ja/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ja/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ja/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -3751,8 +3743,7 @@
                           "l/ko/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/ko/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/ko/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ko/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ko/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ko/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -4198,8 +4189,7 @@
                           "l/pt/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/pt/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/pt/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/pt/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/pt/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/pt/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -4645,8 +4635,7 @@
                           "l/ro/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/ro/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/ro/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ro/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ro/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ro/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -5092,8 +5081,7 @@
                           "l/ru/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/ru/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/ru/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ru/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ru/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ru/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -5539,8 +5527,7 @@
                           "l/tr/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/tr/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/tr/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/tr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/tr/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/tr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -5986,8 +5973,7 @@
                           "l/zh/user-guide/workflows/how-tos/crm-automations/formula-fields",
                           "l/zh/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                           "l/zh/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/zh/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/zh/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/zh/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                         ]
                       },
                       {
@@ -6316,10 +6302,6 @@
       "source": "/developers/extend/capabilities/apps",
       "destination": "/developers/extend/apps/getting-started"
     },
-    {
-      "source": "/developers/extend/mcp",
-      "destination": "/user-guide/ai/capabilities/mcp"
-    },
     {
       "source": "/developers/local-setup",
       "destination": "/developers/contribute/capabilities/local-setup"

packages/twenty-docs/l/ar/developers/extend/capabilities/apps.mdx

@@ -21,51 +21,19 @@ description: أنشئ وأدِر تخصيصات Twenty على هيئة كود.
 ## المتطلبات الأساسية
 
 * Node.js 24+ وYarn 4
-* Docker (لخادم تطوير Twenty المحلي)
+* مساحة عمل Twenty ومفتاح واجهة برمجة التطبيقات (أنشئ واحدًا على https://app.twenty.com/settings/api-webhooks)
 
 ## البدء
 
-أنشئ تطبيقًا جديدًا باستخدام المولّد الرسمي. يمكنه بدء مثيل محلي من Twenty تلقائيًا لك:
+أنشئ تطبيقًا جديدًا باستخدام المُهيئ الرسمي، ثم قم بالمصادقة وابدأ التطوير:
 
 ```bash filename="Terminal"
-# إنشاء تطبيق جديد — ستعرض واجهة سطر الأوامر خيار بدء خادم Twenty محلي
+# إنشاء تطبيق جديد (يتضمن جميع الأمثلة افتراضيًا)
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app
 
 # ابدأ وضع التطوير: يُزامن التغييرات المحلية تلقائيًا مع مساحة العمل الخاصة بك
-yarn twenty dev
-```
-
-### إدارة الخادم المحلي
-
-يتضمن SDK أوامر لإدارة خادم تطوير Twenty محلي (صورة Docker متكاملة تتضمن PostgreSQL وRedis والخادم والعامل):
-
-```bash filename="Terminal"
-# ابدأ الخادم المحلي (يسحب الصورة إذا لزم الأمر)
-yarn twenty server start
-
-# تحقّق من حالة الخادم
-yarn twenty server status
-
-# بثّ سجلات الخادم
-yarn twenty server logs
-
-# أوقف الخادم
-yarn twenty server stop
-
-# أعد ضبط جميع البيانات وابدأ من جديد
-yarn twenty server reset
-```
-
-يأتي الخادم المحلي مهيأً مسبقًا بمساحة عمل ومستخدم (`[email protected]` / `[email protected]`)، بحيث يمكنك البدء في التطوير فورًا دون أي إعداد يدوي.
-
-### المصادقة
-
-وصّل تطبيقك بالخادم المحلي باستخدام OAuth:
-
-```bash filename="Terminal"
-# المصادقة عبر OAuth (يفتح المتصفح)
-yarn twenty remote add --local
+yarn twenty app:dev
 ```
 
 يدعم المُنشئ وضعين للتحكم في ملفات الأمثلة التي سيتم تضمينها:

packages/twenty-docs/l/ar/developers/self-host/capabilities/troubleshooting.mdx

@@ -166,10 +166,6 @@ plugins: [
 
 قم بتشغيل `UPDATE core."user" SET "canAccessFullAdminPanel" = TRUE WHERE email = '[email protected]';` في حاوية قاعدة البيانات للحصول على الوصول إلى لوحة الإدارة.
 
-#### عند تشغيل سير العمل، يفشل تشغيل سير العمل مع الرسالة "تم تعطيل تنفيذ دوال المنطق. عيّن LOGIC_FUNCTION_TYPE إلى LOCAL أو LAMBDA لتمكين ذلك."
-
-في بيئة الإنتاج، يتم تعطيل دوال المنطق افتراضيًا. قم بتعيين متغير البيئة `LOGIC_FUNCTION_TYPE` إلى `LOCAL` أو `LAMBDA` لتمكينها. يمكن تكوين ذلك عبر متغيرات البيئة أو من خلال متغيرات قاعدة البيانات في لوحة الإدارة. راجع [دليل إعداد دوال المنطق](/l/ar/developers/self-host/capabilities/setup#logic-functions-available-drivers) للحصول على التفاصيل.
-
 ### Docker compose بنقرة واحدة
 
 #### غير قادر على تسجيل الدخول

packages/twenty-docs/l/ar/user-guide/ai/capabilities/mcp.mdx

@@ -1,142 +0,0 @@
----
-title: خادم MCP
-description: اربط مساعدي الذكاء الاصطناعي بمساحة عمل Twenty الخاصة بك باستخدام بروتوكول سياق النموذج.
----
-
-<Warning>
-MCP حاليًا في مرحلة **ألفا** وهو متاح فقط في بعض مساحات العمل. قد لا يكون مفعّلًا لمساحة عملك بعد.
-</Warning>
-
-تعرض Twenty خادم [MCP](https://modelcontextprotocol.io/) بحيث تتمكّن مساعدات الذكاء الاصطناعي — Claude Desktop وClaude Code وCursor وChatGPT وغيرها — من قراءة وكتابة بيانات نظام إدارة علاقات العملاء (CRM) لديك باستخدام اللغة الطبيعية.
-
-استخدم **عنوان URL لمساحة العمل** (عنوان URL الذي تستخدمه للوصول إلى Twenty) كنقطة نهاية MCP. على Twenty Cloud، قد يكون عنوان URL لمساحة العمل هو `https://{mycompany}.twenty.com` أو نطاق مخصص. الخادم متاح على:
-
-| البيئة                | نقطة نهاية MCP                                                                           |
-| --------------------- | ---------------------------------------------------------------------------------------- |
-| **السحابة**           | `https://{your-workspace-url}/mcp` (على سبيل المثال: `https://mycompany.twenty.com/mcp`) |
-| **الاستضافة الذاتية** | `https://{your-domain}/mcp`                                                              |
-
-## طرق المصادقة
-
-لديك طريقتان لمصادقة عميل MCP: **OAuth** (مُوصى بها) أو **مفتاح API**.
-
-### الخيار أ — OAuth (مُوصى به)
-
-باستخدام OAuth، يفتح عميل MCP لديك نافذة متصفح لتسجيل الدخول. لا يتم تخزين أي أسرار في ملفات الإعداد، ويتم تحديث الرموز المميِّزة تلقائيًا.
-
-<Note>
-يتطلب OAuth عميل MCP يدعم [مواصفة تفويض MCP](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization). تدعمه Claude Desktop وClaude Code وCursor وChatGPT.
-</Note>
-
-أضِف ما يلي إلى تهيئة عميل MCP لديك، واستبدِل `{your-workspace-url}` بمضيف مساحة العمل لديك (على سبيل المثال: `mycompany.twenty.com`):
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp"
-    }
-  }
-}
-```
-
-هذا كل شيء — لا حاجة إلى مفتاح API. عند اتصال العميل للمرة الأولى، سيفعل ما يلي:
-
-1. اكتشاف بيانات التعريف الخاصة بـ OAuth لدى Twenty عبر `/.well-known/oauth-protected-resource` و`/.well-known/oauth-authorization-server`
-2. تسجيل نفسه كعميل OAuth عبر التسجيل الديناميكي للعميل (RFC 7591)
-3. فتح متصفحك لتفويض الوصول
-4. استلام الرموز المميِّزة والاتصال بخادم MCP
-
-تعيد الاتصالات اللاحقة استخدام الرموز المميِّزة المخزنة وتحدِّثها تلقائيًا.
-
-### الخيار ب — مفتاح API
-
-إذا كان عميل MCP لديك لا يدعم OAuth، أو كنت تفضّل بيانات اعتماد ثابتة، فمرِّر مفتاح API في ترويسة `Authorization`:
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_API_KEY"
-      }
-    }
-  }
-}
-```
-
-<Warning>
-يمنح مفتاح API الخاص بك حق الوصول إلى بيانات مساحة العمل. أبعِده عن أنظمة التحكم في الإصدارات وملفات dotfiles المشتركة.
-</Warning>
-
-لإنشاء مفتاح API، انتقل إلى **Settings > APIs & Webhooks > + Create key**. راجع [واجهات برمجة التطبيقات](/l/ar/developers/extend/api#create-an-api-key) للتفاصيل.
-
-## البدء السريع
-
-### 1. انسخ الإعداد
-
-انتقل إلى **Settings > AI > More > MCP Server** في Twenty. اختر طريقة المصادقة (OAuth أو مفتاح API)، وانسخ مقطع JSON (سيستخدم بالفعل عنوان URL لمساحة العمل لديك)، ثم الصقه في ملف إعدادات عميل MCP لديك.
-
-| العميل             | موقع ملف الإعداد                                                                                                                                    |
-| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Claude Desktop** | `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) أو `%APPDATA%\Claude\claude_desktop_config.json` (Windows)                |
-| **Claude Code**    | `~/.claude.json` (المستخدم) أو `.mcp.json` (المشروع)                                                                                                |
-| **Cursor**         | `.cursor/mcp.json` ضمن مشروعك، أو `~/.cursor/mcp.json` عالميًا                                                                                      |
-| **ChatGPT**        | فعِّل وضع المطوّر في **Settings > Apps & Connectors > Advanced settings**، ثم استخدم **Create** في **Settings > Apps & Connectors** لإضافة خادم MCP |
-
-### 2. الاتصال
-
-أعِد تشغيل عميل MCP لديك (أو أعد تحميل ملف الإعداد). إذا كنت تستخدم OAuth فسيتم توجيهك إلى Twenty لتفويض الوصول. إذا كنت تستخدم مفتاح API فسيكون الاتصال فوريًا.
-
-### 3. ابدأ باستخدامه
-
-اطلب من مساعد الذكاء الاصطناعي التفاعل مع نظام إدارة علاقات العملاء (CRM) لديك:
-
-* *"أرني أحدث 5 شركات تم إنشاؤها"*
-* *"أنشئ شخصًا جديدًا باسم Jane Doe في Acme Corp"*
-* *"اعثر على جميع الفرص المفتوحة التي تزيد قيمتها عن 10 آلاف دولار"*
-
-## الأدوات المتاحة
-
-بعد الاتصال، يوفّر خادم MCP أدوات تعكس واجهة برمجة تطبيقات Twenty (API). سير العمل الموصى به هو:
-
-1. **`get_tool_catalog`** — اكتشف جميع الأدوات المتاحة
-2. **`learn_tools`** — احصل على مخطط الإدخال لأدوات محددة
-3. **`execute_tool`** — شغّل أداة
-
-لا تحتاج إلى تذكّر أسماء الأدوات. اسأل مساعد الذكاء الاصطناعي عمّا يمكنه فعله وسيستدعي `get_tool_catalog` تلقائيًا.
-
-## الصلاحيات
-
-ترث اتصالات MCP أذونات المستخدم المُصادَق عليه (OAuth) أو الدور المُعيَّن لمفتاح API. لتقييد ما يمكن لخادم MCP القيام به:
-
-* **OAuth**: ينطبق دور المستخدم في مساحة العمل.
-* **API Key**: عيِّن دورًا لمفتاح API ضمن **Settings > Roles**. راجع [الأذونات](/l/ar/user-guide/permissions-access/capabilities/permissions).
-
-## التكوين ذاتي الاستضافة
-
-في حالات الاستضافة الذاتية، استبدِل `{your-workspace-url}` بعنوان URL الخاص بالخادم لديك. تأكّد من أن قيمة `SERVER_URL` في بيئتك تطابق عنوان URL العام لمثيل Twenty لديك — إذ يُستخدَم ذلك لإنشاء بيانات تعريف اكتشاف OAuth.
-
-```bash
-SERVER_URL=https://twenty.yourcompany.com
-```
-
-تُشتق نقطة نهاية MCP ونقاط نهاية OAuth وبيانات تعريف الاكتشاف جميعها من هذه القيمة.
-
-## استكشاف الأخطاء وإصلاحها
-
-**أخطاء "Unauthorized" أو 401**
-
-* OAuth: أعد التفويض عبر مسح الرموز المميِّزة المخزنة في عميل MCP لديك ثم أعد الاتصال.
-* API Key: تحقّق من أن المفتاح صالح ولم تنتهِ صلاحيته. أعِد توليده إذا لزم الأمر.
-
-**عملية OAuth لا تفتح متصفحًا**
-
-* تأكّد من أن عميل MCP لديك يدعم تفويض MCP. ارجع إلى طريقة مفتاح API إذا لم يكن كذلك.
-
-**انتهاء مهلة الاتصال**
-
-* تحقّق من إمكانية الوصول إلى عنوان URL لنقطة نهاية MCP من جهازك. بالنسبة لحالات الاستضافة الذاتية، تحقّق من أن الخادم يعمل وأن `SERVER_URL` مُعيَّن بشكل صحيح.

packages/twenty-docs/l/ar/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails.mdx

@@ -1,121 +0,0 @@
----
-title: الرد التلقائي على رسائل البريد الإلكتروني الواردة
-description: أنشئ سير عمل يستخدم الذكاء الاصطناعي لفرز رسائل البريد الإلكتروني الواردة وإرسال ردود ضمن سلسلة المحادثة تلقائيًا.
----
-
-استجب لرسائل البريد الإلكتروني الواردة خلال ثوانٍ — وليس ساعات. يستخدم سير العمل هذا وكيلاً للذكاء الاصطناعي لتصفية الضوضاء (النشرات الإخبارية، الرسائل غير المرغوب فيها، الردود التلقائية) وصياغة رد مخصص للرسائل الحقيقية، ثم يرسله كرد مُسلسل داخل المحادثة الأصلية.
-
-## كيف يعمل تسلسل رسائل البريد الإلكتروني
-
-تحمل كل رسالة بريد إلكتروني ترويسة `Message-ID` مخفية — بصمة فريدة يعيّنها خادم بريد المرسل. عند الرد على بريد إلكتروني، يقوم عميل البريد لديك بتعيين ترويسة `In-Reply-To` التي تُشير إلى تلك البصمة. بهذه الطريقة يقوم Gmail وOutlook وكل عميل آخر بتجميع الرسائل في سلاسل المحادثات.
-
-في Twenty، تُخزَّن تلك البصمة كـ `headerMessageId` على كائن Message. يلتقطه سير العمل لديك ويمرّره إلى حقل In-Reply-To لإجراء Send Email.
-
-## بناء سير العمل
-
-### الخطوة 1: إنشاء سير عمل جديد
-
-توجّه إلى **Settings -> Workflows** وانقر **+ New Workflow**.
-
-### الخطوة 2: التشغيل عند الرسائل الواردة
-
-اختر **When a Record is Created** ثم **Messages**.
-
-في كل مرة يصل فيها بريد إلكتروني إلى Twenty، يُشغَّل هذا.
-
-<img src="/images/user-guide/workflows/auto-reply/workflow-overview.png" style={{width:'100%'}} />
-
-### الخطوة 3: البحث عن المُرسِل
-
-أضِف إجراء **Search Records**.
-
-عنوان المُرسِل ليس في الرسالة نفسها — بل في سجل Message Participant المرتبط.
-
-| الحقل      | القيمة                             |
-| ---------- | ---------------------------------- |
-| **الكائن** | المشاركون في الرسالة               |
-| **تصفية**  | Message **يساوي** `{{trigger.id}}` |
-| **تصفية**  | Role **يساوي** From                |
-| **الحد**   | 1                                  |
-
-سيمنحك هذا بريد المُرسِل الإلكتروني في `handle` واسمه في `displayName`.
-
-<img src="/images/user-guide/workflows/auto-reply/find-sender.png" style={{width:'100%'}} />
-
-### الخطوة 4: الفرز بالذكاء الاصطناعي وصياغة الرد
-
-أضِف إجراء **AI Agent**. تقوم هذه الخطوة الواحدة بأمرين: تقرر ما إذا كان البريد الإلكتروني يستحق الرد، وإن كان كذلك، تصوغ ردًا.
-
-استخدم موجهًا مثل:
-
-```
-You are an email triage assistant for a sales team. Read the following
-inbound email and decide if it deserves a reply.
-
-Subject: {{trigger.subject}}
-Body: {{trigger.text}}
-From: {{Find Sender.first.displayName}} ({{Find Sender.first.handle}})
-
-If this email is spam, a newsletter, an automated notification, or
-otherwise does not need a human reply, respond with exactly: SKIP
-
-Otherwise, write a short, professional reply (3-4 sentences max) that:
-- Acknowledges their specific message
-- Lets them know someone from the team will follow up shortly
-- Is warm but not overly casual
-
-Respond with only the reply text, no subject line or greeting prefix.
-```
-
-يُنتِج AI Agent استجابته في الحقل `response` الذي يمكن للخطوات التالية الرجوع إليه.
-
-<img src="/images/user-guide/workflows/auto-reply/ai-triage.png" style={{width:'100%'}} />
-
-### الخطوة 5: التفريع بناءً على قرار الذكاء الاصطناعي
-
-أضِف إجراء **If/Else** للتحقق مما إذا كان الذكاء الاصطناعي قرر الرد أم التخطي.
-
-| الحقل              | القيمة                                      |
-| ------------------ | ------------------------------------------- |
-| **الشرط**          | AI Agent `response` **لا يحتوي على** `SKIP` |
-| **إذا كان صحيحًا** | المتابعة إلى Send Email                     |
-| **وإلا**           | لا تفعل شيئًا (ينتهي سير العمل)             |
-
-يتم تجاهل الرسائل غير المرغوب فيها والنشرات البريدية والرسائل المُنشأة تلقائيًا. كل ما عدا ذلك ينتقل إلى الخطوة التالية.
-
-<img src="/images/user-guide/workflows/auto-reply/should-reply.png" style={{width:'100%'}} />
-
-### الخطوة 6: إرسال رد ضمن سلسلة المحادثة
-
-أضِف إجراء **Send Email** على فرع "if true". انقر **Advanced options** ثم **Add In-Reply-To**.
-
-| الحقل           | القيمة                                 |
-| --------------- | -------------------------------------- |
-| **إلى**         | `{{Find Sender.first.handle}}`         |
-| **الموضوع**     | `Re: {{trigger.subject}}`              |
-| **المحتوى**     | `{{AI Triage & Draft Reply.response}}` |
-| **In-Reply-To** | `{{trigger.headerMessageId}}`          |
-
-حقل In-Reply-To هو ما يجعل هذا ردًا بدلًا من محادثة جديدة. سيراه المستلِم ضمن سلسلة تحت البريد الأصلي في Gmail أو Outlook أو أي عميل آخر.
-
-<img src="/images/user-guide/workflows/auto-reply/send-email.png" style={{width:'100%'}} />
-
-<Tip>
-**In-Reply-To** يتوقّع `message.headerMessageId` من المشغّل — إنها البصمة الفريدة للبريد الإلكتروني، وليست عنوان المستلم. إذا تركته فارغًا، فسيُرسَل البريد الإلكتروني على أي حال، ولكن كرسالة مستقلة.
-</Tip>
-
-<Warning>
-يستخدم Gmail سطر الموضوع لتجميع الرسائل في سلاسل المحادثات. يجب أن يبدأ الموضوع بـ `Re:` (بما في ذلك النقطتان والمسافة) ليعرض Gmail الرد داخل سلسلة المحادثة الأصلية. بدون ذلك، سيظهر الرد كمحادثة منفصلة — حتى إذا تم تعيين ترويسة In-Reply-To بشكل صحيح.
-</Warning>
-
-### الخطوة 7: الاختبار والتفعيل
-
-اضغط **Test**، ثم تحقّق من عميل البريد لديك. يجب أن يظهر الرد متداخلًا تحت الرسالة الأصلية.
-
-فعِّل عندما تكون راضيًا عنه.
-
-## أفكار للبناء عليها
-
-* **الرد على كبار الشخصيات فقط** — أضِف فرعًا يتحقق من مجال المُرسِل أو مما إذا كان موجودًا كجهة اتصال في Twenty
-* **التوجيه حسب النية** — استخدم موجهات AI Agent منفصلة للتعامل مع استفسارات المبيعات بشكل مختلف عن طلبات الدعم
-* **الإثراء قبل الرد** — أضِف خطوة Search Records لجلب شركة المُرسِل أو سجل الصفقات إلى الموجه الخاص بالذكاء الاصطناعي للحصول على ردود أكثر تخصيصًا

packages/twenty-docs/l/de/developers/extend/capabilities/apps.mdx

@@ -21,51 +21,19 @@ Mit Apps können Sie Twenty-Anpassungen **als Code** erstellen und verwalten. An
 ## Voraussetzungen
 
 * Node.js 24+ und Yarn 4
-* Docker (für den lokalen Twenty-Dev-Server)
+* Ein Twenty-Workspace und ein API-Schlüssel (unter https://app.twenty.com/settings/api-webhooks erstellen)
 
 ## Erste Schritte
 
-Erstelle eine neue App mit dem offiziellen Scaffolder. Der Scaffolder kann für dich automatisch eine lokale Twenty-Instanz starten:
+Erstellen Sie mit dem offiziellen Scaffolder eine neue App, authentifizieren Sie sich und beginnen Sie mit der Entwicklung:
 
 ```bash filename="Terminal"
-# Eine neue App erstellen — die CLI bietet an, einen lokalen Twenty-Server zu starten
+# Eine neue App erstellen (enthält standardmäßig alle Beispiele)
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app
 
 # Dev-Modus starten: synchronisiert lokale Änderungen automatisch mit deinem Arbeitsbereich
-yarn twenty dev
-```
-
-### Lokale Serververwaltung
-
-Das SDK enthält Befehle zur Verwaltung eines lokalen Twenty-Dev-Servers (All-in-One-Docker-Image mit PostgreSQL, Redis, Server und Worker):
-
-```bash filename="Terminal"
-# Den lokalen Server starten (lädt das Image bei Bedarf herunter)
-yarn twenty server start
-
-# Serverstatus prüfen
-yarn twenty server status
-
-# Serverprotokolle streamen
-yarn twenty server logs
-
-# Server stoppen
-yarn twenty server stop
-
-# Alle Daten zurücksetzen und neu starten
-yarn twenty server reset
-```
-
-Der lokale Server ist bereits mit einem Arbeitsbereich und einem Benutzer (`[email protected]` / `[email protected]`) vorbefüllt, sodass Sie ohne manuelle Einrichtung sofort mit der Entwicklung beginnen können.
-
-### Authentifizierung
-
-Verbinden Sie Ihre App mithilfe von OAuth mit dem lokalen Server:
-
-```bash filename="Terminal"
-# Authenticate via OAuth (opens browser)
-yarn twenty remote add --local
+yarn twenty app:dev
 ```
 
 Das Scaffolding-Tool unterstützt zwei Modi, um zu steuern, welche Beispieldateien enthalten sind:

packages/twenty-docs/l/de/developers/self-host/capabilities/troubleshooting.mdx

@@ -166,10 +166,6 @@ plugins: [
 
 Führen Sie den folgenden Befehl im Datenbankcontainer aus, um Zugriff auf das Admin-Panel zu erhalten: `UPDATE core."user" SET "canAccessFullAdminPanel" = TRUE WHERE email = '[email protected]';`
 
-#### Beim Ausführen eines Workflows schlägt die Workflow-Ausführung fehl mit "Logic function execution is disabled. Set LOGIC_FUNCTION_TYPE to LOCAL or LAMBDA to enable."
-
-In der Produktion sind Logikfunktionen standardmäßig deaktiviert. Setzen Sie die Umgebungsvariable `LOGIC_FUNCTION_TYPE` auf `LOCAL` oder `LAMBDA`, um sie zu aktivieren. Dies kann über Umgebungsvariablen oder über die Datenbankvariablen des Admin-Panels konfiguriert werden. Details finden Sie im [Leitfaden zur Einrichtung von Logikfunktionen](/l/de/developers/self-host/capabilities/setup#logic-functions-available-drivers).
-
 ### 1-Klick Docker Compose
 
 #### Kann mich nicht einloggen

packages/twenty-docs/l/de/user-guide/ai/capabilities/mcp.mdx

@@ -1,142 +0,0 @@
----
-title: MCP-Server
-description: Verbinden Sie KI-Assistenten mit Ihrem Twenty-Workspace über das Model Context Protocol.
----
-
-<Warning>
-MCP befindet sich derzeit in **alpha** und ist nur in einigen Workspaces verfügbar. Möglicherweise ist es für Ihren Workspace noch nicht aktiviert.
-</Warning>
-
-Twenty stellt einen [MCP](https://modelcontextprotocol.io/)-Server bereit, damit KI-Assistenten — Claude Desktop, Claude Code, Cursor, ChatGPT und andere — Ihre CRM-Daten in natürlicher Sprache lesen und schreiben können.
-
-Verwenden Sie Ihre **Workspace-URL** (die URL, mit der Sie auf Twenty zugreifen) als MCP-Endpunkt. In Twenty Cloud kann Ihre Workspace-URL `https://{mycompany}.twenty.com` oder eine benutzerdefinierte Domain sein. Der Server ist verfügbar unter:
-
-| Umgebung          | MCP-Endpunkt                                                                  |
-| ----------------- | ----------------------------------------------------------------------------- |
-| **Cloud**         | `https://{your-workspace-url}/mcp` (z. B. `https://mycompany.twenty.com/mcp`) |
-| **Selbsthosting** | `https://{your-domain}/mcp`                                                   |
-
-## Authentifizierungsmethoden
-
-Sie haben zwei Möglichkeiten, Ihren MCP-Client zu authentifizieren: **OAuth** (empfohlen) oder **API-Schlüssel**.
-
-### Option A — OAuth (empfohlen)
-
-Mit OAuth öffnet Ihr MCP-Client ein Browserfenster, damit Sie sich anmelden können. Es werden keine geheimen Informationen in Konfigurationsdateien gespeichert, und Token werden automatisch erneuert.
-
-<Note>
-OAuth erfordert einen MCP-Client, der die [MCP-Autorisierungsspezifikation](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization) unterstützt. Claude Desktop, Claude Code, Cursor und ChatGPT unterstützen dies.
-</Note>
-
-Fügen Sie dies zu Ihrer MCP-Client-Konfiguration hinzu und ersetzen Sie `{your-workspace-url}` durch den Host Ihrer Workspace-URL (z. B. `mycompany.twenty.com`):
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp"
-    }
-  }
-}
-```
-
-Das ist alles — kein API-Schlüssel erforderlich. Wenn der Client sich zum ersten Mal verbindet, wird er:
-
-1. Die OAuth-Metadaten von Twenty über `/.well-known/oauth-protected-resource` und `/.well-known/oauth-authorization-server` ermitteln
-2. Sich über die dynamische Client-Registrierung (RFC 7591) als OAuth-Client registrieren
-3. Ihren Browser öffnen, um den Zugriff zu autorisieren
-4. Token empfangen und eine Verbindung zum MCP-Server herstellen
-
-Nachfolgende Verbindungen verwenden die gespeicherten Token erneut und erneuern sie automatisch.
-
-### Option B — API-Schlüssel
-
-Wenn Ihr MCP-Client OAuth nicht unterstützt oder Sie statische Anmeldeinformationen bevorzugen, übergeben Sie einen API-Schlüssel im `Authorization`-Header:
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_API_KEY"
-      }
-    }
-  }
-}
-```
-
-<Warning>
-Ihr API-Schlüssel gewährt Zugriff auf Workspace-Daten. Halten Sie es von der Versionskontrolle und von gemeinsam genutzten Dotfiles fern.
-</Warning>
-
-Um einen API-Schlüssel zu erstellen, gehen Sie zu **Settings > APIs & Webhooks > + Create key**. Details finden Sie unter [APIs](/l/de/developers/extend/api#create-an-api-key).
-
-## Schnellstart
-
-### 1. Konfiguration kopieren
-
-Gehen Sie in Twenty zu **Settings > AI > More > MCP Server**. Wählen Sie Ihre Authentifizierungsmethode (OAuth oder API-Schlüssel), kopieren Sie das JSON-Snippet (es verwendet bereits Ihre Workspace-URL) und fügen Sie es in die Konfigurationsdatei Ihres MCP-Clients ein.
-
-| Client             | Speicherort der Konfigurationsdatei                                                                                                                                                              |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| **Claude Desktop** | `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) oder `%APPDATA%\Claude\claude_desktop_config.json` (Windows)                                                           |
-| **Claude Code**    | `~/.claude.json` (Benutzer) oder `.mcp.json` (Projekt)                                                                                                                                           |
-| **Cursor**         | `.cursor/mcp.json` in Ihrem Projekt oder `~/.cursor/mcp.json` global                                                                                                                             |
-| **ChatGPT**        | Aktivieren Sie den Entwicklermodus in **Settings > Apps & Connectors > Advanced settings** und verwenden Sie dann **Create** in **Settings > Apps & Connectors**, um den MCP-Server hinzuzufügen |
-
-### 2. Verbinden
-
-Starten Sie Ihren MCP-Client neu (oder laden Sie die Konfiguration neu). Bei Verwendung von OAuth werden Sie zu Twenty weitergeleitet, um den Zugriff zu autorisieren. Bei Verwendung eines API-Schlüssels wird die Verbindung sofort hergestellt.
-
-### 3. Jetzt loslegen
-
-Bitten Sie Ihren KI-Assistenten, mit Ihrem CRM zu interagieren:
-
-* *"Zeige mir die 5 zuletzt erstellten Unternehmen"*
-* *"Erstelle eine neue Person namens Jane Doe bei Acme Corp"*
-* *"Finde alle offenen Verkaufschancen mit einem Wert von mehr als $10k"*
-
-## Verfügbare Tools
-
-Nach der Verbindung stellt der MCP-Server Tools bereit, die die Twenty-API widerspiegeln. Der empfohlene Workflow ist:
-
-1. **`get_tool_catalog`** — alle verfügbaren Tools entdecken
-2. **`learn_tools`** — das Eingabeschema für bestimmte Tools abrufen
-3. **`execute_tool`** — ein Tool ausführen
-
-Sie müssen sich die Tool-Namen nicht merken. Fragen Sie Ihren KI-Assistenten, was er tun kann, und er ruft `get_tool_catalog` automatisch auf.
-
-## Berechtigungen
-
-MCP-Verbindungen erben die Berechtigungen des authentifizierten Benutzers (OAuth) oder die dem API-Schlüssel zugewiesene Rolle. So beschränken Sie, was der MCP-Server tun darf:
-
-* **OAuth**: Es gilt die Workspace-Rolle des Benutzers.
-* **API-Schlüssel**: Weisen Sie dem API-Schlüssel unter **Settings > Roles** eine Rolle zu. Siehe [Berechtigungen](/l/de/user-guide/permissions-access/capabilities/permissions).
-
-## Selbstgehostete Konfiguration
-
-Für selbstgehostete Instanzen ersetzen Sie `{your-workspace-url}` durch die URL Ihres Servers. Stellen Sie sicher, dass `SERVER_URL` in Ihrer Umgebung der öffentlichen URL Ihrer Twenty-Instanz entspricht — dieser Wert wird verwendet, um die OAuth-Discovery-Metadaten zu generieren.
-
-```bash
-SERVER_URL=https://twenty.yourcompany.com
-```
-
-Der MCP-Endpunkt, die OAuth-Endpunkte und die Discovery-Metadaten leiten sich alle von diesem Wert ab.
-
-## Fehlerbehebung
-
-**"Unauthorized"- oder 401-Fehler**
-
-* OAuth: Autorisieren Sie erneut, indem Sie die gespeicherten Token in Ihrem MCP-Client löschen und die Verbindung wiederherstellen.
-* API-Schlüssel: Überprüfen Sie, ob der Schlüssel gültig ist und nicht abgelaufen ist. Generieren Sie ihn bei Bedarf neu.
-
-**Der OAuth-Flow öffnet keinen Browser**
-
-* Stellen Sie sicher, dass Ihr MCP-Client MCP Authorization unterstützt. Wechseln Sie andernfalls zur API-Schlüssel-Methode.
-
-**Verbindungszeitüberschreitung**
-
-* Stellen Sie sicher, dass die MCP-Endpunkt-URL von Ihrem Rechner aus erreichbar ist. Bei selbstgehosteten Instanzen prüfen Sie, ob der Server läuft und `SERVER_URL` korrekt gesetzt ist.

packages/twenty-docs/l/de/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails.mdx

@@ -1,121 +0,0 @@
----
-title: Automatische Antwort auf eingehende E-Mails
-description: Erstellen Sie einen Workflow, der KI nutzt, um eingehende E-Mails zu sichten und automatisch Antworten im Thread zu senden.
----
-
-Antworten Sie auf eingehende E-Mails in Sekunden — nicht in Stunden. Dieser Workflow verwendet einen KI-Agenten, um Störendes auszufiltern (Newsletter, Spam, automatische Antworten) und eine personalisierte Antwort auf echte Nachrichten zu verfassen und sie dann als Antwort im Thread innerhalb der ursprünglichen Unterhaltung zu senden.
-
-## Wie E-Mail-Threading funktioniert
-
-Jede E-Mail enthält einen verborgenen `Message-ID`-Header — einen eindeutigen Fingerabdruck, der vom Mailserver des Absenders zugewiesen wird. Wenn Sie auf eine E-Mail antworten, setzt Ihr E-Mail-Client einen `In-Reply-To`-Header, der auf diesen Fingerabdruck verweist. So gruppieren Gmail, Outlook und alle anderen Clients Nachrichten in Threads.
-
-In Twenty wird dieser Fingerabdruck als `headerMessageId` am Message-Objekt gespeichert. Ihr Workflow greift ihn auf und übergibt ihn an das Feld In-Reply-To der Aktion Send Email.
-
-## Den Workflow erstellen
-
-### Schritt 1: Neuen Workflow erstellen
-
-Gehen Sie zu **Settings -> Workflows** und klicken Sie auf **+ New Workflow**.
-
-### Schritt 2: Bei eingehenden Nachrichten auslösen
-
-Wählen Sie **When a Record is Created** und dann **Messages**.
-
-Jedes Mal, wenn eine E-Mail in Twenty eingeht, wird dies ausgelöst.
-
-<img src="/images/user-guide/workflows/auto-reply/workflow-overview.png" style={{width:'100%'}} />
-
-### Schritt 3: Absender ermitteln
-
-Fügen Sie eine **Datensätze suchen**-Aktion hinzu.
-
-Die Absenderadresse befindet sich nicht in der Nachricht selbst — sie steht im zugehörigen Datensatz Message Participant.
-
-| Feld       | Wert                             |
-| ---------- | -------------------------------- |
-| **Objekt** | Nachrichtenteilnehmer            |
-| **Filter** | Message **ist** `{{trigger.id}}` |
-| **Filter** | Rolle **ist** From               |
-| **Limit**  | 1                                |
-
-Dadurch erhalten Sie die E-Mail-Adresse des Absenders in `handle` und den Namen in `displayName`.
-
-<img src="/images/user-guide/workflows/auto-reply/find-sender.png" style={{width:'100%'}} />
-
-### Schritt 4: KI-Triage und Antwortentwurf
-
-Fügen Sie eine **AI Agent**-Aktion hinzu. Dieser einzelne Schritt erledigt zwei Dinge: Er entscheidet, ob die E-Mail eine Antwort verdient, und falls ja, verfasst er eine.
-
-Verwenden Sie einen Prompt wie:
-
-```
-You are an email triage assistant for a sales team. Read the following
-inbound email and decide if it deserves a reply.
-
-Subject: {{trigger.subject}}
-Body: {{trigger.text}}
-From: {{Find Sender.first.displayName}} ({{Find Sender.first.handle}})
-
-If this email is spam, a newsletter, an automated notification, or
-otherwise does not need a human reply, respond with exactly: SKIP
-
-Otherwise, write a short, professional reply (3-4 sentences max) that:
-- Acknowledges their specific message
-- Lets them know someone from the team will follow up shortly
-- Is warm but not overly casual
-
-Respond with only the reply text, no subject line or greeting prefix.
-```
-
-Der AI Agent gibt seine Antwort in einem Feld `response` aus, auf das sich die nächsten Schritte beziehen können.
-
-<img src="/images/user-guide/workflows/auto-reply/ai-triage.png" style={{width:'100%'}} />
-
-### Schritt 5: Verzweigen anhand der KI-Entscheidung
-
-Fügen Sie eine **If/Else**-Aktion hinzu, um zu prüfen, ob die KI sich entschieden hat zu antworten oder zu überspringen.
-
-| Feld          | Wert                                         |
-| ------------- | -------------------------------------------- |
-| **Bedingung** | AI Agent `response` **enthält nicht** `SKIP` |
-| **Wenn wahr** | Mit Send Email fortfahren                    |
-| **Sonst**     | Nichts tun (Workflow endet)                  |
-
-Spam, Newsletter und automatisch erzeugte Nachrichten werden verworfen. Alles andere geht zum nächsten Schritt über.
-
-<img src="/images/user-guide/workflows/auto-reply/should-reply.png" style={{width:'100%'}} />
-
-### Schritt 6: Eine Antwort im Thread senden
-
-Fügen Sie im "Wenn wahr"-Zweig eine **Send Email**-Aktion hinzu. Klicken Sie auf **Advanced options**, dann **Add In-Reply-To**.
-
-| Feld            | Wert                                   |
-| --------------- | -------------------------------------- |
-| **An**          | `{{Find Sender.first.handle}}`         |
-| **Betreff**     | `Re: {{trigger.subject}}`              |
-| **Body**        | `{{AI Triage & Draft Reply.response}}` |
-| **In-Reply-To** | `{{trigger.headerMessageId}}`          |
-
-Das Feld In-Reply-To sorgt dafür, dass dies eine Antwort und keine neue Unterhaltung ist. Der Empfänger sieht sie als Teil des Threads unter der ursprünglichen E-Mail in Gmail, Outlook oder jedem anderen Client.
-
-<img src="/images/user-guide/workflows/auto-reply/send-email.png" style={{width:'100%'}} />
-
-<Tip>
-**In-Reply-To** erwartet eine `message.headerMessageId` aus dem Trigger — das ist der eindeutige Fingerabdruck der E-Mail, keine Empfängeradresse. Wenn Sie es leer lassen, wird die E-Mail trotzdem gesendet, nur als eigenständige Nachricht.
-</Tip>
-
-<Warning>
-Gmail verwendet die Betreffzeile, um Nachrichten in Threads zu gruppieren. Der Betreff **muss** mit `Re:` beginnen (einschließlich Doppelpunkt und Leerzeichen), damit Gmail die Antwort im ursprünglichen Thread anzeigt. Ohne dies erscheint die Antwort als separate Unterhaltung — selbst wenn der In-Reply-To-Header korrekt gesetzt ist.
-</Warning>
-
-### Schritt 7: Testen und aktivieren
-
-Klicken Sie auf **Test**, und prüfen Sie dann Ihren E-Mail-Client. Die Antwort sollte unter der ursprünglichen Nachricht verschachtelt erscheinen.
-
-Aktivieren Sie ihn, wenn Sie zufrieden sind.
-
-## Ideen zum Ausbau
-
-* **Nur an VIPs antworten** — fügen Sie einen Zweig hinzu, der die Domain des Absenders prüft oder ob er in Twenty als Kontakt existiert
-* **Nach Absicht routen** — verwenden Sie separate AI Agent-Prompts, um Vertriebsanfragen anders zu bearbeiten als Supportanfragen
-* **Vor der Antwort anreichern** — fügen Sie einen Schritt Search Records hinzu, um das Unternehmen oder die Deal-Historie des Absenders in den AI-Prompt zu übernehmen, für persönlichere Antworten

packages/twenty-docs/l/it/developers/extend/capabilities/apps.mdx

@@ -21,51 +21,19 @@ Le app ti consentono di creare e gestire le personalizzazioni di Twenty **come c
 ## Prerequisiti
 
 * Node.js 24+ e Yarn 4
-* Docker (per il server di sviluppo locale di Twenty)
+* Uno spazio di lavoro Twenty e una chiave API (creane una su https://app.twenty.com/settings/api-webhooks)
 
 ## Per iniziare
 
-Crea una nuova app utilizzando lo scaffolder ufficiale. Può avviare automaticamente un'istanza locale di Twenty per te:
+Crea una nuova app utilizzando lo scaffolder ufficiale, quindi autenticati e inizia a sviluppare:
 
 ```bash filename="Terminal"
-# Crea lo scaffold di una nuova app — la CLI offrirà di avviare un server locale di Twenty
+# Crea lo scaffold di una nuova app (include tutti gli esempi per impostazione predefinita)
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app
 
 # Avvia la modalità di sviluppo: sincronizza automaticamente le modifiche locali con il tuo workspace
-yarn twenty dev
-```
-
-### Gestione del server locale
-
-L'SDK include comandi per gestire un server di sviluppo locale di Twenty (immagine Docker all-in-one con PostgreSQL, Redis, server e worker):
-
-```bash filename="Terminal"
-# Avvia il server locale (scarica l'immagine se necessario)
-yarn twenty server start
-
-# Verifica lo stato del server
-yarn twenty server status
-
-# Segui i log del server
-yarn twenty server logs
-
-# Arresta il server
-yarn twenty server stop
-
-# Reimposta tutti i dati e riparti da zero
-yarn twenty server reset
-```
-
-Il server locale è preconfigurato con uno spazio di lavoro e un utente (`[email protected]` / `[email protected]`), così puoi iniziare a sviluppare immediatamente senza alcuna configurazione manuale.
-
-### Autenticazione
-
-Collega la tua app al server locale tramite OAuth:
-
-```bash filename="Terminal"
-# Autenticati tramite OAuth (apre il browser)
-yarn twenty remote add --local
+yarn twenty app:dev
 ```
 
 Lo strumento di scaffolding supporta due modalità per controllare quali file di esempio vengono inclusi:

packages/twenty-docs/l/it/developers/self-host/capabilities/troubleshooting.mdx

@@ -167,10 +167,6 @@ plugins: [
 
 Esegui `UPDATE core."user" SET "canAccessFullAdminPanel" = TRUE WHERE email = '[email protected]';` nel container del database per accedere al pannello di amministrazione.
 
-#### Durante l'esecuzione di un workflow, l'esecuzione del workflow non riesce con "L'esecuzione delle funzioni logiche è disabilitata. Imposta LOGIC_FUNCTION_TYPE su LOCAL o LAMBDA per abilitarle."
-
-In produzione, le funzioni logiche sono disabilitate per impostazione predefinita. Imposta la variabile d'ambiente `LOGIC_FUNCTION_TYPE` su `LOCAL` o `LAMBDA` per abilitarle. Questo può essere configurato tramite variabili d'ambiente o tramite le variabili del database del pannello di amministrazione. Consulta la [guida alla configurazione delle funzioni logiche](/l/it/developers/self-host/capabilities/setup#logic-functions-available-drivers) per dettagli.
-
 ### Composizione Docker a un clic
 
 #### Impossibile connettersi

packages/twenty-docs/l/it/user-guide/ai/capabilities/mcp.mdx

@@ -1,142 +0,0 @@
----
-title: Server MCP
-description: Collega gli assistenti AI al tuo spazio di lavoro di Twenty utilizzando il Model Context Protocol.
----
-
-<Warning>
-MCP è attualmente in **alpha** ed è disponibile solo su alcuni spazi di lavoro. Potrebbe non essere ancora abilitato per il tuo spazio di lavoro.
-</Warning>
-
-Twenty espone un server [MCP](https://modelcontextprotocol.io/) affinché gli assistenti AI — Claude Desktop, Claude Code, Cursor, ChatGPT e altri — possano leggere e scrivere i dati del tuo CRM in linguaggio naturale.
-
-Usa l'**URL dello spazio di lavoro** (l'URL che usi per accedere a Twenty) come endpoint MCP. Su Twenty Cloud, l'URL del tuo spazio di lavoro potrebbe essere `https://{mycompany}.twenty.com` oppure un dominio personalizzato. Il server è disponibile all'indirizzo:
-
-| Ambiente          | Endpoint MCP                                                                   |
-| ----------------- | ------------------------------------------------------------------------------ |
-| **Cloud**         | `https://{your-workspace-url}/mcp` (ad es. `https://mycompany.twenty.com/mcp`) |
-| **Auto-ospitato** | `https://{your-domain}/mcp`                                                    |
-
-## Metodi di autenticazione
-
-Hai due modi per autenticare il tuo client MCP: **OAuth** (consigliato) o **API Key**.
-
-### Opzione A — OAuth (Consigliato)
-
-Con OAuth, il tuo client MCP apre una finestra del browser per effettuare l'accesso. Nessun segreto viene archiviato nei file di configurazione e i token si rinnovano automaticamente.
-
-<Note>
-OAuth richiede un client MCP che supporti la [specifica MCP Authorization](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization). Claude Desktop, Claude Code, Cursor e ChatGPT lo supportano.
-</Note>
-
-Aggiungi questo alla configurazione del tuo client MCP, sostituendo `{your-workspace-url}` con l'host del tuo spazio di lavoro (ad es. `mycompany.twenty.com`):
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp"
-    }
-  }
-}
-```
-
-È tutto — non è necessaria alcuna chiave API. Quando il client si connette per la prima volta, eseguirà:
-
-1. Scoprire i metadati OAuth di Twenty tramite `/.well-known/oauth-protected-resource` e `/.well-known/oauth-authorization-server`
-2. Registrarsi come client OAuth tramite registrazione dinamica del client (RFC 7591)
-3. Aprire il browser per autorizzare l'accesso
-4. Ricevere i token e connettersi al server MCP
-
-Le connessioni successive riutilizzano i token memorizzati e li rinnovano automaticamente.
-
-### Opzione B — Chiave API
-
-Se il tuo client MCP non supporta OAuth, o preferisci credenziali statiche, passa una chiave API nell'header `Authorization`:
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_API_KEY"
-      }
-    }
-  }
-}
-```
-
-<Warning>
-La tua chiave API concede l'accesso ai dati dello spazio di lavoro. Mantienila fuori dal controllo versione e dai dotfile condivisi.
-</Warning>
-
-Per creare una chiave API, vai su **Impostazioni > API e Webhook > + Crea chiave**. Vedi [API](/l/it/developers/extend/api#create-an-api-key) per i dettagli.
-
-## Avvio rapido
-
-### 1. Copia la configurazione
-
-Vai su **Impostazioni > AI > Altro > MCP Server** in Twenty. Scegli il metodo di autenticazione (OAuth o Chiave API), copia lo snippet JSON (userà già l'URL del tuo spazio di lavoro) e incollalo nel file di configurazione del tuo client MCP.
-
-| Client             | Percorso del file di configurazione                                                                                                                                                     |
-| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Claude Desktop** | `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) o `%APPDATA%\Claude\claude_desktop_config.json` (Windows)                                                     |
-| **Claude Code**    | `~/.claude.json` (utente) o `.mcp.json` (progetto)                                                                                                                                      |
-| **Cursor**         | `.cursor/mcp.json` nel tuo progetto, oppure `~/.cursor/mcp.json` globalmente                                                                                                            |
-| **ChatGPT**        | Attiva la Modalità sviluppatore in **Impostazioni > App e Connettori > Impostazioni avanzate**, quindi usa **Crea** in **Impostazioni > App e Connettori** per aggiungere il server MCP |
-
-### 2. Connetti
-
-Riavvia il tuo client MCP (o ricarica la configurazione). Se usi OAuth verrai reindirizzato a Twenty per autorizzare l'accesso. Se usi una chiave API la connessione è immediata.
-
-### 3. Inizia a usarlo
-
-Chiedi al tuo assistente AI di interagire con il tuo CRM:
-
-* *"Mostrami le 5 aziende create più di recente"*
-* *"Crea una nuova persona di nome Jane Doe presso Acme Corp"*
-* *"Trova tutte le opportunità aperte di valore superiore a $10k"*
-
-## Strumenti disponibili
-
-Una volta connesso, il server MCP espone strumenti che rispecchiano l'API di Twenty. Il flusso di lavoro consigliato è:
-
-1. **`get_tool_catalog`** — scoprire tutti gli strumenti disponibili
-2. **`learn_tools`** — ottenere lo schema di input per strumenti specifici
-3. **`execute_tool`** — eseguire uno strumento
-
-Non è necessario ricordare i nomi degli strumenti. Chiedi al tuo assistente AI cosa può fare e chiamerà `get_tool_catalog` automaticamente.
-
-## Permessi
-
-Le connessioni MCP ereditano le autorizzazioni dell'utente autenticato (OAuth) o il ruolo assegnato alla chiave API. Per limitare ciò che il server MCP può fare:
-
-* **OAuth**: si applica il ruolo dell'utente nello spazio di lavoro.
-* **Chiave API**: assegna un ruolo alla chiave API in **Impostazioni > Ruoli**. Vedi [Autorizzazioni](/l/it/user-guide/permissions-access/capabilities/permissions).
-
-## Configurazione self-hosted
-
-Per le istanze self-hosted, sostituisci `{your-workspace-url}` con l'URL del tuo server. Assicurati che `SERVER_URL` nel tuo ambiente corrisponda all'URL pubblico della tua istanza Twenty — viene utilizzato per generare i metadati di discovery OAuth.
-
-```bash
-SERVER_URL=https://twenty.yourcompany.com
-```
-
-L'endpoint MCP, gli endpoint OAuth e i metadati di discovery derivano tutti da questo valore.
-
-## Risoluzione dei problemi
-
-**Errori "Unauthorized" o 401**
-
-* OAuth: esegui nuovamente l'autorizzazione eliminando i token memorizzati nel tuo client MCP e riconnettiti.
-* Chiave API: verifica che la chiave sia valida e non sia scaduta. Rigenerala se necessario.
-
-**Il flusso OAuth non apre il browser**
-
-* Assicurati che il tuo client MCP supporti MCP Authorization. In caso contrario, ricorri al metodo con Chiave API.
-
-**Timeout di connessione**
-
-* Verifica che l'URL dell'endpoint MCP sia raggiungibile dalla tua macchina. Per le istanze self-hosted, controlla che il server sia in esecuzione e che `SERVER_URL` sia impostato correttamente.

packages/twenty-docs/l/it/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails.mdx

@@ -1,121 +0,0 @@
----
-title: Risposta automatica alle email in arrivo
-description: Crea un flusso di lavoro che utilizza l'IA per smistare le email in arrivo e inviare automaticamente risposte in thread.
----
-
-Rispondi alle email in arrivo in pochi secondi — non ore. Questo flusso di lavoro utilizza un agente IA per filtrare il rumore (newsletter, spam, risposte automatiche) e redigere una risposta personalizzata ai messaggi reali, quindi la invia come risposta in thread all'interno della conversazione originale.
-
-## Come funziona il threading delle email
-
-Ogni email include un'intestazione nascosta `Message-ID` — un'impronta univoca assegnata dal server di posta del mittente. Quando rispondi a un'email, il tuo client di posta imposta un'intestazione `In-Reply-To` che fa riferimento a quell'impronta. È così che Gmail, Outlook e tutti gli altri client raggruppano i messaggi nei thread.
-
-In Twenty, quell'impronta è memorizzata come `headerMessageId` sull'oggetto Message. Il tuo flusso di lavoro la recupera e la passa al campo In-Reply-To dell'azione Send Email.
-
-## Creazione del flusso di lavoro
-
-### Passaggio 1: Crea un nuovo flusso di lavoro
-
-Vai a **Impostazioni -> Flussi di lavoro** e fai clic su **+ New Workflow**.
-
-### Passaggio 2: Imposta il trigger sui messaggi in arrivo
-
-Scegli **When a Record is Created** e seleziona **Messages**.
-
-Ogni volta che un'email arriva in Twenty, questo si attiva.
-
-<img src="/images/user-guide/workflows/auto-reply/workflow-overview.png" style={{width:'100%'}} />
-
-### Passaggio 3: Cerca chi l'ha inviato
-
-Aggiungi un'azione **Search Records**.
-
-L'indirizzo del mittente non è presente sul messaggio stesso — si trova nel record Message Participant correlato.
-
-| Campo       | Valore                          |
-| ----------- | ------------------------------- |
-| **Oggetto** | Partecipanti al messaggio       |
-| **Filtro**  | Message **is** `{{trigger.id}}` |
-| **Filtro**  | Role **is** From                |
-| **Limite**  | 1                               |
-
-Questo ti fornisce l'email del mittente in `handle` e il suo nome in `displayName`.
-
-<img src="/images/user-guide/workflows/auto-reply/find-sender.png" style={{width:'100%'}} />
-
-### Passaggio 4: Triage con AI e bozza di risposta
-
-Aggiungi un'azione **AI Agent**. Questo singolo passaggio fa due cose: decide se l'email merita una risposta e, in tal caso, ne scrive una.
-
-Usa un prompt come:
-
-```
-You are an email triage assistant for a sales team. Read the following
-inbound email and decide if it deserves a reply.
-
-Subject: {{trigger.subject}}
-Body: {{trigger.text}}
-From: {{Find Sender.first.displayName}} ({{Find Sender.first.handle}})
-
-If this email is spam, a newsletter, an automated notification, or
-otherwise does not need a human reply, respond with exactly: SKIP
-
-Otherwise, write a short, professional reply (3-4 sentences max) that:
-- Acknowledges their specific message
-- Lets them know someone from the team will follow up shortly
-- Is warm but not overly casual
-
-Respond with only the reply text, no subject line or greeting prefix.
-```
-
-AI Agent produce la sua risposta in un campo `response` a cui i passaggi successivi possono fare riferimento.
-
-<img src="/images/user-guide/workflows/auto-reply/ai-triage.png" style={{width:'100%'}} />
-
-### Passaggio 5: Ramifica in base alla decisione dell'AI
-
-Aggiungi un'azione **If/Else** per verificare se l'AI ha deciso di rispondere o saltare.
-
-| Campo          | Valore                                          |
-| -------------- | ----------------------------------------------- |
-| **Condizione** | AI Agent `response` **does not contain** `SKIP` |
-| **Se vero**    | Continua con Send Email                         |
-| **Altrimenti** | Non fare nulla (il flusso di lavoro termina)    |
-
-Spam, newsletter e messaggi generati automaticamente vengono scartati. Tutto il resto passa al passaggio successivo.
-
-<img src="/images/user-guide/workflows/auto-reply/should-reply.png" style={{width:'100%'}} />
-
-### Passaggio 6: Invia una risposta nello stesso thread
-
-Aggiungi un'azione **Send Email** nel ramo "if true". Fai clic su **Advanced options**, quindi su **Add In-Reply-To**.
-
-| Campo           | Valore                                 |
-| --------------- | -------------------------------------- |
-| **A**           | `{{Find Sender.first.handle}}`         |
-| **Oggetto**     | `Re: {{trigger.subject}}`              |
-| **Corpo**       | `{{AI Triage & Draft Reply.response}}` |
-| **In-Reply-To** | `{{trigger.headerMessageId}}`          |
-
-Il campo In-Reply-To è ciò che rende questo un messaggio di risposta invece di una nuova conversazione. Il destinatario lo vede nel thread sotto l'email originale in Gmail, Outlook o qualsiasi altro client.
-
-<img src="/images/user-guide/workflows/auto-reply/send-email.png" style={{width:'100%'}} />
-
-<Tip>
-**In-Reply-To** si aspetta un `message.headerMessageId` dal trigger — è l'impronta univoca dell'email, non un indirizzo del destinatario. Se lo lasci vuoto, l'email viene comunque inviata, solo come messaggio autonomo.
-</Tip>
-
-<Warning>
-Gmail usa l'oggetto per raggruppare i messaggi nei thread. L'oggetto **deve** iniziare con `Re:` (inclusi i due punti e lo spazio) affinché Gmail visualizzi la risposta all'interno del thread originale. Senza di esso, la risposta apparirà come una conversazione separata — anche se l'intestazione In-Reply-To è impostata correttamente.
-</Warning>
-
-### Passaggio 7: Testa e attiva
-
-Fai clic su **Test**, quindi controlla il tuo client di posta. La risposta dovrebbe comparire annidata sotto il messaggio originale.
-
-Attivalo quando sei soddisfatto.
-
-## Idee per sviluppare ulteriormente
-
-* **Rispondi solo ai VIP** — aggiungi un ramo che controlli il dominio del mittente o se esiste come Contatto in Twenty
-* **Instrada in base all'intento** — usa prompt distinti di AI Agent per gestire le richieste commerciali in modo diverso rispetto a quelle di supporto
-* **Arricchisci prima di rispondere** — aggiungi un passaggio Search Records per inserire nel prompt dell'AI l'azienda del mittente o la cronologia delle trattative per risposte più personalizzate

packages/twenty-docs/l/pt/developers/extend/capabilities/apps.mdx

@@ -21,51 +21,19 @@ Os aplicativos permitem criar e gerenciar personalizações do Twenty **como có
 ## Pré-requisitos
 
 * Node.js 24+ e Yarn 4
-* Docker (para o servidor de desenvolvimento local do Twenty)
+* Um espaço de trabalho do Twenty e uma chave de API (crie uma em https://app.twenty.com/settings/api-webhooks)
 
 ## Primeiros passos
 
-Crie um novo app usando o gerador oficial de estrutura. Ele pode iniciar automaticamente uma instância local do Twenty para você:
+Crie um novo aplicativo usando o gerador oficial, depois autentique-se e comece a desenvolver:
 
 ```bash filename="Terminal"
-# Criar a estrutura de um novo app — a CLI oferecerá iniciar um servidor local do Twenty
+# Criar a estrutura de um novo app (inclui todos os exemplos por padrão)
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app
 
 # Iniciar modo de desenvolvimento: sincroniza automaticamente as alterações locais com seu workspace
-yarn twenty dev
-```
-
-### Gerenciamento do Servidor Local
-
-O SDK inclui comandos para gerenciar um servidor de desenvolvimento local do Twenty (imagem Docker all-in-one com PostgreSQL, Redis, servidor e worker):
-
-```bash filename="Terminal"
-# Iniciar o servidor local (faz pull da imagem se necessário)
-yarn twenty server start
-
-# Verificar o status do servidor
-yarn twenty server status
-
-# Transmitir os logs do servidor
-yarn twenty server logs
-
-# Parar o servidor
-yarn twenty server stop
-
-# Redefinir todos os dados e começar do zero
-yarn twenty server reset
-```
-
-O servidor local já vem pré-configurado com um espaço de trabalho e um usuário (`[email protected]` / `[email protected]`), para que você possa começar a desenvolver imediatamente, sem qualquer configuração manual.
-
-### Autenticação
-
-Conecte seu aplicativo ao servidor local usando OAuth:
-
-```bash filename="Terminal"
-# Authenticate via OAuth (opens browser)
-yarn twenty remote add --local
+yarn twenty app:dev
 ```
 
 O gerador de estrutura oferece suporte a dois modos para controlar quais arquivos de exemplo são incluídos:

packages/twenty-docs/l/pt/developers/self-host/capabilities/troubleshooting.mdx

@@ -166,10 +166,6 @@ plugins: [
 
 Execute `UPDATE core."user" SET "canAccessFullAdminPanel" = TRUE WHERE email = 'você@seudominio.com';` no contêiner de banco de dados para obter acesso ao painel administrativo.
 
-#### Ao executar um fluxo de trabalho, a execução do fluxo de trabalho falha com "A execução da função de lógica está desativada. Defina LOGIC_FUNCTION_TYPE como LOCAL ou LAMBDA para ativar."
-
-Em produção, as funções de lógica estão desativadas por padrão. Defina a variável de ambiente `LOGIC_FUNCTION_TYPE` como `LOCAL` ou `LAMBDA` para ativá-las. Isso pode ser configurado por meio de variáveis de ambiente ou pelas variáveis de banco de dados do painel de administração. Veja o [guia de configuração de Funções de Lógica](/l/pt/developers/self-host/capabilities/setup#logic-functions-available-drivers) para obter detalhes.
-
 ### Docker compose com um clique
 
 #### Impossível efetuar login

packages/twenty-docs/l/pt/user-guide/ai/capabilities/mcp.mdx

@@ -1,142 +0,0 @@
----
-title: Servidor MCP
-description: Conecte assistentes de IA ao seu espaço de trabalho do Twenty usando o Model Context Protocol.
----
-
-<Warning>
-O MCP está atualmente em **alfa** e está disponível apenas em alguns espaços de trabalho. O MCP pode ainda não estar ativado no seu espaço de trabalho.
-</Warning>
-
-O Twenty expõe um servidor [MCP](https://modelcontextprotocol.io/) para que assistentes de IA — Claude Desktop, Claude Code, Cursor, ChatGPT e outros — possam ler e escrever seus dados de CRM por meio de linguagem natural.
-
-Use o **URL do espaço de trabalho** (o URL que você usa para acessar o Twenty) como o endpoint do MCP. Na Twenty Cloud, o URL do seu espaço de trabalho pode ser `https://{mycompany}.twenty.com` ou um domínio personalizado. O servidor está disponível em:
-
-| Ambiente           | Endpoint do MCP                                                                      |
-| ------------------ | ------------------------------------------------------------------------------------ |
-| **Nuvem**          | `https://{your-workspace-url}/mcp` (por exemplo, `https://mycompany.twenty.com/mcp`) |
-| **Auto-hospedado** | `https://{your-domain}/mcp`                                                          |
-
-## Métodos de autenticação
-
-Você tem duas maneiras de autenticar seu cliente MCP: **OAuth** (recomendado) ou **Chave de API**.
-
-### Opção A — OAuth (recomendado)
-
-Com o OAuth, seu cliente MCP abre uma janela do navegador para você fazer login. Nenhum segredo é armazenado em arquivos de configuração, e os tokens são atualizados automaticamente.
-
-<Note>
-O OAuth requer um cliente MCP que ofereça suporte à [especificação de Autorização MCP](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization). Claude Desktop, Claude Code, Cursor e ChatGPT oferecem suporte.
-</Note>
-
-Adicione isto à configuração do seu cliente MCP, substituindo `{your-workspace-url}` pelo host do seu espaço de trabalho (por exemplo, `mycompany.twenty.com`):
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp"
-    }
-  }
-}
-```
-
-É isso — nenhuma chave de API é necessária. Quando o cliente se conectar pela primeira vez, ele irá:
-
-1. Descobrir os metadados de OAuth do Twenty por meio de `/.well-known/oauth-protected-resource` e `/.well-known/oauth-authorization-server`
-2. Registrar-se como um cliente OAuth por meio de registro dinâmico de cliente (RFC 7591)
-3. Abrir seu navegador para autorizar o acesso
-4. Receber tokens e conectar-se ao servidor MCP
-
-Conexões subsequentes reutilizam os tokens armazenados e os atualizam automaticamente.
-
-### Opção B — Chave de API
-
-Se o seu cliente MCP não oferecer suporte a OAuth, ou se você preferir credenciais estáticas, passe uma chave de API no cabeçalho `Authorization`:
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_API_KEY"
-      }
-    }
-  }
-}
-```
-
-<Warning>
-Sua chave de API concede acesso aos dados do espaço de trabalho. Mantenha-a fora do controle de versão e de dotfiles compartilhados.
-</Warning>
-
-Para criar uma chave de API, vá em **Settings > APIs & Webhooks > + Create key**. Veja [APIs](/l/pt/developers/extend/api#create-an-api-key) para detalhes.
-
-## Início rápido
-
-### 1. Copie a configuração
-
-Vá até **Settings > AI > More > MCP Server** no Twenty. Escolha seu método de autenticação (OAuth ou Chave de API), copie o trecho de JSON (ele já usará o URL do seu espaço de trabalho) e cole-o no arquivo de configuração do seu cliente MCP.
-
-| Cliente            | Local do arquivo de configuração                                                                                                                                                   |
-| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Claude Desktop** | `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) ou `%APPDATA%\Claude\claude_desktop_config.json` (Windows)                                               |
-| **Claude Code**    | `~/.claude.json` (usuário) ou `.mcp.json` (projeto)                                                                                                                                |
-| **Cursor**         | `.cursor/mcp.json` no seu projeto, ou `~/.cursor/mcp.json` globalmente                                                                                                             |
-| **ChatGPT**        | Ative o Modo Desenvolvedor em **Settings > Apps & Connectors > Advanced settings** e, em seguida, use **Create** em **Settings > Apps & Connectors** para adicionar o servidor MCP |
-
-### 2. Conectar
-
-Reinicie seu cliente MCP (ou recarregue a configuração). Se estiver usando OAuth, você será redirecionado ao Twenty para autorizar o acesso. Se estiver usando uma chave de API, a conexão é imediata.
-
-### 3. Comece a usá-lo
-
-Peça ao seu assistente de IA para interagir com seu CRM:
-
-* *"Mostre-me as 5 empresas criadas mais recentemente"*
-* *"Crie uma nova pessoa chamada Jane Doe na Acme Corp"*
-* *"Encontre todas as oportunidades em aberto com valor superior a $10k"*
-
-## Ferramentas disponíveis
-
-Depois de conectado, o servidor MCP expõe ferramentas que refletem a API do Twenty. O fluxo de trabalho recomendado é:
-
-1. **`get_tool_catalog`** — descobrir todas as ferramentas disponíveis
-2. **`learn_tools`** — obter o esquema de entrada para ferramentas específicas
-3. **`execute_tool`** — executar uma ferramenta
-
-Você não precisa se lembrar dos nomes das ferramentas. Pergunte ao seu assistente de IA o que ele pode fazer e ele chamará `get_tool_catalog` automaticamente.
-
-## Permissões
-
-As conexões MCP herdam as permissões do usuário autenticado (OAuth) ou da função atribuída à chave de API. Para restringir o que o servidor MCP pode fazer:
-
-* **OAuth**: Aplica-se à função do espaço de trabalho do usuário.
-* **Chave de API**: Atribua uma função à chave de API em **Settings > Roles**. Veja [Permissões](/l/pt/user-guide/permissions-access/capabilities/permissions).
-
-## Configuração auto-hospedada
-
-Para instâncias auto-hospedadas, substitua `{your-workspace-url}` pelo URL do seu servidor. Certifique-se de que `SERVER_URL` no seu ambiente corresponda ao URL público da sua instância do Twenty — isso é usado para gerar os metadados de descoberta do OAuth.
-
-```bash
-SERVER_URL=https://twenty.yourcompany.com
-```
-
-O endpoint do MCP, os endpoints de OAuth e os metadados de descoberta derivam todos desse valor.
-
-## Resolução de Problemas
-
-**Erros "Unauthorized" ou 401**
-
-* OAuth: autorize novamente limpando os tokens armazenados no seu cliente MCP e reconectando.
-* Chave de API: verifique se a chave é válida e não expirou. Gere-a novamente, se necessário.
-
-**O fluxo do OAuth não abre um navegador**
-
-* Garanta que seu cliente MCP ofereça suporte à Autorização MCP. Se não oferecer, utilize o método de Chave de API.
-
-**Tempo limite de conexão**
-
-* Confirme que o URL do endpoint MCP é acessível a partir da sua máquina. Para instâncias auto-hospedadas, verifique se o servidor está em execução e se `SERVER_URL` está definido corretamente.

packages/twenty-docs/l/pt/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails.mdx

@@ -1,121 +0,0 @@
----
-title: Resposta automática a e-mails de entrada
-description: Crie um fluxo de trabalho que use IA para fazer a triagem dos e-mails de entrada e enviar respostas encadeadas automaticamente.
----
-
-Responda a e-mails de entrada em segundos — não em horas. Este fluxo de trabalho usa um Agente de IA para filtrar o ruído (boletins informativos, spam, respostas automáticas) e redigir uma resposta personalizada para mensagens reais e, em seguida, enviá-la como uma resposta encadeada dentro da conversa original.
-
-## Como funciona o encadeamento de e-mails
-
-Cada e-mail contém um cabeçalho oculto `Message-ID` — uma impressão digital única atribuída pelo servidor de e-mail do remetente. Quando você responde a um e-mail, seu cliente de e-mail define um cabeçalho `In-Reply-To` que faz referência a essa impressão digital. É assim que o Gmail, o Outlook e todos os outros clientes agrupam as mensagens em conversas.
-
-No Twenty, essa impressão digital é armazenada como `headerMessageId` no objeto Message. Seu fluxo de trabalho obtém isso e o passa para o campo In-Reply-To da ação Enviar e-mail.
-
-## Criando o fluxo de trabalho
-
-### Etapa 1: Criar um novo fluxo de trabalho
-
-Vá para **Configurações -> Fluxos de trabalho** e clique em **+ Novo fluxo de trabalho**.
-
-### Etapa 2: Acionar com mensagens recebidas
-
-Escolha **When a Record is Created** e selecione **Messages**.
-
-Sempre que um e-mail chega ao Twenty, isto é acionado.
-
-<img src="/images/user-guide/workflows/auto-reply/workflow-overview.png" style={{width:'100%'}} />
-
-### Etapa 3: Procurar quem enviou
-
-Adicione uma ação **Pesquisar Registros**.
-
-O endereço do remetente não está na própria mensagem — está no registro relacionado Message Participant.
-
-| Campo      | Valor                          |
-| ---------- | ------------------------------ |
-| **Objeto** | Participantes da Mensagem      |
-| **Filtro** | Message **é** `{{trigger.id}}` |
-| **Filtro** | Função **é** From              |
-| **Limite** | 1                              |
-
-Isso fornece o e-mail do remetente em `handle` e o nome dele em `displayName`.
-
-<img src="/images/user-guide/workflows/auto-reply/find-sender.png" style={{width:'100%'}} />
-
-### Etapa 4: Triagem por IA e rascunho de resposta
-
-Adicione uma ação **Agente de IA**. Esta única etapa faz duas coisas: decide se o e-mail merece uma resposta e, se sim, redige uma.
-
-Use um prompt como:
-
-```
-You are an email triage assistant for a sales team. Read the following
-inbound email and decide if it deserves a reply.
-
-Subject: {{trigger.subject}}
-Body: {{trigger.text}}
-From: {{Find Sender.first.displayName}} ({{Find Sender.first.handle}})
-
-If this email is spam, a newsletter, an automated notification, or
-otherwise does not need a human reply, respond with exactly: SKIP
-
-Otherwise, write a short, professional reply (3-4 sentences max) that:
-- Acknowledges their specific message
-- Lets them know someone from the team will follow up shortly
-- Is warm but not overly casual
-
-Respond with only the reply text, no subject line or greeting prefix.
-```
-
-O Agente de IA produz sua resposta em um campo `response` ao qual as próximas etapas podem se referir.
-
-<img src="/images/user-guide/workflows/auto-reply/ai-triage.png" style={{width:'100%'}} />
-
-### Etapa 5: Ramificar com base na decisão da IA
-
-Adicione uma ação **If/Else** para verificar se a IA decidiu responder ou pular.
-
-| Campo              | Valor                                              |
-| ------------------ | -------------------------------------------------- |
-| **Condição**       | A `response` do Agente de IA **não contém** `SKIP` |
-| **Se verdadeiro**  | Continuar para Enviar e-mail                       |
-| **Caso contrário** | Não fazer nada (o fluxo de trabalho termina)       |
-
-Spam, boletins informativos e mensagens geradas automaticamente são descartados. Todo o restante segue para a próxima etapa.
-
-<img src="/images/user-guide/workflows/auto-reply/should-reply.png" style={{width:'100%'}} />
-
-### Etapa 6: Enviar uma resposta encadeada
-
-Adicione uma ação **Enviar e-mail** no ramo "se verdadeiro". Clique em **Opções avançadas** e depois em **Adicionar In-Reply-To**.
-
-| Campo           | Valor                                  |
-| --------------- | -------------------------------------- |
-| **Para**        | `{{Find Sender.first.handle}}`         |
-| **Assunto**     | `Re: {{trigger.subject}}`              |
-| **Corpo**       | `{{AI Triage & Draft Reply.response}}` |
-| **In-Reply-To** | `{{trigger.headerMessageId}}`          |
-
-O campo In-Reply-To é o que faz disso uma resposta em vez de uma nova conversa. O destinatário a vê encadeada sob o e-mail original no Gmail, Outlook ou qualquer outro cliente.
-
-<img src="/images/user-guide/workflows/auto-reply/send-email.png" style={{width:'100%'}} />
-
-<Tip>
-**In-Reply-To** espera um `message.headerMessageId` do acionador — é a impressão digital única do e-mail, não um endereço do destinatário. Se você deixá-lo vazio, o e-mail ainda será enviado, apenas como uma mensagem independente.
-</Tip>
-
-<Warning>
-O Gmail usa a linha de assunto para agrupar mensagens em conversas. O assunto **deve** começar com `Re:` (incluindo os dois-pontos e o espaço) para que o Gmail exiba a resposta dentro da conversa original. Sem isso, a resposta aparecerá como uma conversa separada — mesmo que o cabeçalho In-Reply-To esteja definido corretamente.
-</Warning>
-
-### Etapa 7: Testar e ativar
-
-Clique em **Test** e, em seguida, verifique seu cliente de e-mail. A resposta deve aparecer aninhada sob a mensagem original.
-
-Ative quando estiver satisfeito com isso.
-
-## Ideias para desenvolver
-
-* **Responder apenas a VIPs** — adicione um ramo que verifique o domínio do remetente ou se ele existe como um Contato no Twenty
-* **Roteie por intenção** — use prompts separados do Agente de IA para lidar com consultas de vendas de forma diferente de solicitações de suporte
-* **Enriquecer antes de responder** — adicione uma etapa Pesquisar Registros para trazer a empresa do remetente ou o histórico de negócios para o prompt de IA, obtendo respostas mais personalizadas

packages/twenty-docs/l/ro/developers/extend/capabilities/apps.mdx

@@ -21,51 +21,19 @@ Aplicațiile vă permit să construiți și să gestionați personalizările Twe
 ## Cerințe
 
 * Node.js 24+ și Yarn 4
-* Docker (pentru serverul local de dezvoltare Twenty)
+* Un spațiu de lucru Twenty și o cheie API (creați una la https://app.twenty.com/settings/api-webhooks)
 
 ## Începeți
 
-Creează o aplicație nouă folosind generatorul oficial. Poate porni automat o instanță Twenty locală pentru tine:
+Creați o aplicație nouă folosind generatorul oficial, apoi autentificați-vă și începeți să dezvoltați:
 
 ```bash filename="Terminal"
-# Creează scheletul unei aplicații noi — CLI-ul îți va oferi opțiunea de a porni un server Twenty local
+# Creează scheletul unei aplicații noi (include toate exemplele în mod implicit)
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app
 
 # Pornește modul de dezvoltare: sincronizează automat modificările locale cu spațiul tău de lucru
-yarn twenty dev
-```
-
-### Gestionarea serverului local
-
-SDK-ul include comenzi pentru a gestiona un server local de dezvoltare Twenty (imagine Docker all-in-one cu PostgreSQL, Redis, server și worker):
-
-```bash filename="Terminal"
-# Pornește serverul local (descarcă imaginea dacă este necesar)
-yarn twenty server start
-
-# Verifică starea serverului
-yarn twenty server status
-
-# Afișează în timp real jurnalele serverului
-yarn twenty server logs
-
-# Oprește serverul
-yarn twenty server stop
-
-# Resetează toate datele și pornește de la zero
-yarn twenty server reset
-```
-
-Serverul local vine preconfigurat cu un spațiu de lucru și un utilizator (`[email protected]` / `[email protected]`), astfel încât să poți începe să dezvolți imediat, fără nicio configurare manuală.
-
-### Autentificare
-
-Conectează-ți aplicația la serverul local folosind OAuth:
-
-```bash filename="Terminal"
-# Autentifică-te prin OAuth (se deschide browserul)
-yarn twenty remote add --local
+yarn twenty app:dev
 ```
 
 Generatorul de schelet acceptă două moduri pentru a controla ce fișiere de exemplu sunt incluse:

packages/twenty-docs/l/ro/developers/self-host/capabilities/troubleshooting.mdx

@@ -167,10 +167,6 @@ plugins: [
 
 Rulați `UPDATE core."user" SET "canAccessFullAdminPanel" = TRUE WHERE email = 'tine@domeniultău.com';` în containerul de baze de date pentru a obține acces la panoul de administrare.
 
-#### Când rulați un flux de lucru, rularea fluxului de lucru eșuează cu "Execuția funcțiilor logice este dezactivată. Setați LOGIC_FUNCTION_TYPE la LOCAL sau LAMBDA pentru a le activa."
-
-În producție, funcțiile logice sunt dezactivate în mod implicit. Setați variabila de mediu `LOGIC_FUNCTION_TYPE` la `LOCAL` sau `LAMBDA` pentru a le activa. Acest lucru poate fi configurat prin variabile de mediu sau prin variabilele bazei de date din panoul de administrare. Consultați [Ghidul de configurare a funcțiilor logice](/l/ro/developers/self-host/capabilities/setup#logic-functions-available-drivers) pentru detalii.
-
 ### Docker compose cu un singur click
 
 #### Nu se poate conecta

packages/twenty-docs/l/ro/user-guide/ai/capabilities/mcp.mdx

@@ -1,142 +0,0 @@
----
-title: Server MCP
-description: Conectați asistenți AI la spațiul dvs. de lucru Twenty folosind Model Context Protocol.
----
-
-<Warning>
-MCP este în prezent în **alpha** și este disponibil doar în unele spații de lucru. Este posibil să nu fie activat încă pentru spațiul dvs. de lucru.
-</Warning>
-
-Twenty expune un server [MCP](https://modelcontextprotocol.io/) astfel încât asistenții AI — Claude Desktop, Claude Code, Cursor, ChatGPT și alții — să poată citi și scrie datele tale din CRM prin limbaj natural.
-
-Folosește **URL-ul spațiului de lucru** (URL-ul pe care îl folosești pentru a accesa Twenty) drept punct final MCP. Pe Twenty Cloud, URL-ul spațiului tău de lucru poate fi `https://{mycompany}.twenty.com` sau un domeniu personalizat. Serverul este disponibil la:
-
-| Mediu                | Punct final MCP                                                                |
-| -------------------- | ------------------------------------------------------------------------------ |
-| **Cloud**            | `https://{your-workspace-url}/mcp` (de ex. `https://mycompany.twenty.com/mcp`) |
-| **Găzduire proprie** | `https://{your-domain}/mcp`                                                    |
-
-## Metode de autentificare
-
-Ai două moduri de a-ți autentifica clientul MCP: **OAuth** (recomandat) sau **Cheie API**.
-
-### Opțiunea A — OAuth (Recomandat)
-
-Cu OAuth, clientul tău MCP deschide o fereastră de browser pentru a te autentifica. Nicio informație secretă nu este stocată în fișierele de configurare, iar tokenurile se reîmprospătează automat.
-
-<Note>
-OAuth necesită un client MCP care suportă [specificația MCP Authorization](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization). Claude Desktop, Claude Code, Cursor și ChatGPT o suportă.
-</Note>
-
-Adaugă asta în configurația clientului tău MCP, înlocuind `{your-workspace-url}` cu gazda spațiului tău de lucru (de ex. `mycompany.twenty.com`):
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp"
-    }
-  }
-}
-```
-
-Atât — nu este necesară nicio cheie API. Când clientul se conectează pentru prima dată, acesta va:
-
-1. Va descoperi metadatele OAuth ale Twenty prin `/.well-known/oauth-protected-resource` și `/.well-known/oauth-authorization-server`
-2. Se va înregistra ca un client OAuth prin înregistrare dinamică a clientului (RFC 7591)
-3. Îți va deschide browserul pentru a autoriza accesul
-4. Va primi tokenurile și se va conecta la serverul MCP
-
-Conexiunile ulterioare reutilizează tokenurile stocate și le reîmprospătează automat.
-
-### Opțiunea B — Cheie API
-
-Dacă clientul tău MCP nu suportă OAuth sau preferi acreditări statice, furnizează o cheie API în antetul `Authorization`:
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_API_KEY"
-      }
-    }
-  }
-}
-```
-
-<Warning>
-Cheia ta API oferă acces la datele spațiului de lucru. Ține-o în afara controlului versiunilor și a dotfiles partajate.
-</Warning>
-
-Pentru a crea o cheie API, mergi la **Settings > APIs & Webhooks > + Create key**. Vezi [API-uri](/l/ro/developers/extend/api#create-an-api-key) pentru detalii.
-
-## Pornire rapidă
-
-### 1. Copiază configurația
-
-Mergi la **Settings > AI > More > MCP Server** în Twenty. Alege metoda de autentificare (OAuth sau Cheie API), copiază fragmentul JSON (va folosi deja URL-ul spațiului tău de lucru) și lipește-l în fișierul de configurare al clientului tău MCP.
-
-| Client             | Locația fișierului de configurare                                                                                                                                                       |
-| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Claude Desktop** | `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) sau `%APPDATA%\Claude\claude_desktop_config.json` (Windows)                                                   |
-| **Claude Code**    | `~/.claude.json` (utilizator) sau `.mcp.json` (proiect)                                                                                                                                 |
-| **Cursor**         | `.cursor/mcp.json` în proiectul tău sau `~/.cursor/mcp.json` global                                                                                                                     |
-| **ChatGPT**        | Activează Modul pentru dezvoltatori în **Settings > Apps & Connectors > Advanced settings**, apoi folosește **Create** în **Settings > Apps & Connectors** pentru a adăuga serverul MCP |
-
-### 2. Conectează-te
-
-Repornește clientul tău MCP (sau reîncarcă configurația). Dacă folosești OAuth, vei fi redirecționat către Twenty pentru a autoriza accesul. Dacă folosești o cheie API, conexiunea este imediată.
-
-### 3. Începe să-l folosești
-
-Roagă-ți asistentul AI să interacționeze cu CRM-ul tău:
-
-* *"Arată-mi cele 5 companii create cel mai recent"*
-* *"Creează o persoană nouă numită Jane Doe la Acme Corp"*
-* *"Găsește toate oportunitățile deschise cu o valoare mai mare de $10k"*
-
-## Instrumente disponibile
-
-După conectare, serverul MCP expune instrumente care oglindesc API-ul Twenty. Fluxul de lucru recomandat este:
-
-1. **`get_tool_catalog`** — descoperă toate instrumentele disponibile
-2. **`learn_tools`** — obține schema de intrare pentru instrumente specifice
-3. **`execute_tool`** — rulează un instrument
-
-Nu este nevoie să reții numele instrumentelor. Întreabă-ți asistentul AI ce poate face și va apela `get_tool_catalog` automat.
-
-## Permisiuni
-
-Conexiunile MCP moștenesc permisiunile utilizatorului autentificat (OAuth) sau rolul atribuit cheii API. Pentru a restricționa ce poate face serverul MCP:
-
-* **OAuth**: Se aplică rolul utilizatorului din spațiul de lucru.
-* **Cheie API**: Atribuie un rol cheii API în **Settings > Roles**. Vezi [Permisiuni](/l/ro/user-guide/permissions-access/capabilities/permissions).
-
-## Configurație pentru auto-găzduire
-
-Pentru instanțele auto-găzduite, înlocuiește `{your-workspace-url}` cu URL-ul serverului tău. Asigură-te că `SERVER_URL` din mediul tău corespunde URL-ului public al instanței tale Twenty — acesta este folosit pentru a genera metadatele de descoperire OAuth.
-
-```bash
-SERVER_URL=https://twenty.yourcompany.com
-```
-
-Punctul final MCP, punctele finale OAuth și metadatele de descoperire derivă toate din această valoare.
-
-## Depanare
-
-**Erori "Unauthorized" sau 401**
-
-* OAuth: reautorizează ștergând tokenurile stocate din clientul tău MCP și reconectează-te.
-* Cheie API: verifică dacă cheia este validă și nu a expirat. Regenereaz-o dacă este necesar.
-
-**Fluxul OAuth nu deschide un browser**
-
-* Asigură-te că clientul tău MCP suportă MCP Authorization. Dacă nu, revino la metoda cu Cheie API.
-
-**Timeout de conexiune**
-
-* Confirmă că URL-ul punctului final MCP este accesibil de pe calculatorul tău. Pentru instanțele auto-găzduite, verifică faptul că serverul rulează și că `SERVER_URL` este setat corect.

packages/twenty-docs/l/ro/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails.mdx

@@ -1,121 +0,0 @@
----
-title: Răspuns automat la e-mailurile primite
-description: Creează un flux de lucru care folosește IA pentru a tria e-mailurile primite și pentru a trimite automat răspunsuri în același fir.
----
-
-Răspunde la e-mailurile primite în câteva secunde — nu în ore. Acest flux de lucru folosește un Agent IA pentru a filtra zgomotul (newslettere, spam, răspunsuri automate) și pentru a redacta un răspuns personalizat la mesajele reale, apoi îl trimite ca răspuns în același fir, în cadrul conversației originale.
-
-## Cum funcționează firele de e-mail
-
-Fiecare e-mail are un antet ascuns `Message-ID` — o amprentă unică atribuită de serverul de e-mail al expeditorului. Când răspundeți la un e-mail, clientul dvs. de e-mail setează un antet `In-Reply-To` care face referire la acea amprentă. Astfel, Gmail, Outlook și orice alt client grupează mesajele în fire de discuție.
-
-În Twenty, acea amprentă este stocată ca `headerMessageId` pe obiectul Message. Fluxul dvs. de lucru o preia și o transmite în câmpul In-Reply-To al acțiunii Send Email.
-
-## Construirea fluxului de lucru
-
-### Pasul 1: Creați un flux de lucru nou
-
-Accesați **Settings -> Workflows** și faceți clic pe **+ New Workflow**.
-
-### Pasul 2: Declanșare la mesajele primite
-
-Alegeți **When a Record is Created** și selectați **Messages**.
-
-De fiecare dată când un e-mail ajunge în Twenty, aceasta se declanșează.
-
-<img src="/images/user-guide/workflows/auto-reply/workflow-overview.png" style={{width:'100%'}} />
-
-### Pasul 3: Căutați cine l-a trimis
-
-Adăugați o acțiune **Search Records**.
-
-Adresa expeditorului nu este în mesajul propriu-zis — se găsește în înregistrarea asociată Message Participant.
-
-| Câmp       | Valoare                           |
-| ---------- | --------------------------------- |
-| **Obiect** | Participanți la mesaj             |
-| **Filtru** | Mesajul **este** `{{trigger.id}}` |
-| **Filtru** | Rolul **este** From               |
-| **Limită** | 1                                 |
-
-Aceasta vă oferă e-mailul expeditorului în `handle` și numele acestuia în `displayName`.
-
-<img src="/images/user-guide/workflows/auto-reply/find-sender.png" style={{width:'100%'}} />
-
-### Pasul 4: Triere cu AI și redactarea răspunsului
-
-Adăugați o acțiune **AI Agent**. Acest singur pas face două lucruri: decide dacă e-mailul merită un răspuns și, dacă da, redactează unul.
-
-Folosiți un prompt de tipul:
-
-```
-You are an email triage assistant for a sales team. Read the following
-inbound email and decide if it deserves a reply.
-
-Subject: {{trigger.subject}}
-Body: {{trigger.text}}
-From: {{Find Sender.first.displayName}} ({{Find Sender.first.handle}})
-
-If this email is spam, a newsletter, an automated notification, or
-otherwise does not need a human reply, respond with exactly: SKIP
-
-Otherwise, write a short, professional reply (3-4 sentences max) that:
-- Acknowledges their specific message
-- Lets them know someone from the team will follow up shortly
-- Is warm but not overly casual
-
-Respond with only the reply text, no subject line or greeting prefix.
-```
-
-AI Agent produce răspunsul în câmpul `response`, la care pot face referire pașii următori.
-
-<img src="/images/user-guide/workflows/auto-reply/ai-triage.png" style={{width:'100%'}} />
-
-### Pasul 5: Ramificați în funcție de decizia AI
-
-Adăugați o acțiune **If/Else** pentru a verifica dacă AI a decis să răspundă sau să o omită.
-
-| Câmp                   | Valoare                                      |
-| ---------------------- | -------------------------------------------- |
-| **Condiție**           | AI Agent `response` **nu conține** `SKIP`    |
-| **Dacă este adevărat** | Continuați la Send Email                     |
-| **Altfel**             | Nu faceți nimic (fluxul de lucru se încheie) |
-
-Spam-ul, buletinele informative și mesajele generate automat sunt ignorate. Tot restul trece la pasul următor.
-
-<img src="/images/user-guide/workflows/auto-reply/should-reply.png" style={{width:'100%'}} />
-
-### Pasul 6: Trimiteți un răspuns în același fir
-
-Adăugați o acțiune **Send Email** pe ramura "if true". Faceți clic pe **Advanced options**, apoi pe **Add In-Reply-To**.
-
-| Câmp            | Valoare                                |
-| --------------- | -------------------------------------- |
-| **Către**       | `{{Find Sender.first.handle}}`         |
-| **Subiect**     | `Re: {{trigger.subject}}`              |
-| **Body**        | `{{AI Triage & Draft Reply.response}}` |
-| **In-Reply-To** | `{{trigger.headerMessageId}}`          |
-
-Câmpul In-Reply-To este cel care face ca acesta să fie un răspuns, nu o conversație nouă. Destinatarul îl vede afișat în fir sub e-mailul original în Gmail, Outlook sau orice alt client.
-
-<img src="/images/user-guide/workflows/auto-reply/send-email.png" style={{width:'100%'}} />
-
-<Tip>
-**In-Reply-To** necesită un `message.headerMessageId` din declanșator — este amprenta unică a e-mailului, nu o adresă a destinatarului. Dacă îl lăsați necompletat, e-mailul se trimite în continuare, doar ca un mesaj independent.
-</Tip>
-
-<Warning>
-Gmail folosește subiectul pentru a grupa mesajele în fire de discuție. Subiectul **trebuie** să înceapă cu `Re:` (inclusiv două puncte și spațiu) pentru ca Gmail să afișeze răspunsul în cadrul firului original. Fără acesta, răspunsul va apărea ca o conversație separată — chiar dacă antetul In-Reply-To este setat corect.
-</Warning>
-
-### Pasul 7: Testați și activați
-
-Apăsați **Test**, apoi verificați clientul de e-mail. Răspunsul ar trebui să apară sub mesajul original.
-
-Activați când sunteți mulțumit(ă) de rezultat.
-
-## Idei pe care să le dezvoltați
-
-* **Răspundeți doar VIP-urilor** — adăugați o ramură care verifică domeniul expeditorului sau dacă acesta există ca Contact în Twenty
-* **Dirijați în funcție de intenție** — folosiți prompturi AI Agent separate pentru a trata diferit solicitările de vânzări față de cererile de asistență
-* **Îmbogățiți înainte de a răspunde** — adăugați un pas Search Records pentru a include compania expeditorului sau istoricul tranzacțiilor în promptul AI, pentru răspunsuri mai personalizate