Back to Signal Feed
CodeTracked since May 18, 2026

Rulesync enforces explicit Kilo subagent frontmatter validation

This pull request replaces the old alias-based handling of Kilo subagent frontmatter with a dedicated schema that explicitly lists supported Kilo fields and uses it for runtime parsing/validation, so invalid values are rejected at config load time instead of passing silently.

rulesyncKiloSubagentKiloSubagentFrontmatterSchemaZod

What Happened

  • This pull request replaces the old alias-based handling of Kilo subagent frontmatter with a dedicated schema that explicitly lists supported Kilo fields and uses it for runtime parsing/validation, so invalid values are rejected at config load time instead of passing silently.
  • This pull request replaces the old alias-based handling of Kilo subagent frontmatter with a dedicated schema that explicitly lists supported Kilo fields and uses it for runtime parsing/validation, so invalid values are rejected at config load time instead of passing silently.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Added a dedicated runtime-validated Kilo frontmatter schema and wired `KiloSubagent` parsing/validation to it, replacing fallback validation via the parent schema so supported Kilo settings become explicit and type-safe.

Why Track This

Why It Matters

Developers and operators using rulesync with Kilo subagents will now see immediate configuration errors when they specify bad agent-frontmatter values, which reduces silent misconfiguration and helps avoid broken agent runs later in deployment pipelines. The update introduces `KiloSubagentFrontmatterSchema` as the authoritative field set for `displayName`, `temperature`, `model`, and related Kilo options, and makes `KiloSubagent.validate()`/`fromRulesyncSubagent` enforce it with Zod at runtime while still allowing unknown future Kilo fields via loose passthrough. Watch for any existing subagent configs that relied on permissive parsing, and monitor CI or startup logs after rollout for newly surfaced validation failures.

Impact

Developers and operators using rulesync with Kilo subagents will now see immediate configuration errors when they specify bad agent-frontmatter values, which reduces silent misconfiguration and helps avoid broken agent runs later in deployment pipelines. The update introduces `KiloSubagentFrontmatterSchema` as the authoritative field set for `displayName`, `temperature`, `model`, and related Kilo options, and makes `KiloSubagent.validate()`/`fromRulesyncSubagent` enforce it with Zod at runtime while still allowing unknown future Kilo fields via loose passthrough. Watch for any existing subagent configs that relied on permissive parsing, and monitor CI or startup logs after rollout for newly surfaced validation failures.

What To Watch Next

  • Watch whether rulesync becomes a repeated pattern.
  • Track follow-up changes around Tool Calling.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: strict_validation_breaks_existing_configs, permissive_custom_fields_become_hidden_failures.
Open Topic TimelineOpen Technical EventOpen Original Sourcestrict_validation_breaks_existing_configs / permissive_custom_fields_become_hidden_failures / new_parse_time_errors_needing_quick_rollback_plans

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

dyoshikawa/rulesync PR #1655: feat(kilo): explicitly declare supported Kilo agent frontmatter fields

Rulesync now validates Kilo subagent frontmatter against an explicit schema, making unsupported or malformed fields fail fast.