feat: experimental dynamic workflows — runtime, TUI, SDK, mode, autocomplete, docs

.changeset/add-langsearch-web-search.md

@@ -0,0 +1,5 @@
+---
+"@moonshot-ai/kimi-code": minor
+---
+
+Add configurable LangSearch web search and optional semantic reranking. Configure it under Settings → Web Search or with `kimi search`.

.changeset/dynamic-workflows.md

@@ -0,0 +1,7 @@
+---
+"@moonshot-ai/kimi-code": minor
+---
+
+Add experimental dynamic workflows: multi-phase subagent orchestration from user-approved JS scripts, with background runs, progress tracking, cancellation, and project/user-level reuse. Enable with KIMI_CODE_EXPERIMENTAL_DYNAMIC_WORKFLOWS=1, then run /workflow.
+
+Also add the `/workflow on|off` mode that instructs the agent to propose dynamic workflows for large tasks, dynamic argument autocomplete listing available workflows after `/workflow run`, a `wf` mode badge in the footer, and workflow visibility in the `/tasks` browser.

.gitignore

@@ -32,7 +32,8 @@ docs/superpowers/
 reports/
 .superpowers/
 /plan/
-
+app-kimi/
+app-gpt/
 # Agent scratch / throwaway files - do not commit
 .tmp/
 HANDOVER*.md

.oxlintrc.json

@@ -142,6 +142,14 @@
         "vitest/no-standalone-expect": "error",
         "vitest/warn-todo": "off"
       }
+    },
+    {
+      "files": ["scripts/use-personal-build.mjs"],
+      "rules": {
+        "eslint/no-console": "off",
+        "unicorn/prefer-top-level-await": "off",
+        "unicorn/prefer-import-meta-properties": "off"
+      }
     }
   ],
   "ignorePatterns": [

PERSONAL_BUILD.md

@@ -0,0 +1,73 @@
+# Build pessoal do Kimi Code
+
+Este guia explica como compilar e usar o Kimi Code diretamente da source deste fork, sem depender do binário oficial da Moonshot.
+
+## Quando usar
+
+- Você quer rodar sua própria build a partir da branch `personal`.
+- Você quer que o comando `kimi` aponte sempre para o executável gerado neste repositório.
+- Você quer evitar que o atualizador oficial substitua seu binário personalizado.
+
+## Pré-requisitos
+
+- Node.js `>= 24.15.0`
+- pnpm `10.33.0` (o repositório usa `corepack`)
+- Sistema: Linux x64 ou Windows x64
+
+## Comando principal
+
+Na raiz do repositório, na branch `personal`:
+
+```bash
+node scripts/use-personal-build.mjs
+```
+
+O script vai:
+
+1. Validar Node.js, pnpm e plataforma.
+2. Instalar dependências (`pnpm install --frozen-lockfile`).
+3. Compilar os assets web.
+4. Compilar o executável nativo SEA (`build:native:sea`).
+5. Rodar o smoke test nativo.
+6. Substituir `~/.kimi-code/bin/kimi` por um launcher que aponta para o binário deste clone.
+7. Desativar atualizações oficiais via `KIMI_CODE_NO_AUTO_UPDATE=1`.
+8. Garantir que `~/.kimi-code/bin` esteja no PATH.
+
+## Dry run
+
+Para ver o que seria feito sem alterar nada:
+
+```bash
+node scripts/use-personal-build.mjs --dry-run
+```
+
+## Atualizar depois de puxar do upstream
+
+```bash
+git fetch upstream
+git rebase upstream/main   # ou merge, se preferir
+node scripts/use-personal-build.mjs
+```
+
+## Usar em outro computador
+
+1. Clone este fork e entre na branch `personal`.
+2. Instale Node.js `>= 24.15.0` e ative o corepack:
+   ```bash
+   corepack enable
+   corepack prepare pnpm@10.33.0 --activate
+   ```
+3. Rode:
+   ```bash
+   node scripts/use-personal-build.mjs
+   ```
+
+Suas configurações (`~/.kimi-code/config.toml`), credenciais, sessões e plugins serão preservadas.
+
+## Por que não `pnpm build`?
+
+O comando `pnpm build` do root compila pacotes e assets, mas **não gera o executável nativo SEA**. Para produzir o binário `kimi`/`kimi.exe` é necessário rodar `build:native:sea`, que é exatamente o que o script `use-personal-build.mjs` faz, seguindo o mesmo fluxo do workflow oficial de release nativa.
+
+## Windows
+
+No Windows o script remove `~/.kimi-code/bin/kimi.exe` e cria `~/.kimi-code/bin/kimi.cmd` apontando para o `.exe` gerado no clone. A atualização do PATH é feita via PowerShell. Abra um novo terminal após rodar o script.

apps/kimi-code/scripts/native/01-bundle.mjs

@@ -1,5 +1,6 @@
 import { createRequire } from 'node:module';
 import { resolve } from 'node:path';
+import { pathToFileURL } from 'node:url';
 
 import { run } from './exec.mjs';
 
@@ -18,6 +19,6 @@ export async function runBundleStep() {
   await run(process.execPath, [checkBundlePath]);
 }
 
-if (import.meta.url === `file://${process.argv[1]}`) {
+if (process.argv[1] !== undefined && import.meta.url === pathToFileURL(process.argv[1]).href) {
   await runBundleStep();
 }

apps/kimi-code/scripts/native/03-inject.mjs

@@ -1,4 +1,4 @@
-import { copyFile, mkdir, stat } from 'node:fs/promises';
+import { copyFile, mkdir, rm, stat } from 'node:fs/promises';
 import { resolve } from 'node:path';
 
 import { fail, run, tryRun } from './exec.mjs';
@@ -27,6 +27,10 @@ async function ensureBlobExists() {
 async function copyNodeExecutable(target) {
   await mkdir(nativeBinDir(target), { recursive: true });
   const out = nativeBinPath(target);
+  // Unlink first: overwriting a currently-running binary fails with ETXTBSY on
+  // Linux. Removing the path detaches the running process from it (it keeps
+  // the old inode), so the fresh copy can be written.
+  await rm(out, { force: true });
   await copyFile(process.execPath, out);
   if (process.platform !== 'win32') {
     await run('chmod', ['755', out]);

apps/kimi-code/src/cli/commands.ts

@@ -8,6 +8,7 @@ import { registerDoctorCommand } from './sub/doctor';
 import { registerExportCommand } from './sub/export';
 import { registerLoginCommand } from './sub/login';
 import { registerProviderCommand } from './sub/provider';
+import { registerSearchCommand } from './sub/search';
 import { registerVisCommand } from './sub/vis';
 import { registerWebCommand } from './sub/web';
 
@@ -115,6 +116,7 @@ export function createProgram(
 
   registerExportCommand(program);
   registerProviderCommand(program);
+  registerSearchCommand(program);
   registerAcpCommand(program);
   registerWebCommand(program);
   registerLoginCommand(program);