langgenius · Yevanchen · Sep 1, 2026 · Sep 1, 2026
diff --git a/content/docs/en/cli/overview.mdx b/content/docs/en/cli/overview.mdx
@@ -39,7 +39,7 @@ printf '%s' "$MOSOO_API_TOKEN" | \
 ```bash
 mosoo --help
 mosoo commands --json
-mosoo commands show console apps deploy-app
+mosoo commands show console environments create-environment
 mosoo search "create environment"
 ```
 
@@ -60,12 +60,6 @@ mosoo run \
 
 # Create an Environment from the project context or explicit flags
 mosoo console environments create-environment
-
-# Deploy a public GitHub repository
-mosoo console apps deploy-app \
-  --input-app-id <app-id> \
-  --input-repo-url https://github.com/owner/repository \
-  --wait
 ```
 
 Use `--target local|cloud|custom`, `--base-url`, or `--hostname` to control endpoint resolution. Output formats are `table`, `json`, `yaml`, and `raw`.

diff --git a/content/docs/en/concepts.mdx b/content/docs/en/concepts.mdx
@@ -7,7 +7,7 @@ mosoo is an open-source agent runtime for coding agents. It runs Claude Agent SD
 
 ## Apps are isolation boundaries
 
-An App keeps its Agents, files, configuration resources, deployment, and usage separate. Switching Apps changes the resources visible in the console. The current Alpha is single-owner: organization team roles, invitations, and ownership transfer are not available.
+An App keeps its Agents, files, configuration resources, and usage separate. Switching Apps changes the resources visible in the console. The current Alpha is single-owner: organization team roles, invitations, and ownership transfer are not available.
 
 ## Agent types control continuity
 

diff --git a/content/docs/en/deploy-app.mdx b/content/docs/en/deploy-app.mdx
diff --git a/content/docs/en/deploy-mosoo.mdx b/content/docs/en/deploy-mosoo.mdx
@@ -3,7 +3,7 @@ title: "Deploy mosoo on Cloudflare"
 description: "Deploy mosoo with Cloudflare Workers from GitHub Actions or a local Wrangler toolchain."
 ---
 
-mosoo runs as two Cloudflare Workers: an API Worker backed by D1, R2, Queues, Durable Objects, and Containers, plus a Web Worker that serves the console and binds to the API service. It is not a standalone Cloudflare Pages site.
+mosoo runs as two Cloudflare Workers: an API Worker backed by D1, R2, Queues, Durable Objects, and Containers, plus a Web Worker that serves the console and binds to the API service.
 
 This guide covers the two deployment paths used by the reference deployment:
 
@@ -15,17 +15,17 @@ Both paths use `apps/api/wrangler.toml`, `apps/web/wrangler.toml`, and the repos
 ## Prerequisites
 
 - A Cloudflare account with Workers, D1, R2, Queues, Durable Objects, and Containers available.
-- A domain in Cloudflare DNS, such as `console.example.com`, plus a deployment subdomain such as `apps.example.com` if you enable App Deployment.
+- A domain in Cloudflare DNS, such as `console.example.com`.
 - Git, Docker, [Bun](https://bun.sh/), [just](https://just.systems/), and the repository submodules.
 - A Cloudflare API token with the account and zone permissions required to deploy the resources above. Keep tokens and secret values outside Git. Use the least privilege that covers the operations below.
 
 | Scope | Required operations |
 | --- | --- |
-| Account | Workers scripts, versions, deployments, custom domains, and Containers; D1 migrations; R2; Queues; and, when App Deployment is enabled, Pages projects and domains |
-| Zone selected by `CLOUDFLARE_ZONE_ID` | Workers Routes changes for the App Deployment domain |
-| R2 S3 credentials | Read and write the sandbox-state bucket used by deployed apps |
+| Account | Workers scripts, versions, deployments, custom domains, and Containers; D1 migrations; R2; Queues |
+| Zone that owns the console domain | Workers Routes changes for the `<console-domain>/api/*` API route |
+| R2 S3 credentials | Read and write the sandbox-state bucket used for Agent runtime backups |
 
-`CLOUDFLARE_ZONE_ID` must identify the zone that owns `MOSOO_APP_DEPLOYMENT_DOMAIN`. Cloudflare's token labels can change; verify that the token permits these exact API operations rather than granting account-wide administrator access.
+Cloudflare's token labels can change; verify that the token permits these exact API operations rather than granting account-wide administrator access.
 
 Clone your fork and install the pinned dependencies:
 
@@ -80,7 +80,6 @@ Edit the `[env.prod]` sections in both Wrangler files. At minimum:
 
 1. In `apps/api/wrangler.toml`:
    - set `WEB_ORIGIN` to the public HTTPS console URL;
-   - set `MOSOO_APP_DEPLOYMENT_DOMAIN` to the deployment domain;
    - set the API route to `<console-domain>/api/*` and its `zone_name`;
    - set the D1 `database_id` returned by `wrangler d1 create`;
    - update D1, R2, and Queue names if you did not use the defaults;
@@ -94,7 +93,6 @@ For example, the routing shape is:
 ```text
 https://console.example.com/*      -> Web Worker
 https://console.example.com/api/*  -> API Worker
-https://*.apps.example.com/*       -> Apps published by mosoo, when enabled
 ```
 
 Choose names that are unused in each resource's Cloudflare namespace. Workers, D1 databases, Queues, R2 buckets, and hostnames have different naming and uniqueness rules. Do not copy database IDs, account IDs, zone IDs, or hostnames from another deployment.
@@ -109,12 +107,10 @@ The current production configuration requires these API Worker secrets:
 - `R2_ACCESS_KEY_ID`
 - `R2_SECRET_ACCESS_KEY`
 - `CLOUDFLARE_ACCOUNT_ID`
-- `CLOUDFLARE_API_TOKEN`
-- `CLOUDFLARE_ZONE_ID`
 - `GOOGLE_OAUTH_CLIENT_ID`
 - `GOOGLE_OAUTH_CLIENT_SECRET`
 
-Generate independent random values for the first three secrets. Create R2 S3 credentials and the Cloudflare API token in the Cloudflare dashboard. Configure the Google OAuth client with the public mosoo origin and the exact callback URL `https://console.example.com/api/auth/callback/google`, replacing the example domain with `WEB_ORIGIN`.
+Generate independent random values for the first three secrets. Copy the account ID and create the R2 S3 credentials in the Cloudflare dashboard. Configure the Google OAuth client with the public mosoo origin and the exact callback URL `https://console.example.com/api/auth/callback/google`, replacing the example domain with `WEB_ORIGIN`.
 
 Store each value with Wrangler; do not add it to `wrangler.toml` or a committed `.env` file:
 

diff --git a/content/docs/en/import-export-versions.mdx b/content/docs/en/import-export-versions.mdx
@@ -23,8 +23,7 @@ A `.agent` package is not an App backup or running-state snapshot. It does not c
 
 - Provider or MCP credentials;
 - conversations, logs, or usage history;
-- live runtime state or working files;
-- App deployment history.
+- live runtime state or working files.
 
 Reconnect external services and reselect missing Environment or secret values in the destination App.
 

diff --git a/content/docs/en/index.mdx b/content/docs/en/index.mdx
@@ -22,7 +22,6 @@ mosoo gives you one workspace to configure AI Agents, test them against real tas
 ## Publish and operate
 
 - [Publish the Agent and enable API access](/docs/publish-and-api-access).
-- [Deploy a supported public App](/docs/deploy-app).
 - Track [Runs, files, and usage](/docs/operations).
 - Reuse setup through [import, export, fork, and version history](/docs/import-export-versions).
 

diff --git a/content/docs/en/meta.json b/content/docs/en/meta.json
@@ -16,7 +16,6 @@
     "test-and-debug",
     "---Publish and operate---",
     "publish-and-api-access",
-    "deploy-app",
     "operations",
     "import-export-versions",
     "use-cases",

diff --git a/content/docs/en/product-tour.mdx b/content/docs/en/product-tour.mdx
@@ -3,16 +3,14 @@ title: "Product tour"
 description: "Understand how Organizations, Apps, Agents, and runs fit together in mosoo."
 ---
 
-mosoo is a managed workspace for building, running, publishing, and operating AI Agents. You configure an Agent once, test it in the console, then make it available through a Thread, an API endpoint, or an App deployment.
-
-![The App Overview connects Agent setup, CLI onboarding, and deployment.](/docs/images/product/app-overview.png)
+mosoo is a managed workspace for building, running, publishing, and operating AI Agents. You configure an Agent once, test it in the console, then use it through a Thread or an API endpoint.
 
 ## The product model
 
 | Resource | What it owns |
 | --- | --- |
 | **Organization** | Your account-level container. The current product is a single-owner experience; team roles and invitations are not available. |
-| **App** | The engineering and delivery boundary for Agents, files, configuration, usage, and one optional deployed site. A new account starts with a Default App. |
+| **App** | The isolation boundary for Agents, files, configuration, and usage. A new account starts with a Default App. |
 | **Agent** | A reusable worker with a type, runtime, model, instructions, Skills, MCP connections, and an Environment. |
 | **Thread** | The durable conversation and work record for one Agent. Replies can resume work asynchronously. |
 | **Run** | One execution inside a Thread. Runs produce events, logs, usage, and files. |
@@ -25,7 +23,7 @@ mosoo is a managed workspace for building, running, publishing, and operating AI
 4. Configure its identity, instructions, Skills, MCP servers, and Environment.
 5. Test in **Preview**; inspect **Logs**, **Cost**, and **Terminal** when applicable.
 6. Publish the Agent.
-7. Start Threads in mosoo, enable API access, or bind the Agent to a deployed App.
+7. Start Threads in mosoo or enable API access.
 8. Monitor Runs, files, versions, and usage.
 
 <Callout type="info">

diff --git a/content/docs/en/use-cases.mdx b/content/docs/en/use-cases.mdx
@@ -35,4 +35,4 @@ Use these patterns as starting points, then test with your own data and failure
 
 ## Public application
 
-Publish the Agent, then use the Public Thread API from your backend. If you also need a simple website, App Deployment can publish one supported public repository and bind Agent access. It is not a general backend, authentication, scheduling, or custom-domain platform.
+Publish the Agent, then use the Public Thread API from your backend to create or resume a Thread for each application user.
diff --git a/content/docs/ja/cli/overview.mdx b/content/docs/ja/cli/overview.mdx
@@ -39,7 +39,7 @@ printf '%s' "$MOSOO_API_TOKEN" | \
 ```bash
 mosoo --help
 mosoo commands --json
-mosoo commands show console apps deploy-app
+mosoo commands show console environments create-environment
 mosoo search "create environment"
 ```
 
@@ -60,12 +60,6 @@ mosoo run \
 
 # project context または明示した flag から Environment を作成
 mosoo console environments create-environment
-
-# public GitHub repository をデプロイ
-mosoo console apps deploy-app \
-  --input-app-id <app-id> \
-  --input-repo-url https://github.com/owner/repository \
-  --wait
 ```
 
 endpoint resolution は `--target local|cloud|custom`、`--base-url`、`--hostname` で制御します。output format は `table`、`json`、`yaml`、`raw` です。

diff --git a/content/docs/ja/concepts.mdx b/content/docs/ja/concepts.mdx
@@ -7,7 +7,7 @@ mosoo は Coding Agent 向けのオープンソース Agent runtime です。Cla
 
 ## App は分離の境界
 
-App は Agent、ファイル、設定リソース、デプロイ、使用量を分離します。App を切り替えると console に表示されるリソースも変わります。現在の Alpha は単一オーナー向けであり、Organization のチームロール、招待、所有権移管は利用できません。
+App は Agent、ファイル、設定リソース、使用量を分離します。App を切り替えると console に表示されるリソースも変わります。現在の Alpha は単一オーナー向けであり、Organization のチームロール、招待、所有権移管は利用できません。
 
 ## Agent タイプは継続性を決める
 

diff --git a/content/docs/ja/deploy-app.mdx b/content/docs/ja/deploy-app.mdx
diff --git a/content/docs/ja/deploy-mosoo.mdx b/content/docs/ja/deploy-mosoo.mdx
@@ -3,7 +3,7 @@ title: "Cloudflare に mosoo をデプロイ"
 description: "GitHub Actions またはローカルの Wrangler toolchain から Cloudflare Workers に mosoo をデプロイします。"
 ---
 
-mosoo は二つの Cloudflare Worker として動作します。一つは D1、R2、Queues、Durable Objects、Containers を使用する API Worker、もう一つは console を配信し API service に binding する Web Worker です。単体の Cloudflare Pages site ではありません。
+mosoo は二つの Cloudflare Worker として動作します。一つは D1、R2、Queues、Durable Objects、Containers を使用する API Worker、もう一つは console を配信し API service に binding する Web Worker です。
 
 このガイドでは、reference deployment で使用する二つの方法を説明します。
 
@@ -15,17 +15,17 @@ mosoo は二つの Cloudflare Worker として動作します。一つは D1、R
 ## 前提条件
 
 - Workers、D1、R2、Queues、Durable Objects、Containers が利用可能な Cloudflare account。
-- Cloudflare DNS にある `console.example.com` などの domain。App Deployment を有効にする場合は `apps.example.com` などの deployment subdomain も必要です。
+- Cloudflare DNS にある `console.example.com` などの domain。
 - Git、Docker、[Bun](https://bun.sh/)、[just](https://just.systems/)、repository submodule。
 - 上記 resource のデプロイに必要な account と zone permission を持つ Cloudflare API token。token と secret value は Git の外に保管し、以下の操作に必要な最小権限を使用してください。
 
 | Scope | 必要な操作 |
 | --- | --- |
-| Account | Workers script、version、deployment、custom domain、Containers、D1 migration、R2、Queues。App Deployment を有効にする場合は Pages project と domain も必要です。 |
-| `CLOUDFLARE_ZONE_ID` で選択する Zone | App Deployment domain に対する Workers Routes の変更。 |
-| R2 S3 credential | deployed app が使用する sandbox-state bucket の読み書き。 |
+| Account | Workers script、version、deployment、custom domain、Containers、D1 migration、R2、Queues。 |
+| Console domain を所有する Zone | `<console-domain>/api/*` API route に対する Workers Routes の変更。 |
+| R2 S3 credential | Agent runtime backup が使用する sandbox-state bucket の読み書き。 |
 
-`CLOUDFLARE_ZONE_ID` は `MOSOO_APP_DEPLOYMENT_DOMAIN` を所有する zone を指定する必要があります。Cloudflare の token label は変わることがあるため、account 全体の administrator 権限を付与するのではなく、上記の API operation が許可されていることを確認してください。
+Cloudflare の token label は変わることがあるため、account 全体の administrator 権限を付与するのではなく、上記の API operation が許可されていることを確認してください。
 
 fork を clone し、固定された dependency を install します。
 
@@ -80,7 +80,6 @@ resource 名を変更した場合は、`apps/api/wrangler.toml` にある対応
 
 1. `apps/api/wrangler.toml`:
    - `WEB_ORIGIN` を公開 HTTPS console URL に設定。
-   - `MOSOO_APP_DEPLOYMENT_DOMAIN` を deployment domain に設定。
    - API route を `<console-domain>/api/*` に設定し、その `zone_name` を指定。
    - `wrangler d1 create` が返した D1 `database_id` を設定。
    - default を使用しなかった場合は D1、R2、Queue 名を更新。
@@ -94,7 +93,6 @@ resource 名を変更した場合は、`apps/api/wrangler.toml` にある対応
 ```text
 https://console.example.com/*      -> Web Worker
 https://console.example.com/api/*  -> API Worker
-https://*.apps.example.com/*       -> Apps published by mosoo, when enabled
 ```
 
 Cloudflare の各 resource namespace で未使用の名前を選びます。Workers、D1 database、Queue、R2 bucket、hostname にはそれぞれ異なる命名規則と一意性の要件があります。別の deployment の database ID、account ID、zone ID、hostname をコピーしないでください。
@@ -109,12 +107,10 @@ Cloudflare の各 resource namespace で未使用の名前を選びます。Work
 - `R2_ACCESS_KEY_ID`
 - `R2_SECRET_ACCESS_KEY`
 - `CLOUDFLARE_ACCOUNT_ID`
-- `CLOUDFLARE_API_TOKEN`
-- `CLOUDFLARE_ZONE_ID`
 - `GOOGLE_OAUTH_CLIENT_ID`
 - `GOOGLE_OAUTH_CLIENT_SECRET`
 
-最初の三つにはそれぞれ独立した random value を生成します。R2 S3 credential と Cloudflare API token は Cloudflare dashboard で作成します。Google OAuth client には公開 mosoo origin と正確な callback URL `https://console.example.com/api/auth/callback/google` を設定し、example domain は `WEB_ORIGIN` に置き換えてください。
+最初の三つにはそれぞれ独立した random value を生成します。Cloudflare dashboard で account ID を確認し、R2 S3 credential を作成します。Google OAuth client には公開 mosoo origin と正確な callback URL `https://console.example.com/api/auth/callback/google` を設定し、example domain は `WEB_ORIGIN` に置き換えてください。
 
 各 value は Wrangler で保存し、`wrangler.toml` や commit 対象の `.env` file には追加しないでください。
 

diff --git a/content/docs/ja/import-export-versions.mdx b/content/docs/ja/import-export-versions.mdx
@@ -24,7 +24,6 @@ Agent settings を開いて **Fork agent** を選択します。fork は同じ A
 - Provider または MCP credential。
 - conversation、ログ、使用履歴。
 - live runtime state または作業ファイル。
-- App deployment history。
 
 移行先 App で外部 service を再接続し、見つからない Environment や secret value を再選択してください。
Original file line number	Diff line number	Diff line change
Expand Up		@@ -35,4 +35,4 @@ Use these patterns as starting points, then test with your own data and failure

		## Public application

		Publish the Agent, then use the Public Thread API from your backend. If you also need a simple website, App Deployment can publish one supported public repository and bind Agent access. It is not a general backend, authentication, scheduling, or custom-domain platform.
		Publish the Agent, then use the Public Thread API from your backend to create or resume a Thread for each application user.