[Question]: Any plan to follow OpenCode PR #20259 for Kimi system prompt optimization? · Issue #2990 · code-yeongyu/oh-my-openagent · GitHub
Skip to content

[Question]: Any plan to follow OpenCode PR #20259 for Kimi system prompt optimization? #2990

Closed

Description

@Meteor-3

Prerequisites

  • I will write this issue in English (see our Language Policy)
  • I have searched existing issues and discussions
  • I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer
  • This is a question (not a bug report or feature request)

Question

Hi, I noticed OpenCode already merged PR #20259 for Kimi:
anomalyco/opencode#20259

Does OMO have any plan to follow or adapt that change as well?

Context

From what I understand, OMO uses a different prompt architecture, so this would probably need adaptation rather than a direct copy.

Doctor Output (Optional)

Question Category

Other

Additional Information

No response

Activity

  1. changed the title [-][Question]: Any plan to follow OpenCode PR #20259 for Kimi?[/-] [+][Question]: Any plan to follow OpenCode PR #20259 for Kimi system prompt optimization?[/+] on Apr 1, 2026
  2. code-yeongyu commented on May 15, 2026

    @code-yeongyu
    Owner

    [sisyphus-bot]

    OMO already has Kimi-specific adaptation rather than a direct copy of OpenCode's prompt.

    Current source/docs show:

    • Sisyphus has a Kimi K2.x-native prompt implementation in src/agents/sisyphus/kimi-k2-6.ts.
    • That prompt is explicitly tuned around K2.x behavior and is separate from the Claude/GPT prompt style.
    • Atlas also routes Kimi K2.x models to a dedicated Kimi prompt path.
    • The model matching docs recommend Kimi K2.5/K2.6 as Claude-family alternatives for Sisyphus-style orchestration.

    So the answer is effectively yes: OMO follows the same need at the architecture level, but via OMO-specific prompt routing and Kimi-native prompts rather than directly copying the upstream OpenCode change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions