Back to Kilocode

Rules & Workflows Sub-Tabs Parity

packages/kilo-vscode/docs/agent-behaviour/rules-workflows-subtab-parity.md

7.2.423.5 KB
Original Source

Rules & Workflows Sub-Tabs Parity

Priority: P2 (Rules), P3 (Workflows)

The legacy extension had feature-complete Rules and Workflows sub-tabs with toggle lists, file creation, and global/workspace separation. The new extension has a simpler Rules sub-tab and a stub Workflows sub-tab.

Rules Sub-Tab Comparison

FeatureLegacyNew
Description text + docs linkYesNo
Global rules sectionToggle list of global rule filesNot separated — single flat list of instruction file paths
Workspace rules sectionToggle list of workspace rule filesSame flat list
Per-rule enable/disable toggleToggleSwitch per rule fileNot available — paths are either in the list or removed
Create new rule fileInput field with validation (.md, .txt, or no extension) per sectionNot available
Add instruction file pathNot available (auto-discovered from filesystem)TextField + "Add" button
Rule source discoveryAuto-discovers from .kilocode/rules/, .kilocoderules, .roorules, .clinerules, mode-specific dirs, AGENTS.mdOnly shows explicitly configured paths in config.instructions

Key Architectural Difference

The legacy extension auto-discovered rule files from well-known filesystem locations and displayed them with on/off toggles. The new extension treats instruction files as explicit config entries — you add paths to config.instructions and they're always active. There's no discovery or toggling.

Workflows Sub-Tab Comparison

FeatureLegacyNew
Description text + docs linkYesPlaceholder: "Not yet implemented."
Global workflows sectionToggle list of global workflow filesNot available
Workspace workflows sectionToggle list of workspace workflow filesNot available
Per-workflow enable/disable toggleToggleSwitch per workflow fileNot available
Create new workflow fileInput field per sectionNot available
Invoke workflowType /workflow-name in chatCLI has custom commands (similar concept)

Remaining Work

Rules (P2)

  • Description text: Add explanatory description with link to docs, matching the legacy pattern
  • Global vs workspace separation: If the CLI distinguishes between global and workspace instruction files, separate them into two sections
  • Enable/disable toggles: If rules can be toggled without removing them from config, add toggle switches per rule
  • New rule file creation: Add a button/input to create a new rule file (not just add an existing path)
  • Auto-discovery: Consider adding a section showing auto-discovered rule sources (.kilocode/rules/, AGENTS.md) that the CLI loads regardless of explicit config.instructions entries

Workflows (P3)

  • Implement the sub-tab: Replace the placeholder with actual workflow management
  • Determine CLI mapping: The CLI has custom commands — determine whether "workflows" maps to CLI custom commands or is a distinct concept
  • Workflow file management: Add toggle list for global/workspace workflow files with create/enable/disable
  • Description text: Add explanatory description matching the legacy pattern

Notes

The existing non-agent-features/rules-and-workflows.md doc covers workflows broadly. This doc adds the specific UI comparison for what the sub-tabs look like in the Agent Behaviour tab. The CLI's config.instructions array is a simpler model than the legacy's auto-discovered toggle list — the extension may need to augment it with discovery logic to match parity.