Feature request: configurable default swarm mode

Problem

Currently, swarm mode must be enabled manually every session via /swarm on or per-task via /swarm <task>. There is no persistent configuration option to start new sessions with swarm mode already enabled.

Use case

Users who consistently want parallel subagent delegation for their workflows have to remember to toggle swarm mode at the start of every session. A config default would remove this friction and make swarm mode a first-class preference alongside other defaults like default_thinking, default_permission_mode, and default_plan_mode.

Proposed solution

Add a top-level config option in ~/.kimi-code/config.toml:

default_swarm_mode = false   # or true

When set to true, new interactive sessions would start with swarm mode enabled (equivalent to the user having typed /swarm on).

Alternatively, it could live under an [experimental] or [swarm] table:

[swarm]
default_enabled = false

Additional considerations

• Should be overridable via CLI flag (e.g., kimi --no-swarm / kimi --swarm) for one-off sessions.
• Could also respect an environment variable such as KIMI_SWARM_MODE=1.
• Existing /swarm on|off behavior within a session should remain unchanged.

Related

• /swarm slash command added in v0.12.0
• PR #569 removed the experimental gate for swarm mode but did not add a startup default

Thanks for considering this!

Start by tracing the existing /swarm on|off handling and the configuration loading for ~/.kimi-code/config.toml; PR #569 provides related context. Decide how the proposed default, session overrides, and any CLI or environment override should interact, then verify that new sessions honor the setting while existing in-session behavior remains unchanged.