Skip to content

fix(kimi-for-coding): inherit attachment support for K3 models - #6102

Open
ysntony wants to merge 1 commit into
anomalyco:devfrom
ysntony:fix/kimi-for-coding-k3-attachment
Open

fix(kimi-for-coding): inherit attachment support for K3 models#6102
ysntony wants to merge 1 commit into
anomalyco:devfrom
ysntony:fix/kimi-for-coding-k3-attachment

Conversation

@ysntony

@ysntony ysntony commented Sep 2, 2026

Copy link
Copy Markdown

What

Drops the stale attachment = false override from k3.toml and k3-256k.toml under providers/kimi-for-coding/, letting the flag inherit true from the moonshotai/kimi-k3 lab base (per the repo's override-only rule for base_model files).

Why

Both models accept image input on the Kimi For Coding endpoint, and k3 also accepts video. This is reflected in Kimi Code's own subscription model catalog (the OAuth-managed provider in the Kimi Code CLI), which lists:

  • k3: image_in, video_in
  • k3-256k: image_in (no video)

The TOML files already declare matching [modalities]k3 inherits text/image/video input from the lab base, and k3-256k declares text/image with a header comment noting "accepts no video input (image only)". The attachment = false override contradicted those modalities and makes the models unusable for image attach flows in tools that gate on the flag.

Same class of fix as #5793 (align attachment flag with modalities).

Validation

bun validate passes.

Both k3 and k3-256k inherit from the moonshotai/kimi-k3 lab base, which already declares attachment = true, so per the repo's override-only rule the correct fix is to drop the stale attachment = false override rather than flip it.
On the Kimi For Coding endpoint both models accept image input (k3 also accepts video), per Kimi Code's own subscription model catalog: k3 lists image_in and video_in, k3-256k lists image_in.
The declared [modalities] already match this (k3 inherits text/image/video from the base; k3-256k declares text/image), so the inherited flag is now consistent with modalities — same class of fix as anomalyco#5793.
@ysntony
ysntony force-pushed the fix/kimi-for-coding-k3-attachment branch from 09f2976 to b8b0b7b Compare September 3, 2026 04:02
@ysntony ysntony changed the title fix(kimi-for-coding): set attachment=true for k3 and k3-256k fix(kimi-for-coding): inherit attachment support for K3 models Sep 3, 2026
@ysntony
ysntony marked this pull request as ready for review September 3, 2026 04:09
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

No actionable findings.

@github-actions github-actions Bot added the reviewer: ready Automated review found no actionable items label Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

reviewer: ready Automated review found no actionable items

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant