specrails-desktop 2.58.1 → 2.59.1

package/client/dist/index.html

@@ -204,58 +204,60 @@
         .specrails-splash__mark .pill { opacity: 1; }
       }
     </style>
-    <script type="module" crossorigin src="/assets/index-C4Mv6tV6.js"></script>
+    <script type="module" crossorigin src="/assets/index-Czov72g7.js"></script>
     <link rel="modulepreload" crossorigin href="/assets/rolldown-runtime-CNC7AqOf.js">
     <link rel="modulepreload" crossorigin href="/assets/jsx-runtime-zu2_FqZY.js">
     <link rel="modulepreload" crossorigin href="/assets/react-dom-DiWzBDP9.js">
     <link rel="modulepreload" crossorigin href="/assets/preload-helper-Czpn1I53.js">
     <link rel="modulepreload" crossorigin href="/assets/chunk-KS7C4IRE-DEKu087k.js">
+    <link rel="modulepreload" crossorigin href="/assets/tauri-shell-DE6LfGPw.js">
     <link rel="modulepreload" crossorigin href="/assets/activity-DiyjsgQV.js">
     <link rel="modulepreload" crossorigin href="/assets/addspec-BOvgmcgk.js">
-    <link rel="modulepreload" crossorigin href="/assets/agent-aiVhqFW1.js">
-    <link rel="modulepreload" crossorigin href="/assets/agentRuntime-BeUb3g9g.js">
+    <link rel="modulepreload" crossorigin href="/assets/agent-Z5s_GTP0.js">
+    <link rel="modulepreload" crossorigin href="/assets/agentRuntime-Bpx3yWHK.js">
     <link rel="modulepreload" crossorigin href="/assets/agents-CTwbx-fb.js">
     <link rel="modulepreload" crossorigin href="/assets/agentstudio-BWAKeGgB.js">
     <link rel="modulepreload" crossorigin href="/assets/aiedit-iIjz2_Qk.js">
     <link rel="modulepreload" crossorigin href="/assets/analytics-BWynXPEm.js">
     <link rel="modulepreload" crossorigin href="/assets/attachments-B53PG733.js">
     <link rel="modulepreload" crossorigin href="/assets/browser-CG0PE1j_.js">
-    <link rel="modulepreload" crossorigin href="/assets/builder-CzW5ovyI.js">
+    <link rel="modulepreload" crossorigin href="/assets/builder-CpS9liE9.js">
     <link rel="modulepreload" crossorigin href="/assets/chat-BGD7MXAy.js">
     <link rel="modulepreload" crossorigin href="/assets/code-DaZ-ZwCT.js">
     <link rel="modulepreload" crossorigin href="/assets/commands-BAWSYHjQ.js">
-    <link rel="modulepreload" crossorigin href="/assets/common-DmsclwjP.js">
+    <link rel="modulepreload" crossorigin href="/assets/common-Bdi0qN4S.js">
     <link rel="modulepreload" crossorigin href="/assets/dashboard-XGdQ5mjw.js">
     <link rel="modulepreload" crossorigin href="/assets/explore-DgBACn39.js">
-    <link rel="modulepreload" crossorigin href="/assets/integrations-mB-7zoyT.js">
+    <link rel="modulepreload" crossorigin href="/assets/integrations-Dwl9KQp0.js">
     <link rel="modulepreload" crossorigin href="/assets/jira-CKJg3HZd.js">
-    <link rel="modulepreload" crossorigin href="/assets/jobs-KG4Sn12X.js">
-    <link rel="modulepreload" crossorigin href="/assets/loops-B4_D-nbg.js">
+    <link rel="modulepreload" crossorigin href="/assets/jobs-1G3wodhl.js">
+    <link rel="modulepreload" crossorigin href="/assets/loops--KWr0X-w.js">
     <link rel="modulepreload" crossorigin href="/assets/mcp-CUAN6ORK.js">
     <link rel="modulepreload" crossorigin href="/assets/narration-n3hOA7LY.js">
-    <link rel="modulepreload" crossorigin href="/assets/nav-DhPb-Isc.js">
+    <link rel="modulepreload" crossorigin href="/assets/nav--u7iPYlS.js">
     <link rel="modulepreload" crossorigin href="/assets/packet-B0H15elv.js">
-    <link rel="modulepreload" crossorigin href="/assets/settings-tfLhQZRN.js">
-    <link rel="modulepreload" crossorigin href="/assets/setup-CRKLp_ke.js">
+    <link rel="modulepreload" crossorigin href="/assets/settings-Dbyd6gmj.js">
+    <link rel="modulepreload" crossorigin href="/assets/setup-CKGUxKr-.js">
     <link rel="modulepreload" crossorigin href="/assets/specs-DfIdoU5L.js">
+    <link rel="modulepreload" crossorigin href="/assets/subscriptionUsage-CdlE5Mg1.js">
     <link rel="modulepreload" crossorigin href="/assets/terminal-BAzpHtpY.js">
     <link rel="modulepreload" crossorigin href="/assets/tickets-D41ZMQpf.js">
     <link rel="modulepreload" crossorigin href="/assets/createLucideIcon-Bjbbp_KS.js">
-    <link rel="modulepreload" crossorigin href="/assets/useSharedWebSocket-BZMrX4jr.js">
-    <link rel="modulepreload" crossorigin href="/assets/Trans-D3AfDylf.js">
-    <link rel="modulepreload" crossorigin href="/assets/useDesktop-0unHDBJJ.js">
-    <link rel="modulepreload" crossorigin href="/assets/provider-capabilities-Vi1ZGvAK.js">
-    <link rel="modulepreload" crossorigin href="/assets/save-B6wGWwBR.js">
-    <link rel="modulepreload" crossorigin href="/assets/spending-HBSk-6jv.js">
+    <link rel="modulepreload" crossorigin href="/assets/useSharedWebSocket-C17TGqT8.js">
+    <link rel="modulepreload" crossorigin href="/assets/Trans-CzhPjnjB.js">
+    <link rel="modulepreload" crossorigin href="/assets/useDesktop-DpxVGfUC.js">
+    <link rel="modulepreload" crossorigin href="/assets/provider-capabilities-lePfeT_Y.js">
+    <link rel="modulepreload" crossorigin href="/assets/save-OsUqVn99.js">
+    <link rel="modulepreload" crossorigin href="/assets/spending-CYotH-9N.js">
     <link rel="modulepreload" crossorigin href="/assets/sparkles-DrY8hb0X.js">
     <link rel="modulepreload" crossorigin href="/assets/x-CBMI9ejn.js">
-    <link rel="modulepreload" crossorigin href="/assets/MinimizedChatsContext-CNx_0bZu.js">
+    <link rel="modulepreload" crossorigin href="/assets/MinimizedChatsContext-DKlPf54Y.js">
     <link rel="modulepreload" crossorigin href="/assets/zap-CUOlvtT1.js">
+    <link rel="modulepreload" crossorigin href="/assets/file-text-BcLCfcWZ.js">
     <link rel="modulepreload" crossorigin href="/assets/circle-x-CMYsN4ZH.js">
     <link rel="modulepreload" crossorigin href="/assets/download-CFHyyHcw.js">
-    <link rel="modulepreload" crossorigin href="/assets/file-text-CFT-xXKN.js">
+    <link rel="modulepreload" crossorigin href="/assets/external-link-D6XxC_Cu.js">
     <link rel="modulepreload" crossorigin href="/assets/git-branch-BRM0F5GN.js">
-    <link rel="modulepreload" crossorigin href="/assets/layers-eDMjG41I.js">
     <link rel="modulepreload" crossorigin href="/assets/loader-circle-DcygOQpC.js">
     <link rel="modulepreload" crossorigin href="/assets/pencil-C9RkrIPZ.js">
     <link rel="modulepreload" crossorigin href="/assets/square-Ci-PFcFe.js">
@@ -264,23 +266,22 @@
     <link rel="modulepreload" crossorigin href="/assets/search-Cq_gE3Ik.js">
     <link rel="modulepreload" crossorigin href="/assets/trash-2-BOU3WdZZ.js">
     <link rel="modulepreload" crossorigin href="/assets/triangle-alert-H9T4jAmh.js">
-    <link rel="modulepreload" crossorigin href="/assets/wrench-BfmNO9Vw.js">
+    <link rel="modulepreload" crossorigin href="/assets/jira-api-CbJvbRYx.js">
     <link rel="modulepreload" crossorigin href="/assets/clsx-CjueKrWZ.js">
     <link rel="modulepreload" crossorigin href="/assets/utils-BC4DHlz2.js">
-    <link rel="modulepreload" crossorigin href="/assets/dialog-xXB2q5HJ.js">
+    <link rel="modulepreload" crossorigin href="/assets/dialog-CMgps2MY.js">
     <link rel="modulepreload" crossorigin href="/assets/lib-CGdyxIWg.js">
-    <link rel="modulepreload" crossorigin href="/assets/getTimezoneOffsetInMilliseconds-DOGj1Mfz.js">
-    <link rel="modulepreload" crossorigin href="/assets/formatDistanceToNow-aBss1Nai.js">
-    <link rel="modulepreload" crossorigin href="/assets/button-Ccc9Dc-D.js">
-    <link rel="modulepreload" crossorigin href="/assets/jira-api-BYbEPlkr.js">
-    <link rel="modulepreload" crossorigin href="/assets/project-repositories-CSnfzUpg.js">
-    <link rel="modulepreload" crossorigin href="/assets/RepositoryScopeSelector-C2mvWBQ6.js">
-    <link rel="modulepreload" crossorigin href="/assets/TicketDetailModalContext-B-DySpKL.js">
+    <link rel="modulepreload" crossorigin href="/assets/getTimezoneOffsetInMilliseconds-DxUFGcVq.js">
+    <link rel="modulepreload" crossorigin href="/assets/formatDistanceToNow-DlQaXc7c.js">
+    <link rel="modulepreload" crossorigin href="/assets/button-D1xExSTF.js">
+    <link rel="modulepreload" crossorigin href="/assets/project-repositories-BkBD3rxx.js">
+    <link rel="modulepreload" crossorigin href="/assets/RepositoryScopeSelector-BeM-2gIZ.js">
+    <link rel="modulepreload" crossorigin href="/assets/TicketDetailModalContext-CkVXuHxU.js">
     <link rel="modulepreload" crossorigin href="/assets/core-B3mKBIh5.js">
-    <link rel="modulepreload" crossorigin href="/assets/RepositoryDeliveries-BiwJuS8r.js">
-    <link rel="modulepreload" crossorigin href="/assets/useRuntimeRuns-BN1rhyEm.js">
+    <link rel="modulepreload" crossorigin href="/assets/RepositoryDeliveries-CJVpOUpZ.js">
+    <link rel="modulepreload" crossorigin href="/assets/useRuntimeRuns-CfGRbhr9.js">
     <link rel="modulepreload" crossorigin href="/assets/event-Bt7f3wXe.js">
-    <link rel="stylesheet" crossorigin href="/assets/index-BS7KCWkV.css">
+    <link rel="stylesheet" crossorigin href="/assets/index-Bfunvi6w.css">
   </head>
   <body>
     <div id="specrails-splash" aria-hidden="false" role="status" aria-label="Loading Specrails">

package/docs/README.md

@@ -2,15 +2,11 @@
 
 Welcome. These guides are written for **you, the user**: how to get specrails-desktop running, how to use each feature, and what to do when something looks off.
 
-Specrails works with four AI CLIs — **Claude Code**, **OpenAI Codex**,
-**Google Gemini**, and **Kimi Code**. Install any compatible combination per
-project and choose which engine runs each task.
-
 If you're contributing to the app itself or building on its API, head over to [`internals/`](internals/) for the technical deep dive.
 
 ## Exclusively for agents
 
-When asked to connect to Specrails MCP, read [the agent runbook](agents/mcp.md). It covers Claude, Codex, Kimi and Gemini, preserves existing servers and requires a real read-only verification.
+When asked to connect to Specrails MCP, read [the agent runbook](agents/mcp.md). It covers Claude and Codex, preserves existing servers and requires a real read-only verification.
 
 ## Start here
 
@@ -27,8 +23,6 @@ When asked to connect to Specrails MCP, read [the agent runbook](agents/mcp.md).
 | [Running pipelines](running-pipelines.md) | …you want to launch the AI pipeline against a spec, manage rails, pick agent profiles, or install plugins |
 | [Programmatic agent runtime](internals/programmatic-agent-runtime.md) | …you want separate phases, a provider per role, a local model, or explicit workflow recovery |
 | [Using Codex](codex.md) | …you added a project with OpenAI's Codex CLI instead of (or alongside) Claude |
-| [Using Gemini](gemini.md) | …you added a project with Google's Gemini CLI instead of (or alongside) Claude, Codex, or Kimi |
-| [Using Kimi](kimi.md) | …you want Kimi Code setup, models/effort, session behavior, MCP, and native limitations |
 | [Tracking cost](tracking-cost.md) | …you want to see what AI is costing you and which specs are the most expensive |
 | [Customising the app](customizing.md) | …you want to change theme, configure settings, set a budget, or turn on telemetry |
 | [Terminal panel](terminal.md) | …you want to use the built-in terminal: shortcuts, shell integration, drag-and-drop |
@@ -45,8 +39,6 @@ When asked to connect to Specrails MCP, read [the agent runbook](agents/mcp.md).
 - **"How do I install it?"** → [Getting started](getting-started.md#install)
 - **"How do I add a project?"** → [Getting started](getting-started.md#add-a-project)
 - **"Quick vs Explore mode?"** → [Creating specs › Creating a spec](creating-specs.md#creating-a-spec)
-- **"How do I use a different provider?"** → [Using Codex](codex.md) ·
-  [Using Gemini](gemini.md) · [Using Kimi](kimi.md)
 - **"How do I compare two specs?"** → [Creating specs › Compare two specs side by side](creating-specs.md#compare-two-specs-side-by-side)
 - **"What's a draft?"** → [Creating specs › Drafts](creating-specs.md#drafts)
 - **"What's SMASH?"** → [Creating specs › SMASH a big spec](creating-specs.md#smash-a-big-spec)

package/docs/agent-live-steering.md

@@ -10,8 +10,6 @@ Enviar y Detener permanecen disponibles por separado. Una vez solicitada la entr
 
 Con **Claude y Codex**, las indicaciones entran por el canal nativo del proveedor durante la ejecución. No hace falta esperar a una llamada al MCP de Specrails. Claude las incorpora al contexto después de su lote de herramientas en curso; Codex acepta la actualización del turno activo mediante `turn/steer`. No se mata una herramienta para introducir el mensaje. La conversación mantiene el orden: respuesta anterior, nueva indicación y continuación del agente.
 
-Con **Gemini y Kimi**, los transportes actuales siguen entregando las indicaciones en el siguiente punto seguro de las herramientas de Specrails. Si una acción ya está ejecutándose, se conserva su resultado. Las acciones todavía no iniciadas se suspenden para que el agente lea la corrección y revise su plan. Si no aparece otro punto de entrega, Specrails continúa con el mensaje pendiente al terminar la invocación.
-
 Si el agente está esperando novedades de un rail o job mediante `specrails_watch`, tu mensaje termina inmediatamente esa espera para darle paso. El rail o job observado sigue ejecutándose; no se cancela como efecto de enviar el mensaje.
 
 ## Estados y recuperación
@@ -31,8 +29,6 @@ Los estados de envío se muestran como iconos, con su explicación al pasar el r
 
 Enviar durante una ejecución no garantiza que el modelo cambie una acción que ya ha comenzado ni que interrumpa su razonamiento inmediatamente. El eco de usuario con UUID en Claude y la respuesta de `turn/steer` en Codex confirman recepción; por sí solos no demuestran lectura. En ambos, el verde requiere que el agente confirme esos mensajes con `specrails_mission(action:'acknowledge_inputs', inputIds:[queueId, ...])`. Una salida posterior del modelo no marca automáticamente leída una corrección nativa. En la vía MCP, confirmar la revisión entregada con `acknowledge_updates` registra la lectura. El mensaje inicial incluye un identificador de entrada y también requiere un acuse explícito de lectura. Los avisos sintéticos del proveedor no ponen checks verdes. Si el turno ya terminó antes del envío, el mensaje continúa por la vía normal. Una escritura sin confirmación nunca se reintenta automáticamente.
 
-Claude usa un proceso `stream-json` con entrada abierta; una indicación que llega después de su última frontera interna puede ejecutarse como siguiente turno nativo del mismo proceso. Gemini ACP actualmente cancela el prompt anterior al enviar otro, y Kimi requiere un transporte Server API diferente: no se usan esas rutas como sustituto de la entrega actual.
-
 Una indicación a la misión no cambia por sí sola un job de los rails que ya se haya lanzado. El agente debe revisar su estado y realizar las acciones de gestión apropiadas con los permisos existentes. El proveedor, el proyecto fijado y los permisos del proceso activo tampoco cambian mediante una indicación.
 
 Las referencias a specs, archivos y repositorios conservan su identidad. Los adjuntos de texto se resuelven como contexto. Codex recibe las imágenes por su entrada nativa de archivo; Claude recibe bloques de imagen y los otros transportes usan imágenes MCP, con un presupuesto de 8 MiB por lote. Los archivos originales y sus referencias se conservan; las imágenes no disponibles o que superan el presupuesto se indican explícitamente sin inventar su contenido.
@@ -53,8 +49,6 @@ Cada invocación, incluido un reintento por sesión caducada, recibe una capabil
 
 - [Claude CLI: stream-json y replay-user-messages](https://code.claude.com/docs/en/cli-reference), contrastado con el bucle nativo de Claude Code 2.1.261.
 - [Codex app-server](https://learn.chatgpt.com/docs/app-server), contrastado con el esquema generado por Codex 0.153.4.
-- [Gemini model steering](https://geminicli.com/docs/cli/model-steering/) y ACP instalado 0.49.0: la capacidad interactiva no equivale a entrada sin interrupción en su transporte ACP.
-- [Kimi Server API](https://www.kimi.com/code/docs/en/kimi-code-cli/reference/server-api.html): transporte distinto del modo print utilizado actualmente.
 
 ## Definition engine runs
 

package/docs/agents/README.md

@@ -1,7 +1,5 @@
 # Documentation exclusively for agents
 
-When a person says “connect to the Specrails MCP”, use the [connection runbook](mcp.md). These instructions cover Claude Code, Codex CLI/desktop, Kimi Code and Gemini CLI. They require local discovery, a configuration-preserving registration and a real read-only verification.
-
 ## Maintaining the public copy
 
 The canonical connection runbook is `docs/agents/mcp.md` in Specrails Desktop. Specrails Web keeps a reviewed copy in `src/content/for-agents/`. Its `docs:sync` command generates `/llms.txt`, `/for-agents/index.html` and the static Markdown runbook. These resources are usable without executing the documentation SPA.

package/docs/agents/mcp.md

@@ -1,6 +1,6 @@
 # For agents only: connect to Specrails MCP
 
-Use this runbook when a person asks Claude, Codex, Kimi or Gemini to connect to Specrails. Complete discovery, registration and a read-only verification for the requested client. Do not configure all four clients unless asked. If the tools are already loaded, test the existing connection before changing anything.
+Use this runbook when a person asks Claude or Codex to connect to Specrails. Complete discovery, registration and a read-only verification for the requested client. Do not configure both clients unless asked. If the tools are already loaded, test the existing connection before changing anything.
 
 This is an external agent connecting to Specrails Desktop. It is separate from choosing an AI provider inside Specrails. Connection authorization does not authorize starting missions, creating specs or changing permission tiers. If local files or the client configuration are inaccessible, complete the available checks and report the exact remaining step.
 
@@ -42,8 +42,6 @@ Check the installed client's version and help before editing. Prefer user scope
 |---|---|---|
 | Claude Code | `claude mcp add --scope user --transport stdio specrails --` followed by the verified executable and arguments. User and local entries live in `~/.claude.json`; project entries use `.mcp.json`. The default CLI scope is local, so select scope explicitly. | `claude mcp get specrails`; `/mcp` in the client. Project approvals can block loading. |
 | Codex CLI / desktop | `codex mcp add specrails --` followed by the verified executable and arguments. TOML user configuration, normally `~/.codex/config.toml`, is shared by local Codex clients using that home. | `codex mcp get specrails`; inspect the actual conversation tool catalog. |
-| Gemini CLI | `gemini mcp add --scope user --transport stdio specrails` followed by the verified executable and arguments. Uses `mcpServers` in `~/.gemini/settings.json`; project scope uses `.gemini/settings.json` and is the CLI default. | `gemini mcp list`; `/mcp` in the client. Check allowed/excluded servers and tools. Do not add `--trust` merely to connect. |
-| Kimi Code | Merge the stdio entry into `~/.kimi-code/mcp.json` (or the configured `KIMI_CODE_HOME`), or project `.kimi-code/mcp.json`. Project entries override user entries. Kimi Code 0.27.0 does **not** expose `kimi mcp add`; do not confuse it with the older Python Kimi CLI. | `/mcp` shows connection status; `/mcp-config` edits entries interactively. A newly added file entry requires a new session. |
 
 The following commands are **alternatives**, not a script to install all clients. These macOS examples require the same two file checks shown above and no conflicting existing entry:
 
@@ -54,15 +52,6 @@ claude mcp add --scope user --transport stdio specrails -- \
   /Applications/Specrails.app/Contents/Resources/binaries/specrails-mcp.js
 ```
 
-```bash
-# Gemini CLI only
-gemini mcp add --scope user --transport stdio specrails \
-  /Applications/Specrails.app/Contents/Resources/runtimes/node/bin/node \
-  /Applications/Specrails.app/Contents/Resources/binaries/specrails-mcp.js
-```
-
-For Kimi Code, merge this macOS example into the chosen `mcp.json`, retaining the existing root object and other servers. Use the verified paths for other installations:
-
 ```json
 {
   "mcpServers": {
@@ -76,8 +65,6 @@ For Kimi Code, merge this macOS example into the chosen `mcp.json`, retaining th
 
 Claude Desktop is a separate client from Claude Code. If that is the requested host, merge this same `mcpServers` structure in its local MCP configuration through its settings; registering Claude Code alone is not proof that Claude Desktop is configured.
 
-Sources: [Claude Code MCP](https://code.claude.com/docs/en/mcp), [Gemini CLI MCP](https://geminicli.com/docs/tools/mcp-server/), [Kimi Code MCP](https://moonshotai.github.io/kimi-code/en/customization/mcp). Command shapes were also checked against installed help for Claude Code 2.1.265, Gemini CLI 0.49.0 and Kimi Code 0.27.0. Client configuration and live connection are separate checks.
-
 ## Verify all three stages
 
 - **Registered:** the requested client's configuration check (for Codex, `codex mcp get specrails`) shows the expected stdio command and arguments. This only proves configuration was saved.

package/docs/cli.md

@@ -8,8 +8,6 @@ The `specrails-desktop` CLI does three things:
 
 Everything here is grouped by what you're trying to do, not by alphabetical order of flags.
 
-## Manage the app
-
 ### Start it
 
 ```bash
@@ -49,8 +47,6 @@ specrails-desktop --jobs                # see the note below
 
 > **Note on `--jobs`:** there is no app-level `/api/jobs` route, so the server returns 404 and `--jobs` prints `jobs history requires manager with SQLite persistence (#57)` and exits non-zero against a running server. Job history lives **per project** — view it on the project's **Jobs** page (right sidebar) in the dashboard instead.
 
-## Manage projects
-
 ### List
 
 ```bash
@@ -160,14 +156,6 @@ specrails-desktop --project ~/repos/api-srv implement "#5" "#6"
 
 `--project` accepts a project **name** or a **path** (absolute, or relative starting with `.` / `..`). Use it when you want to launch work in a project from outside its directory (e.g. from a CI runner or your home directory). Both `--project` and `--port` may appear **anywhere** in the command, not just at the front.
 
-## Providers
-
-The app supports four AI providers — **Claude, Codex, Gemini, and Kimi** — and all four are registered by default. Each project is configured with one or more of them when you add it.
-
-The CLI itself has **no provider flag**: a CLI-routed job always launches the project's **primary provider** (the first one you selected when you added the project). To pick a different engine for a single spec or rail on a multi-provider project, use the **dashboard** — the Add Spec engine selector or the rail-header engine selector. Provider guides: [Codex](codex.md), [Gemini](gemini.md), and [Kimi](kimi.md).
-
-> **Ops note:** to constrain which providers the dashboard offers, set `SPECRAILS_CODEX_BETA=0` or `SPECRAILS_GEMINI_BETA=0` in the server's environment (only the exact string `0` disables a provider; unset, `1`, or `true` all leave it enabled). This affects the dashboard's provider picker, not the CLI, which has no engine flag.
-
 ## OpenSpec workflow
 
 Bundled `opsx:*` commands for structured change management of the app itself. Run them from the project directory:
@@ -205,7 +193,6 @@ If you invoke a command that routes work (`implement`, a raw prompt, …) while
 
 This fallback has two important limitations:
 
-- **It always spawns `claude`** — even on a project whose primary provider is Codex, Gemini, or Kimi. The offline path does not honour the project's configured provider, so an offline run can behave differently from the same command run through the app.
 - **Nothing is recorded.** There's no queue, no job in the Dashboard, and nothing written to Analytics.
 
 Start the app first (`specrails-desktop start`) if you want the job to use the right provider and show up in the dashboard.

package/docs/codex.md

@@ -1,11 +1,5 @@
 # Using Specrails with the Codex CLI
 
-Specrails supports **four AI providers** — Claude, Codex, Gemini, and Kimi.
-This guide covers OpenAI's
-[Codex CLI](https://developers.openai.com/codex). For the others, see
-[Claude Code](https://claude.com/claude-code) and the
-[Gemini guide](gemini.md) or [Kimi guide](kimi.md).
-
 > **Just want to get going?** Install the `codex` CLI, log in, then in
 > the app click **Add Project → check Codex → Submit**. The rest of the
 > app (specs, rails, chat, analytics) works the same as it does for
@@ -14,7 +8,7 @@ This guide covers OpenAI's
 You pick any subset of the four providers when you add a project — and
 you can mix them in a single project too (see [Running more than one
 provider in one project](#running-more-than-one-provider-in-one-project)
-below). All four are registered by default.
+below). Both are registered by default.
 
 > The codex path is enabled by default. To temporarily disable it
 > (e.g. as an emergency rollback), set `SPECRAILS_CODEX_BETA=0` in the
@@ -38,28 +32,6 @@ binary isn't on `PATH`; it shows install commands if you click "More info".
 
 ## Adding a codex project
 
-1. Open the app UI and click **Add Project**.
-2. Pick the project's path.
-3. In the **AI providers** row, check **Codex** (you can check
-   **Claude**, **Gemini**, and/or **Kimi** too — see [Running more than one
-   provider in one project](#running-more-than-one-provider-in-one-project)).
-   The first provider you select becomes the project default.
-4. Submit. The app writes `.specrails/install-config.yaml` (with
-   `provider: codex` and `tier: quick` as YAML keys) and spawns
-   `npx --yes --prefer-online specrails-core@^5.1.0 init --yes --from-config <file>`
-   — the provider and tier live in the YAML, not as CLI flags. (The app
-   pins `specrails-core@^5.1.0`; that floor is the version that ships the
-   current provider targets, including Kimi and the Codex skill set.) The install
-   produces:
-   - `.codex/config.toml` — model, reasoning effort, sandbox mode, and
-     approval policy (all top-level keys per the codex 0.128.0+ schema).
-   - `.codex/skills/sr-*/SKILL.md` — general specrails skills
-     (implement, why, compat-check, …).
-   - `.codex/skills/rails/sr-*/SKILL.md` — the pipeline rails.
-   - `AGENTS.md` — top-level instructions file with a sentinel-protected
-     managed block. Anything outside the sentinels is preserved on
-     updates.
-
    The exact rail and lifecycle skill set is produced by
    `specrails-core`, not the app, so the precise file list can vary by
    core version.
@@ -72,14 +44,6 @@ the choice later.
 
 ## Running more than one provider in one project
 
-A single project can install **any combination** of Claude, Codex, Gemini, and
-Kimi. In the **Add Project** dialog the **AI providers** control is a
-multi-select — check the ones you want and the app runs each provider's
-install sequentially. The first provider you select is the
-**primary/default**; the helper text spells this out: *"The engines will
-be set up. The first is the project default. Cannot be changed after
-creation."*
-
 Once more than one is installed:
 
 - **Per-invocation engine pickers** let you choose which engine runs each
@@ -90,11 +54,6 @@ Once more than one is installed:
   to choose.
 - The **selected engine is remembered per project** (it defaults to the
   primary), so you don't have to re-pick on every spawn.
-- **Provider-scoped capabilities.** Claude and Kimi expose independent
-  profile catalogs; Codex and Gemini run rails in legacy/no-profile mode.
-  Integration entries and health are resolved for the effective provider:
-  Serena supports Claude, Codex, and Kimi through each provider's native MCP
-  registration, while Jira is provider-agnostic.
 
 When only one provider is installed the app behaves byte-identically to
 a single-provider project — no engine pickers, no provider persisted on
@@ -113,23 +72,13 @@ These models do not offer `minimal`. Mission-originated launches inherit the
 mission's model and effort when the engine matches; an explicit launch model
 still takes precedence.
 
-The table below includes all four registered providers. See the
-[Kimi guide](kimi.md) for its full safety matrix.
-
-| Surface | Claude | Codex | Gemini | Kimi |
 |---|---|---|---|---|
-| **CLI** | `claude` | `codex` | `gemini` | `kimi` |
 | **Min CLI version** | none pinned | `0.128.0` | `0.11.0` | `0.27.0` |
-| **Project dir** | `.claude/` | `.codex/` | `.gemini/` | `.kimi-code/` |
-| **Instructions file** | `CLAUDE.md` | `AGENTS.md` | `GEMINI.md` | `AGENTS.md` |
-| **Default model** | `sonnet` | `gpt-5.5` (catalog also lists `gpt-6-astra` — the `max` preset model, no rate card yet so its cost shows as unavailable — and the GPT-5.6 family `gpt-5.6-sol` / `gpt-5.6-terra` / `gpt-5.6-luna`) | `gemini-3.5-flash` | `k3` |
 | **Reasoning efforts** | `low`–`xhigh` | model-dependent | none | `low`/`high`/`max`, K3 only |
-| **Agent format** | `.claude/agents/<id>.md` | `.codex/skills/<id>/SKILL.md` | `.gemini/` target | `.kimi-code/skills/<id>/SKILL.md` |
 | **Agent profiles** | ✅ | legacy | legacy | ✅ provider-scoped |
 | **Implement** | ✅ | ✅ | ✅ | ✅ |
 | **Freestyle** | ✅ | ❌ | ❌ | ✅ |
 | **Pure-output transforms** | capability-dependent | capability-dependent | capability-dependent | ❌ fail closed |
-| **MCP registration** | `.mcp.json` | isolated `CODEX_HOME` | `.gemini/settings.json` | `.kimi-code/mcp.json` |
 | **Session resume** | `--resume` | `exec resume` | `--resume` | bound `--session=<id>` after resume hint |
 | **Native cost report** | exact | estimated | estimated | unavailable |
 | **Telemetry** | native | synthesized | native | unavailable |
@@ -141,9 +90,6 @@ A few Codex-specific behaviours worth calling out:
   a rail can read and write anywhere in the project. This is intentional —
   rails need to apply edits across the repo — but it's worth knowing if
   you're surprised by a rail touching files outside the working tree.
-- **Freestyle rails require a capable provider.** Launching a Freestyle rail
-  (`mode: freestyle`) on Codex or Gemini is rejected before spawn. Pick Claude
-  or Kimi for that autonomous rail mode.
 
 ## Estimated cost
 
@@ -163,7 +109,7 @@ The Analytics page surfaces this in two places:
 - **A "By provider" card** between the Hero and the Timeline splits
   cost per provider into authoritative vs estimated whenever the project
   has invoked more than one. Claude rows are authoritative (the CLI
-  reports cost); Codex and Gemini rows are estimated from token counts
+  reports cost); Codex rows are estimated from token counts
   and the local rate-card.
 
 The pricing table is reviewed quarterly. The reference date sits on
@@ -172,13 +118,6 @@ ship an out-of-band update to `server/modules/accounting/runtime/pricing.ts`.
 
 ## Plugins and MCP on codex projects
 
-The **Integrations** section stays visible on Codex projects. Serena is
-provider-aware and registers its server with `codex mcp add` in Specrails'
-isolated per-project `CODEX_HOME`; Claude uses `.mcp.json`, and Kimi uses
-`.kimi-code/mcp.json`. Install state and health are scoped to the selected
-provider, so one provider's entry never masquerades as another's. Jira remains
-provider-agnostic.
-
 For MCP servers outside the managed plugin catalog, use Codex's native
 configuration flow. Codex chat and Explore turns inherit the appropriate Codex
 environment and read that MCP configuration.
@@ -228,9 +167,6 @@ SPECRAILS_CODEX_BETA=0 npm run dev
 For the packaged desktop app, set the variable in the environment the app
 process inherits (the `npm run dev` form is for source runs only).
 
-(Gemini has the same kill switch, `SPECRAILS_GEMINI_BETA=0`, but **no**
-legacy `SPECRAILS_HUB_*` fallback name.)
-
 `GET /api/available-providers` will report `codex: false` and
 `POST /api/projects` will refuse new codex projects. Existing
 codex projects keep functioning — the env var only gates creating
@@ -249,17 +185,8 @@ The codex integration lives in:
 - `server/plugins/codex-mcp.ts` — `codex mcp add/remove/list` wrapper
   with per-project `CODEX_HOME`.
 
-The contract every provider implements is at
-`server/providers/types.ts`. Adding a provider is essentially one new
-adapter file + one `register(...)` entry in `server/providers/index.ts`
-(the rest of the codebase is registry-driven and provider-id-agnostic).
-`server/providers/gemini-adapter.ts` is the freshest worked example —
-see [Adding a provider](internals/adding-a-provider.md).
-
 ## See also
 
-- [Using Gemini](gemini.md) — the Gemini CLI provider (the other
-  provider with estimated cost).
 - [Adding a provider](internals/adding-a-provider.md) — the developer
   guide to wiring an AI CLI adapter.
 - [Tracking cost](tracking-cost.md) — how the Analytics page surfaces

package/docs/creating-specs.md

@@ -2,13 +2,6 @@
 
 A **spec** in specrails-desktop is a description of work you want done — what the AI agents will read and act on. This guide walks through every way you can create, refine, compare, and organise them.
 
-Specs are engine-agnostic: depending on how the project was set up, they can
-be shaped by **Claude, Codex, Gemini, or Kimi**. Engine selectors show only
-providers that advertise the surface's required capability. Kimi is available
-for agentic Explore/proposal work, but its `-p` mode cannot enforce the
-no-tools/read-only boundary required by Quick Spec and the structured
-transforms listed below.
-
 ## Creating a spec
 
 Open the Dashboard and click **Add** (the Plus button on the SpecsBoard toolbar). The **Add Spec** dialog opens with three modes:
@@ -17,20 +10,10 @@ Open the Dashboard and click **Add** (the Plus button on the SpecsBoard toolbar)
 - **Explore** — you converse with the AI and shape the spec turn by turn.
 - **Raw** — your prompt is saved verbatim as a spec, with **no AI** involved.
 
-If the project has **more than one compatible provider installed**, an **AI
-engine** selector sits at the top of the dialog. The choice is remembered per
-project. Projects with a single compatible provider don't show the selector;
-Kimi is not offered for Quick Spec even when it is installed.
-
 ### Quick mode
 
 For when you already know what you want. Type your idea; the AI generates the full spec. This is usually a single turn — but it runs multi-turn when you give it the full codebase (the context slider's higher presets) or attach files, so it can read what it needs first.
 
-> **Kimi:** Quick Spec is unavailable. The server rejects a direct Kimi
-> request before spawning because this form is a pure-output action. This is
-> separate from the agentic **Quick Launcher**, where commands such as
-> `/opsx:ff` can run with Kimi. Use Explore, Raw, or that launcher instead.
-
 **Controls:**
 
 - **Engine + model** — the engine selector (multi-provider only) and a model picker. The model defaults to a sensible choice for the engine and can be overridden per spec.
@@ -49,11 +32,6 @@ For when you already know what you want. Type your idea; the AI generates the fu
 
 Your last choice for this toggle is remembered per project.
 
-Contract Layer enrichment requires a provider that can enforce the structured
-action's safe tool policy. It is hidden for Kimi because Kimi 0.27 prompt mode
-auto-approves tools and has no per-spawn no-tools boundary. A direct request
-fails before spawn.
-
 While the spec is being generated, a toast in the corner shows the project name, a truncated copy of your idea, and the **elapsed time** ("Generating… 0:12"). When it finishes it switches to "Generated in <time>" with a **View** action that jumps straight to the new spec.
 
 ### Explore mode
@@ -73,16 +51,10 @@ For when the spec needs shaping. You converse with the AI; a live draft updates
 
 Rich and Max both load the full codebase — they differ only in whether the Contract Layer pass runs. The decision is per-conversation (saved on `chat_conversations.context_scope`) so it doesn't bleed into other Explore sessions.
 
-Kimi supports the agentic Explore conversation and proposal flow. It does not
-offer the Max Contract Layer pass. Its prompt mode may use tools
-autonomously—Explore is not a read-only sandbox.
-
 The **Desktop** preset is Explore-only — Quick mode caps the slider at **Max** (no project/approved MCPs), as noted under [Quick mode](#quick-mode) above.
 
 Click **Fine-tune** to set the flags individually. One toggle only appears here:
 
-- **My approved MCPs** — loads the MCP servers you've already approved locally (`claude mcp add` / `codex mcp add`) without changing where the spawn runs. Explore-only; disabled in Quick mode. On a **Gemini** project, Gemini reads your own approved MCP servers from its native config (`~/.gemini`) automatically, so this toggle isn't needed there. Kimi's user-global MCP source cannot be isolated per spawn, so this opt-in is unavailable for Kimi; project `.kimi-code/mcp.json` remains supported.
-
 **Buttons in the shell:**
 
 - **Save as Draft** — persists the conversation as a draft ticket so you can come back later. Available once you've sent at least one user message. The draft carries `origin_conversation_id` pointing back at this conversation so you can resume it from the dashboard.
@@ -150,11 +122,6 @@ Got an epic that's clearly too big? Open it and click **SMASH Spec into Sub-Spec
 
 Inside the epic's modal you'll see an **Epic Family Sidebar** listing all children. Inside each child's modal, an **Epic Breadcrumb** lets you jump back to the parent. If the epic already has children, the button reads **Re-SMASH** and regenerates the family (after a confirmation).
 
-SMASH and Re-SMASH are unavailable for Kimi: both require a constrained
-structured transform, and Re-SMASH can delete existing children. Desktop
-checks the capability before any spawn or deletion, so a direct Kimi request
-leaves the existing family untouched.
-
 ## Continue Editing — refine an existing spec
 
 For any spec with status `draft`, `todo`, or `backlog`, the detail modal shows a **Continue Editing** button. Click it and:
@@ -167,10 +134,6 @@ For any spec with status `draft`, `todo`, or `backlog`, the detail modal shows a
 
 Continue Editing works from the dashboard or from inside a split-view comparison — triggering it from a split-view panel collapses the comparison automatically because the shell needs the full screen.
 
-The AI Edit/refine operation is unavailable for Kimi because its output-only
-rewrite contract must not be able to mutate the workspace through tools.
-Manual edits and a separate Kimi Explore proposal remain available.
-
 The Contract Layer (if a spec has one) is shown inside the detail modal as a collapsible disclosure with an `N/5 populated` badge. You can re-run the enrichment for a single ticket from there.
 
 ## Addenda — iterate on a spec without rewriting it
@@ -270,5 +233,3 @@ You don't need this to use the feature, but it's nice to know:
 - [Running pipelines](running-pipelines.md) — drag those specs onto rails and launch the implementation pipeline.
 - [Tracking cost](tracking-cost.md) — see what each spec is costing you.
 - [Customising the app](customizing.md) — set a daily budget so you can stop worrying.
-- [Using Codex](codex.md) / [Using Gemini](gemini.md) — provider-specific notes if you generate specs with Codex or Gemini.
-- [Using Kimi](kimi.md) — agentic spec surfaces and the structured actions that fail closed.

package/docs/customizing.md

@@ -67,7 +67,7 @@ A custom instruction appended to every **Implement** rail job, after the ticket
 
 ### Freestyle pre-prompt
 
-The instruction sent to the selected provider for **Freestyle** rails. Freestyle skips the OpenSpec pipeline — it hands that provider this pre-prompt plus the spec text and lets it implement autonomously. Claude and Kimi currently advertise Freestyle support. The spec text is appended automatically after the pre-prompt. Leave it blank to use the built-in default.
+The instruction sent to the selected provider for **Freestyle** rails. Freestyle skips the OpenSpec pipeline — it hands that provider this pre-prompt plus the spec text and lets it implement autonomously. Claude currently advertise Freestyle support. The spec text is appended automatically after the pre-prompt. Leave it blank to use the built-in default.
 
 ### Telemetry
 
@@ -128,22 +128,10 @@ On first run the app generates a token and persists it to `~/.specrails/desktop.
 
 The app binds to `127.0.0.1` only, so it's never exposed to your network. To rotate the token, stop the app, delete `~/.specrails/desktop.token`, and start it again — a fresh token is generated on the next boot.
 
-## Providers
-
-The app works with **four AI providers — Claude, Codex, Gemini, and Kimi — all enabled by default.** When you add a project you pick which provider(s) to install (you can install any subset; the first one becomes the project's default). The engine pickers on Add Spec, the rail header, and the terminal's "Open AI CLI" button appear automatically whenever more than one provider is installed.
-
-You normally don't configure anything here — providers are selected per project in the UI. Codex and Gemini have the emergency rollback env vars below; Kimi availability follows executable/version detection and Core compatibility. See [codex.md](codex.md), [gemini.md](gemini.md), and [kimi.md](kimi.md) for setup, authentication, and limitations.
-
 ## Environment variables
 
 Most settings live in the UI. A few app-level switches are env-only because they're guardrails ops people want to flip without opening the dashboard.
 
-> **How values are read** (the rules differ by flag type):
-> - **Section gates** (`SPECRAILS_*_SECTION`, `SPECRAILS_TERMINAL_PANEL`, `SPECRAILS_CODE_EXPLORER`, …) are ON unless set to the **exact string `false`**.
-> - **Provider rollbacks** (`SPECRAILS_CODEX_BETA`, `SPECRAILS_GEMINI_BETA`) disable on the **exact string `0`** only — `false`/`off` do *not* disable them.
-> - **Kill switches** (`SPECRAILS_SMASH`, `SPECRAILS_EXPLORE_CONTRACT_REFINE`) accept `0` / `false` / `off`.
-> - **Opt-in hatches** (`SPECRAILS_EXPLORE_LEGACY_CWD`, `SPECRAILS_ALLOW_LOCAL_WEBHOOKS`) enable on the **exact string `1`**.
-
 ### Server-side (read at app startup or by spawned children)
 
 | Variable | Effect |
@@ -158,11 +146,9 @@ Most settings live in the UI. A few app-level switches are env-only because they
 | `SPECRAILS_INTERACTIVE_JOBS=false` | Disable interactive jobs everywhere (every Claude job — and every Claude loop step — is interactive by default): jobs fall back to the legacy one-shot spawn and the per-job message/finalize routes return 403 |
 | `SPECRAILS_BROWSER_CAPTURE=false` | Disable Add-Spec-from-browser capture |
 | `SPECRAILS_CODEX_BETA=0` | Emergency rollback — disable the Codex provider (only the exact string `0`; the legacy `SPECRAILS_HUB_CODEX_BETA` is read as a fallback **only when `SPECRAILS_CODEX_BETA` is unset**) |
-| `SPECRAILS_GEMINI_BETA=0` | Emergency rollback — disable the Gemini provider (default unset = enabled; only the exact string `0` disables; **no legacy fallback name**) |
 | `SPECRAILS_SMASH=0` | Kill switch for SMASH spec decomposition (`0` / `false` / `off`; endpoints return 409) |
 | `SPECRAILS_EXPLORE_CONTRACT_REFINE=0` | App-wide kill switch for Contract Refine (auto-fire + retry endpoint; accepts `0` / `false` / `off`) |
 | `SPECRAILS_EXPLORE_LEGACY_CWD=1` | Force every Explore spawn to use the project root instead of the app-managed `explore-cwd/` or a relocated workspace |
-| `SPECRAILS_FILE_SUMMARY_MODEL` | Override the model used for Code-section file summaries. Per-provider overrides take precedence: `SPECRAILS_FILE_SUMMARY_MODEL_CLAUDE` (Claude) and `SPECRAILS_FILE_SUMMARY_MODEL_CODEX` (Codex); the generic var is the fallback. Kimi file summaries and construction-story AI are capability-gated off, so this variable never enables them for Kimi. |
 | `SPECRAILS_ALLOW_LOCAL_WEBHOOKS=1` | Allow outbound webhooks to target loopback / private-network addresses |
 
 ### Client-side (Vite — set at build time)