Skip to content

fix(config): kilo.json schema validation + z.ai/MiniMax provider setup - #1477

Merged
POWERFULMOVES merged 3 commits into
mainfrom
fix/kilo-json-schema-validation
May 16, 2026
Merged

POWERFULMOVES merged 3 commits into
mainfrom
fix/kilo-json-schema-validation

Conversation

@POWERFULMOVES

@POWERFULMOVES POWERFULMOVES commented May 15, 2026

Copy link
Copy Markdown
Owner

Summary

  • Fix config validation failure: kilo.json contained 8 unrecognized top-level keys causing Configuration is invalid warnings on every Kilo Code session
  • Register z.ai provider: 6 GLM models with dedicated coding API endpoint
  • Register MiniMax provider: 2 models per MINIMAX_INTEGRATION.md
  • Set defaults: primary model zai/glm-5-turbo, small model zai/glm-4-air

Changes

Commit 1: fix(config): migrate kilo.json to valid Kilo schema

Removes 8 invalid keys and remaps to valid schema fields. Adds permission block and skills paths. Preserves Authorization headers on remote MCP servers.

Commit 2: feat(config): add z.ai and MiniMax provider definitions

Adds provider block with two custom providers and model/small_model defaults.

Testing

  • Config validation passes (confirmed by Kilo Code IDE)
  • No functional code changes - configuration only
  • Submodule pointers and unrelated working tree changes excluded

Summary by CodeRabbit

  • Chores
    • Updated configuration schema with new agent and model selection structure for improved flexibility
    • Enhanced MCP server integration with support for multiple local and remote servers
    • Added improved permission and skills configuration management

Review Change Stack

hunnibear added 2 commits May 14, 2026 23:05
Remove 8 unrecognized keys that cause config validation failure:
- name, description, version, node (not valid top-level fields)
- agents, commands (defined via .kilo/agent/*.md and .kilo/command/*.md)
- context (replaced with instructions glob array)
- mcpServers (remapped to mcp with corrected sub-key names)
- references (not a valid config key)

Schema-corrected remapping:
- agents.primary -> default_agent
- context paths -> instructions glob array
- mcpServers -> mcp (stdio->local, streamable-http->remote,
  args->command, env->environment)
- description fields removed from MCP entries (not valid in schema)
- Authorization headers from origin/main preserved on remote MCP servers

Adds: permission block (bash/edit/read + z.ai MCP tool auto-approve),
skills paths declaration.

Refs: kilo-config skill schema, PMOVES-ClawZ/docs/providers/zai.md
…l registry

Register two custom providers in kilo.json:

z.ai (Z.AI Platform):
- baseURL: https://api.z.ai/api/coding/paas/v4 (dedicated coding API)
- Models: glm-5-turbo, glm-5.1, glm-4.7, glm-4.6, glm-4.6v, glm-4-air
- Default model: zai/glm-5-turbo (primary coding model)
- Small model: zai/glm-4-air (titles/summaries)
- Whitelist: glm-* (auto-approve all GLM variants)

MiniMax:
- baseURL: https://api.minimax.chat/v1
- Models: minimax-m2.7 (1M context), minimax-m2.1 (100K context)
- Whitelist: minimax-*
- Per MINIMAX_INTEGRATION.md and minimax_provider_cascade.yaml

Model mapping (per kilocode-glm.md agent doc):
- Claude sonnet/opus -> glm-5.1, haiku -> glm-4.5-air (for interop)
- MiniMax used for: long-context research, hyperdimensional ops,
  AGENT TRAILS, wave-function collapse, writing/vibes overflow

Refs: pmoves/docs/MINIMAX_INTEGRATION.md,
pmoves/tools/models/minimax_provider_cascade.yaml,
pmoves/docs/AGENTS/MINIMAX_GLM_PARITY_ANALYSIS.md
@coderabbitai

coderabbitai Bot commented May 15, 2026

Copy link
Copy Markdown
Contributor

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

Kilo.json undergoes a comprehensive configuration schema migration: legacy metadata and orchestration fields are replaced with a unified provider-centric structure, MCP servers are redefined as either local commands or remote endpoints, and capabilities are now gated by explicit skills and permission rules.

Changes

Configuration Schema Migration

Layer / File(s) Summary
Agent selection and provider configuration
kilo.json
default_agent, model, and small_model replace legacy metadata fields; instructions file list is added; unified provider section consolidates ZAI and MiniMax endpoints with baseURL, timeout, API key templating, and per-provider model whitelists.
MCP server endpoint configuration
kilo.json
MCP layout restructures zai-vision as a local command-based server and zai-web-search, zai-web-reader, zai-zread as remote HTTP servers with Authorization header support.
Skills and permission rules
kilo.json
Skills block defines available resource paths and URLs; permission rules explicitly allow bash, edit, and read capabilities with wildcard patterns for MCP server outputs.

🐰 A schema shaped anew in JSON's neat fold,
With agents and tools in a structure bold,
Permissions now guard what the system may do,
MCP endpoints glisten—both local and new! 🎯

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is missing the required Testing section with command output and lacks most required checkbox items. Add Testing section with specific commands/outputs confirming schema validation passes, and include all required checklist items from the template.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main changes: fixing config schema validation issues and setting up two providers (z.ai and MiniMax).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/kilo-json-schema-validation

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5b7d8da9a4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread kilo.json Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5b7d8da9a4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread kilo.json Outdated
Both custom OpenAI-compatible providers were missing options.apiKey,
causing unauthenticated requests that fail with 401. Refs Z_AI_API_KEY
and MINIMAX_API_KEY consistent with existing MCP Authorization headers.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants