oh-my-opencode 5.1.45 → 5.1.47

package/.agents/command/publish.md

@@ -205,8 +205,7 @@ gh release view "v${NEW_VERSION}" --json tagName,url --jq '{tag: .tagName, url:
 
 **Release notes are written BEFORE the release, not after.**
 
-The release body is extracted from the `CHANGELOG.md` section for this version. Author the user-facing
-notes under `## [Unreleased]` and land them before dispatching `/publish`; release-state preparation
+The release body is extracted from the `CHANGELOG.md` section for this version. Add the user-facing notes as `changes/unreleased/<pr-number>.md` fragments (one per PR, named for the PR) and land them before dispatching `/publish`; release-state preparation
 stamps that heading into `## [<version>] - <UTC date>` and commits it with the release state, so the
 published commit already carries its own notes.
 
@@ -220,13 +219,13 @@ bun run script/print-release-notes.ts "${NEW_VERSION}" /tmp/contributors.md
 <agent-instruction>
 After running the preview, present the output to the user and say:
 
-> **This is the exact body the release will publish:** the notes you authored under `[Unreleased]`,
+> **This is the exact body the release will publish:** the assembled fragments,
 > then contributor thank-yous for non-team contributors, then the install footer.
 >
 > Both steps are fail-closed: an absent, empty, or duplicated section aborts the release instead of
 > publishing blank notes, and re-stamping a version that already has a section is refused.
 >
-> If the `[Unreleased]` section is empty, STOP and write the notes first — the release cannot proceed.
+> If `changes/unreleased/` holds no fragments, STOP and write them first — the release cannot proceed.
 
 **APPROVAL GATE (single, binary):** The user's initial publish request with a named bump type IS the only approval this workflow requires. Do NOT wait for a separate acknowledgement here. Present the preview, then IMMEDIATELY proceed to Step 6. The only exception: if the user explicitly said "let me review the changelog before you continue" (or equivalent), stop and wait. Otherwise continue without ending the turn.
 </agent-instruction>
@@ -373,25 +372,25 @@ After the release notes are finalized, post them to the Discord channel. This st
 <hard-gate>
 The workflow is not complete until this step has either:
 1. Sent a Discord message successfully and recorded the message ID, or
-2. Failed after `agent-discordbot auth status` plus one send retry, with the Jobdori bot-token failure reported to the user.
+2. Failed after `agent-discordbot auth status` plus one send retry, with the release bot-token failure reported to the user.
 
 Never skip this step because the release summary was awaiting approval. If the user already confirmed the publish, continue through Discord before stopping.
 </hard-gate>
 
 <agent-discord-instruction>
-1. Use the Jobdori bot token through `agent-discordbot` for release announcements. This is the required release path; do not use the personal `agent-discord` token unless the bot path is unavailable and the user explicitly approves the fallback. Pin the bot id so release messages go out as the Jobdori bot even if the local `agent-discordbot` current bot changes.
+1. Use the release bot token through `agent-discordbot` for release announcements. This is the required release path; do not use the personal `agent-discord` token unless the bot path is unavailable and the user explicitly approves the fallback. Pin the bot id so release messages go out as the release bot even if the local `agent-discordbot` current bot changes.
 ```bash
-JOBDORI_BOT_ID=1486173823354146917
-agent-discordbot auth status --bot "$JOBDORI_BOT_ID"
+RELEASE_BOT_ID=1486173823354146917
+agent-discordbot auth status --bot "$RELEASE_BOT_ID"
 ```
 
 2. **Read recent messages** in the channel to match the existing announcement style:
 ```bash
-JOBDORI_BOT_ID=1486173823354146917
-agent-discordbot message list 1454708427392680067 --bot "$JOBDORI_BOT_ID" --limit 5
+RELEASE_BOT_ID=1486173823354146917
+agent-discordbot message list 1454708427392680067 --bot "$RELEASE_BOT_ID" --limit 5
 ```
 
-3. If `agent-discordbot` is unavailable or unauthorized, stop and report that the Jobdori token path failed. Only then may a human decide whether to use `agent-discord`.
+3. If `agent-discordbot` is unavailable or unauthorized, stop and report that the release bot token path failed. Only then may a human decide whether to use `agent-discord`.
 
 4. Post the release announcement to channel `1454708427392680067` matching the style of previous announcements. The message should follow this structure:
 ```
@@ -414,9 +413,9 @@ Plus {summary of remaining changes}.
 ```
 
 ```bash
-JOBDORI_BOT_ID=1486173823354146917
+RELEASE_BOT_ID=1486173823354146917
 RELEASE_URL=$(gh release view "v${NEW_VERSION}" --json url --jq '.url')
-agent-discordbot message send 1454708427392680067 "{your message following the style above}" --bot "$JOBDORI_BOT_ID"
+agent-discordbot message send 1454708427392680067 "{your message following the style above}" --bot "$RELEASE_BOT_ID"
 ```
 
 If the message fails to send, warn the user and continue — do NOT block the publish workflow on Discord errors.

package/.agents/skills/publish/SKILL.md

@@ -204,8 +204,7 @@ gh release view "v${NEW_VERSION}" --json tagName,url --jq '{tag: .tagName, url:
 
 **Release notes are written BEFORE the release, not after.**
 
-The release body is extracted from the `CHANGELOG.md` section for this version. Author the user-facing
-notes under `## [Unreleased]` and land them before dispatching `/publish`; release-state preparation
+The release body is extracted from the `CHANGELOG.md` section for this version. Add the user-facing notes as `changes/unreleased/<pr-number>.md` fragments (one per PR, named for the PR) and land them before dispatching `/publish`; release-state preparation
 stamps that heading into `## [<version>] - <UTC date>` and commits it with the release state, so the
 published commit already carries its own notes.
 
@@ -219,13 +218,13 @@ bun run script/print-release-notes.ts "${NEW_VERSION}" /tmp/contributors.md
 <agent-instruction>
 After running the preview, present the output to the user and say:
 
-> **This is the exact body the release will publish:** the notes you authored under `[Unreleased]`,
+> **This is the exact body the release will publish:** the assembled fragments,
 > then contributor thank-yous for non-team contributors, then the install footer.
 >
 > Both steps are fail-closed: an absent, empty, or duplicated section aborts the release instead of
 > publishing blank notes, and re-stamping a version that already has a section is refused.
 >
-> If the `[Unreleased]` section is empty, STOP and write the notes first — the release cannot proceed.
+> If `changes/unreleased/` holds no fragments, STOP and write them first — the release cannot proceed.
 
 **APPROVAL GATE (single, binary):** The user's initial publish request with a named bump type IS the only approval this workflow requires. Do NOT wait for a separate acknowledgement here. Present the preview, then IMMEDIATELY proceed to Step 6. The only exception: if the user explicitly said "let me review the changelog before you continue" (or equivalent), stop and wait. Otherwise continue without ending the turn.
 </agent-instruction>
@@ -372,25 +371,25 @@ After the release notes are finalized, post them to the Discord channel. This st
 <hard-gate>
 The workflow is not complete until this step has either:
 1. Sent a Discord message successfully and recorded the message ID, or
-2. Failed after `agent-discordbot auth status` plus one send retry, with the Jobdori bot-token failure reported to the user.
+2. Failed after `agent-discordbot auth status` plus one send retry, with the release bot-token failure reported to the user.
 
 Never skip this step because the release summary was awaiting approval. If the user already confirmed the publish, continue through Discord before stopping.
 </hard-gate>
 
 <agent-discord-instruction>
-1. Use the Jobdori bot token through `agent-discordbot` for release announcements. This is the required release path; do not use the personal `agent-discord` token unless the bot path is unavailable and the user explicitly approves the fallback. Pin the bot id so release messages go out as the Jobdori bot even if the local `agent-discordbot` current bot changes.
+1. Use the release bot token through `agent-discordbot` for release announcements. This is the required release path; do not use the personal `agent-discord` token unless the bot path is unavailable and the user explicitly approves the fallback. Pin the bot id so release messages go out as the release bot even if the local `agent-discordbot` current bot changes.
 ```bash
-JOBDORI_BOT_ID=1486173823354146917
-agent-discordbot auth status --bot "$JOBDORI_BOT_ID"
+RELEASE_BOT_ID=1486173823354146917
+agent-discordbot auth status --bot "$RELEASE_BOT_ID"
 ```
 
 2. **Read recent messages** in the channel to match the existing announcement style:
 ```bash
-JOBDORI_BOT_ID=1486173823354146917
-agent-discordbot message list 1454708427392680067 --bot "$JOBDORI_BOT_ID" --limit 5
+RELEASE_BOT_ID=1486173823354146917
+agent-discordbot message list 1454708427392680067 --bot "$RELEASE_BOT_ID" --limit 5
 ```
 
-3. If `agent-discordbot` is unavailable or unauthorized, stop and report that the Jobdori token path failed. Only then may a human decide whether to use `agent-discord`.
+3. If `agent-discordbot` is unavailable or unauthorized, stop and report that the release bot token path failed. Only then may a human decide whether to use `agent-discord`.
 
 4. Post the release announcement to channel `1454708427392680067` matching the style of previous announcements. The message should follow this structure:
 ```
@@ -413,9 +412,9 @@ Plus {summary of remaining changes}.
 ```
 
 ```bash
-JOBDORI_BOT_ID=1486173823354146917
+RELEASE_BOT_ID=1486173823354146917
 RELEASE_URL=$(gh release view "v${NEW_VERSION}" --json url --jq '.url')
-agent-discordbot message send 1454708427392680067 "{your message following the style above}" --bot "$JOBDORI_BOT_ID"
+agent-discordbot message send 1454708427392680067 "{your message following the style above}" --bot "$RELEASE_BOT_ID"
 ```
 
 If the message fails to send, warn the user and continue — do NOT block the publish workflow on Discord errors.

package/.opencode/command/publish.md

@@ -205,8 +205,7 @@ gh release view "v${NEW_VERSION}" --json tagName,url --jq '{tag: .tagName, url:
 
 **Release notes are written BEFORE the release, not after.**
 
-The release body is extracted from the `CHANGELOG.md` section for this version. Author the user-facing
-notes under `## [Unreleased]` and land them before dispatching `/publish`; release-state preparation
+The release body is extracted from the `CHANGELOG.md` section for this version. Add the user-facing notes as `changes/unreleased/<pr-number>.md` fragments (one per PR, named for the PR) and land them before dispatching `/publish`; release-state preparation
 stamps that heading into `## [<version>] - <UTC date>` and commits it with the release state, so the
 published commit already carries its own notes.
 
@@ -220,13 +219,13 @@ bun run script/print-release-notes.ts "${NEW_VERSION}" /tmp/contributors.md
 <agent-instruction>
 After running the preview, present the output to the user and say:
 
-> **This is the exact body the release will publish:** the notes you authored under `[Unreleased]`,
+> **This is the exact body the release will publish:** the assembled fragments,
 > then contributor thank-yous for non-team contributors, then the install footer.
 >
 > Both steps are fail-closed: an absent, empty, or duplicated section aborts the release instead of
 > publishing blank notes, and re-stamping a version that already has a section is refused.
 >
-> If the `[Unreleased]` section is empty, STOP and write the notes first — the release cannot proceed.
+> If `changes/unreleased/` holds no fragments, STOP and write them first — the release cannot proceed.
 
 **APPROVAL GATE (single, binary):** The user's initial publish request with a named bump type IS the only approval this workflow requires. Do NOT wait for a separate acknowledgement here. Present the preview, then IMMEDIATELY proceed to Step 6. The only exception: if the user explicitly said "let me review the changelog before you continue" (or equivalent), stop and wait. Otherwise continue without ending the turn.
 </agent-instruction>
@@ -373,25 +372,25 @@ After the release notes are finalized, post them to the Discord channel. This st
 <hard-gate>
 The workflow is not complete until this step has either:
 1. Sent a Discord message successfully and recorded the message ID, or
-2. Failed after `agent-discordbot auth status` plus one send retry, with the Jobdori bot-token failure reported to the user.
+2. Failed after `agent-discordbot auth status` plus one send retry, with the release bot-token failure reported to the user.
 
 Never skip this step because the release summary was awaiting approval. If the user already confirmed the publish, continue through Discord before stopping.
 </hard-gate>
 
 <agent-discord-instruction>
-1. Use the Jobdori bot token through `agent-discordbot` for release announcements. This is the required release path; do not use the personal `agent-discord` token unless the bot path is unavailable and the user explicitly approves the fallback. Pin the bot id so release messages go out as the Jobdori bot even if the local `agent-discordbot` current bot changes.
+1. Use the release bot token through `agent-discordbot` for release announcements. This is the required release path; do not use the personal `agent-discord` token unless the bot path is unavailable and the user explicitly approves the fallback. Pin the bot id so release messages go out as the release bot even if the local `agent-discordbot` current bot changes.
 ```bash
-JOBDORI_BOT_ID=1486173823354146917
-agent-discordbot auth status --bot "$JOBDORI_BOT_ID"
+RELEASE_BOT_ID=1486173823354146917
+agent-discordbot auth status --bot "$RELEASE_BOT_ID"
 ```
 
 2. **Read recent messages** in the channel to match the existing announcement style:
 ```bash
-JOBDORI_BOT_ID=1486173823354146917
-agent-discordbot message list 1454708427392680067 --bot "$JOBDORI_BOT_ID" --limit 5
+RELEASE_BOT_ID=1486173823354146917
+agent-discordbot message list 1454708427392680067 --bot "$RELEASE_BOT_ID" --limit 5
 ```
 
-3. If `agent-discordbot` is unavailable or unauthorized, stop and report that the Jobdori token path failed. Only then may a human decide whether to use `agent-discord`.
+3. If `agent-discordbot` is unavailable or unauthorized, stop and report that the release bot token path failed. Only then may a human decide whether to use `agent-discord`.
 
 4. Post the release announcement to channel `1454708427392680067` matching the style of previous announcements. The message should follow this structure:
 ```
@@ -414,9 +413,9 @@ Plus {summary of remaining changes}.
 ```
 
 ```bash
-JOBDORI_BOT_ID=1486173823354146917
+RELEASE_BOT_ID=1486173823354146917
 RELEASE_URL=$(gh release view "v${NEW_VERSION}" --json url --jq '.url')
-agent-discordbot message send 1454708427392680067 "{your message following the style above}" --bot "$JOBDORI_BOT_ID"
+agent-discordbot message send 1454708427392680067 "{your message following the style above}" --bot "$RELEASE_BOT_ID"
 ```
 
 If the message fails to send, warn the user and continue — do NOT block the publish workflow on Discord errors.

package/README.de.md

@@ -12,11 +12,6 @@
 > | :-----| :----- |
 
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Lerne Dori kennen. Keine Demo. Abonniert einfach alles.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
-> > **OmO wird von Jobdori betreut, dem oben gezeigten KI-Assistenten. Lerne deinen eigenen Jobdori kennen: Dori. <br />Trag dich [hier](https://sisyphuslabs.ai) auf die Warteliste ein.**
-
 > [!TIP]
 > Sei dabei!
 >

package/README.es.md

@@ -12,11 +12,6 @@
 > | :-----| :----- |
 
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Conoce a Dori. No es una demo. Se suscribe a todo.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
-> > **OmO es mantenido por Jobdori, el asistente de IA que se muestra arriba. Conoce a tu propio Jobdori, Dori. <br />Únete a la lista de espera [aquí](https://sisyphuslabs.ai).**
-
 > [!TIP]
 > ¡Acompáñanos!
 >

package/README.fr.md

@@ -12,11 +12,6 @@
 > | :-----| :----- |
 
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Découvrez Dori. Pas une démo. S'abonne à tout.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
-> > **OmO est maintenu par Jobdori, l'assistant IA présenté ci-dessus. Découvrez votre propre Jobdori, Dori. <br />Rejoignez la liste d'attente [ici](https://sisyphuslabs.ai).**
-
 > [!TIP]
 > Rejoignez-nous !
 >

package/README.it.md

@@ -12,11 +12,6 @@
 > | :-----| :----- |
 
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Scopri Dori. Non è una demo. Si abbona a tutto.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
-> > **OmO è mantenuto da Jobdori, l'assistente IA mostrato qui sopra. Scopri il tuo Jobdori personale, Dori. <br />Iscriviti alla lista d'attesa [qui](https://sisyphuslabs.ai).**
-
 > [!TIP]
 > Unisciti a noi!
 >

package/README.ja.md

@@ -13,11 +13,6 @@
 > | :-----| :----- |
 
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Meet Dori. Not a demo. Subscribes to everything.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
-> > **OmO は上記の Jobdori によってメンテナンスされています。あなた専用の Jobdori、Dori に会いましょう。 <br />[こちら](https://sisyphuslabs.ai) からウェイトリストにご登録ください。**
-
 > [!TIP]
 > 私たちと一緒に！
 >

package/README.ko.md

@@ -12,11 +12,6 @@
 > | [<img alt="OpenGateway" src="./.github/assets/opengateway-logo.svg" width="156px" />](https://opengateway.ai/) | **[OpenGateway](https://opengateway.ai/)**가 OmO를 후원하고 있습니다. 여러 모델 제공사를 하나의 API로 쓸 수 있는 OpenAI 호환 게이트웨이입니다. 오픈소스를 응원해주셔서 감사합니다. |
 > | :-----| :----- |
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Meet Dori. Not a demo. Subscribes to everything.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
-> > **OmO는 위의 Jobdori에 의해 메인테이닝되고 있습니다. 당신의 Jobdori, Dori를 만나세요. <br />대기 명단은 [여기](https://sisyphuslabs.ai)에서 받습니다.**
-
 > [!TIP]
 > 함께해요!
 >

package/README.md

@@ -12,11 +12,6 @@
 > | :-----| :----- |
 
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Meet Dori. Not a demo. Subscribes to everything.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
-> > **OmO is maintained by Jobdori, the AI assistant shown above. Meet your own Jobdori, Dori. <br />Join the waitlist [here](https://sisyphuslabs.ai).**
-
 > [!TIP]
 > Be with us!
 >
@@ -95,6 +90,10 @@ Opinionated defaults, adjustable if you insist. Your settings live in `~/.omo/om
 - [Computer use](docs/guide/computer-use.md) (experimental)
 - [Ultrawork Manifesto](docs/manifesto.md)
 
+## Reporting a bug
+
+The fastest way to report a bug is `/bug` inside a session (available in the omo app). It lists what it includes and lets you see the exact report before you send it, then sends it to the OmO team: the recent engine log, your environment and config with secrets blanked, the session transcript, and identity lines - your device name and, when telemetry is on, an install id and a session hash, plus your account details (email, name, account, user and device ids, plan, device name) when you report from the desktop app, so we can reply. Everything but the identity lines goes through the upload redactor. GitHub issues stay open for anyone who cannot use the in-app report.
+
 ## Reviews
 
 > "It made me cancel my Cursor subscription. Unbelievable things are happening in the open source community." - [Arthur Guiot](https://x.com/arthur_guiot/status/2008736347092382053?s=20)

package/README.pt-br.md

@@ -12,11 +12,6 @@
 > | :-----| :----- |
 
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Conheça Dori. Não é uma demo. Assina tudo.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
-> > **O OmO é mantido por Jobdori, o assistente de IA mostrado acima. Conheça seu próprio Jobdori, Dori. <br />Entre na lista de espera [aqui](https://sisyphuslabs.ai).**
-
 > [!TIP]
 > Junte-se a nós!
 >

package/README.ru.md

@@ -13,12 +13,6 @@
 > | :-----| :----- |
 
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Meet Dori. Not a demo. Subscribes to everything.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
->
-> > **OmO поддерживается Jobdori, ИИ-ассистентом, показанным выше. Познакомьтесь со своим Jobdori, Dori. <br />Присоединяйтесь к листу ожидания [здесь](https://sisyphuslabs.ai).**
-
 > [!TIP] Будьте с нами!
 >
 > | [<img alt="Discord link" src="https://img.shields.io/discord/1452487457085063218?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=flat-square" width="156px" />](https://discord.gg/PUwSMR9XNk) | Вступайте в наш [Discord](https://discord.gg/PUwSMR9XNk), чтобы общаться с контрибьюторами и пользователями OmO. |

package/README.zh-cn.md

@@ -13,11 +13,6 @@
 > | :-----| :----- |
 
 
-> [!NOTE]
->
-> [![Sisyphus Labs - Meet Dori. Not a demo. Subscribes to everything.](./.github/assets/sisyphuslabs.png?v=4)](https://sisyphuslabs.ai)
-> > **OmO 由上述的 Jobdori 进行维护。认识你专属的 Jobdori, Dori。<br />[在此处](https://sisyphuslabs.ai)加入等待名单。**
-
 > [!TIP]
 > 加入我们！
 >

package/dist/agents/atlas/agent.d.ts

@@ -7,7 +7,8 @@
  * 1. Claude Opus 4.7       → opus-4-7.md   (literal-following + explicit fan-out push)
  * 2. GPT family            → gpt.md        (shared GPT-family calibration)
  * 3. Gemini family         → gemini.md
- * 4. Kimi K3              → kimi-k3.md    (K3-native; checked first among Kimi)
+ * 4. Kimi K3.1            → kimi-k3-1.md  (own copy of kimi-k3.md; checked before K3)
+ * 4b. Kimi K3             → kimi-k3.md    (K3-native; checked first among the rest of Kimi)
  * 5. Kimi K2.7             → kimi-k2-7.md  (restrained, outcome-first; checked before generic kimi)
  * 6. Kimi K2.x family      → kimi.md       (Claude-family base + K2.6 thinking-mode calibration)
  * 7. GLM family            → glm.md        (GLM 5.2 calibration)
@@ -18,7 +19,7 @@ import type { AgentMode, AgentPromptMetadata } from "../types";
 import type { AvailableAgent, AvailableSkill } from "../dynamic-agent-prompt-builder";
 import type { CategoryConfig } from "../../config/schema";
 declare const MODE: AgentMode;
-export type AtlasPromptSource = "default" | "gpt" | "gemini" | "kimi" | "kimi-k3" | "kimi-k2-7" | "opus-4-7" | "glm";
+export type AtlasPromptSource = "default" | "gpt" | "gemini" | "kimi" | "kimi-k3" | "kimi-k3-1" | "kimi-k2-7" | "opus-4-7" | "glm";
 export declare function getAtlasPromptSource(model?: string): AtlasPromptSource;
 export interface OrchestratorContext {
     model?: string;

package/dist/agents/sisyphus/index.d.ts

@@ -28,3 +28,4 @@ export { buildGlm52SisyphusPrompt } from "./glm-5-2";
 export { buildKimiK26SisyphusPrompt } from "./kimi-k2-6";
 export { buildKimiK27SisyphusPrompt } from "./kimi-k2-7";
 export { buildKimiK3SisyphusPrompt } from "./kimi-k3";
+export { buildKimiK31SisyphusPrompt } from "./kimi-k3-1";

package/dist/agents/sisyphus/kimi-k3-1.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Kimi K3.1 Sisyphus prompt: its own copy of kimi-k3.ts (Q, 2026-10-24), so later K3 tuning never
+ * changes what K3.1 sees. Copied at omo dev de27f2ebfa; only the identity line and the function names
+ * differ. Tune it on K3.1 evidence from here on. The K3 design notes in kimi-k3.ts applied at the copy.
+ */
+import type { AvailableAgent, AvailableTool, AvailableSkill, AvailableCategory } from "../dynamic-agent-prompt-builder";
+import { categorizeTools } from "../dynamic-agent-prompt-builder";
+export declare function buildKimiK31SisyphusPrompt(model: string, availableAgents: AvailableAgent[], availableTools?: AvailableTool[], availableSkills?: AvailableSkill[], availableCategories?: AvailableCategory[], useTaskSystem?: boolean): string;
+export { categorizeTools };

package/dist/agents/sisyphus-agent-factory.d.ts

@@ -9,7 +9,7 @@ declare const MODE: AgentMode;
  * runtime model resolves to a different family than the configured one, the baked
  * body is the wrong family and must be rebuilt (issue #5297/#5316).
  */
-export type SisyphusPromptFamily = "kimi-k3" | "kimi-k2-7" | "kimi-k2-6" | "gpt-5-5" | "gpt-5-4" | "claude-fable-5" | "claude-opus-5" | "claude-opus-4-8" | "claude-opus-4-7" | "glm-5-2" | "grok-4" | "fallback";
+export type SisyphusPromptFamily = "kimi-k3-1" | "kimi-k3" | "kimi-k2-7" | "kimi-k2-6" | "gpt-5-5" | "gpt-5-4" | "claude-fable-5" | "claude-opus-5" | "claude-opus-4-8" | "claude-opus-4-7" | "glm-5-2" | "grok-4" | "fallback";
 export declare function resolveSisyphusPromptFamily(model: string): SisyphusPromptFamily;
 export declare function createSisyphusAgent(model: string, availableAgents?: AvailableAgent[], availableToolNames?: string[], availableSkills?: AvailableSkill[], availableCategories?: AvailableCategory[], useTaskSystem?: boolean): AgentConfig;
 export declare namespace createSisyphusAgent {

package/dist/agents/sisyphus-junior/agent.d.ts

@@ -21,7 +21,7 @@ export declare const SISYPHUS_JUNIOR_DEFAULTS: {
     readonly model: "anthropic/claude-sonnet-5";
     readonly temperature: 0.1;
 };
-export type SisyphusJuniorPromptSource = "default" | "kimi-k2" | "kimi-k2-7" | "kimi-k3" | "gpt" | "gpt-5-5" | "gpt-5-4" | "gemini" | "glm-5-2";
+export type SisyphusJuniorPromptSource = "default" | "kimi-k2" | "kimi-k2-7" | "kimi-k3" | "kimi-k3-1" | "gpt" | "gpt-5-5" | "gpt-5-4" | "gemini" | "glm-5-2";
 export declare function getSisyphusJuniorPromptSource(model?: string): SisyphusJuniorPromptSource;
 /**
  * Builds the appropriate Sisyphus-Junior prompt based on model.

package/dist/agents/sisyphus-junior/index.d.ts

@@ -2,6 +2,7 @@ export { buildDefaultSisyphusJuniorPrompt } from "./default";
 export { buildKimiK26SisyphusJuniorPrompt } from "./kimi-k2-6";
 export { buildKimiK27SisyphusJuniorPrompt } from "./kimi-k2-7";
 export { buildKimiK3SisyphusJuniorPrompt } from "./kimi-k3";
+export { buildKimiK31SisyphusJuniorPrompt } from "./kimi-k3-1";
 export { buildGptSisyphusJuniorPrompt } from "./gpt";
 export { buildGpt54SisyphusJuniorPrompt } from "./gpt-5-4";
 export { buildGpt55SisyphusJuniorPrompt } from "./gpt-5-5";

package/dist/agents/sisyphus-junior/kimi-k3-1.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Kimi K3.1 Sisyphus-Junior prompt: its own copy of kimi-k3.ts (Q, 2026-10-24), so later K3 tuning never
+ * changes what K3.1 sees. Copied at omo dev de27f2ebfa; only the identity line and the function names
+ * differ. Tune it on K3.1 evidence from here on. The K3 design notes in kimi-k3.ts applied at the copy.
+ */
+export declare function buildKimiK31SisyphusJuniorPrompt(useTaskSystem: boolean, promptAppend?: string): string;

package/dist/agents/types.d.ts

@@ -1,6 +1,6 @@
 import type { AgentConfig } from "@opencode-ai/sdk";
-import { isClaudeFable5Model, isClaudeFableOrMythosModel, isClaudeOpus46Model, isClaudeOpus47Model, isClaudeOpus47OrLaterModel, isClaudeOpus48Model, isClaudeOpus5Model, isGeminiModel, isGlmModel, isGptModel, isGrok45Model, isGrok46Model, isKimiK2CodeModel, isKimiK2Model, isKimiK27Model, isKimiK28Model, isKimiK3Model, isMiniMaxModel } from "@oh-my-opencode/model-core";
-export { isClaudeFable5Model, isClaudeFableOrMythosModel, isClaudeOpus46Model, isClaudeOpus47Model, isClaudeOpus47OrLaterModel, isClaudeOpus48Model, isClaudeOpus5Model, isGeminiModel, isGlmModel, isGptModel, isGrok45Model, isGrok46Model, isKimiK2CodeModel, isKimiK2Model, isKimiK27Model, isKimiK28Model, isKimiK3Model, isMiniMaxModel, };
+import { isClaudeFable5Model, isClaudeFableOrMythosModel, isClaudeOpus46Model, isClaudeOpus47Model, isClaudeOpus47OrLaterModel, isClaudeOpus48Model, isClaudeOpus5Model, isGeminiModel, isGlmModel, isGptModel, isGrok45Model, isGrok46Model, isKimiK2CodeModel, isKimiK2Model, isKimiK27Model, isKimiK28Model, isKimiK3Model, isKimiK31Model, isMiniMaxModel } from "@oh-my-opencode/model-core";
+export { isClaudeFable5Model, isClaudeFableOrMythosModel, isClaudeOpus46Model, isClaudeOpus47Model, isClaudeOpus47OrLaterModel, isClaudeOpus48Model, isClaudeOpus5Model, isGeminiModel, isGlmModel, isGptModel, isGrok45Model, isGrok46Model, isKimiK2CodeModel, isKimiK2Model, isKimiK27Model, isKimiK28Model, isKimiK3Model, isKimiK31Model, isMiniMaxModel, };
 /**
  * Anthropic Opus 4.7+, Fable, and Mythos models reject thinking.type "enabled";
  * they require adaptive thinking plus an effort, which OpenCode core derives from