Repository navigation
Release 1.10.0: native Kimi integration and learning support - #88
Merged
Merged
Conversation
ytvee
marked this pull request as ready for review
November 3, 2026 10:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem and result
Kimi discovered WebDev skills but lacked a complete native integration. This release candidate packages 23 skills, nine bounded roles, startup policy, opt-in capture, and a Kimi proposal/text-evaluation engine.
The follow-up audit found functional and privacy problems in the initial PR. They are corrected in this branch; authenticated runtime acceptance remains required before publication.
Audit findings and fixes
.agents/AGENTS.mdis not a Kimi startup instruction location.kimi-code/AGENTS.md; preserve surrounding host instructions, use atomic writes and unique backups..agentsas a plugin copies project facts, memory and attachments into the user-wide plugin cache--kimi-model, pin one configured alias across both A/B arms, snapshot config/environment fingerprints, reject drift, record configured rather than provider-observed identity.The evaluator denies tools and subagents, uses JSON-encoded file-based evidence with template-variable protection, rejects error/tool stream records, and does not pass large evidence through argv. Visual attachments remain metadata-only. Role names do not select models; existing Kimi secondary-model settings control routing.
Evidence reviewed
Official Kimi documentation and source at MoonshotAI/kimi-code 244819a:
Verification
python scripts/validate_skill_pack.py: source, graph, budgets, generated targets, archives and cross-client contracts passed.git diff --checkpassed.Installation documentation follow-up
Added a task-based MCP checklist (Context7, Playwright, GitHub, conditional Figma), CLI/VS Code configuration steps and a credential-free example. Documented Desktop browser, Browser Extension and Computer Use setup, Windows/macOS requirements, model/permission choices, main-session browser verification, and current subagent limitations. Official provider documentation is linked in the guide.
Documentation head: d771261. Full local pack validation, install-guide validation, links and whitespace checks passed. quality-ci and link-check passed for this documentation-only commit; skill-pack-ci is still running. No client configuration or credentials were changed.
Remaining release gates
Authenticated current Kimi v2: startup/skill discovery, a real bounded role handoff, capture on/off and isolation, proposal generation and same-model A/B. Live Kimi execution on Windows also needs observed acceptance; helper regression tests already pass there. Synthetic checks are not live Kimi certification.
Kimi Stop exposes no final assistant response; tool output is capped upstream. These are documented client limits, not full-transcript capture. Text benchmarks cannot certify real coding behavior.
Scope and rollout
Version 1.10.0 metadata and release packaging are prepared; PR remains draft. No merge, tag or release publication. No new dependency or test infrastructure. Existing host instructions, model credentials and capture consent are preserved. Normal frontend work or installing the package must not enable learning/capture.