Kilocode cheat sheet
The stuff you actually need. Updated 2026-04-02.
🚀 Get running in 5 minutes
- 1. Install from VS Code Marketplace: search 'Kilocode'
- 2. Sign in with your Kilocode account (or create one at kilocode.ai)
- 3. Open a project folder — Kilocode indexes your codebase automatically
- 4. Open the Kilocode sidebar panel (robot icon) and describe a task
- 5. Kilocode creates a plan and asks for approval before editing files
// daily_workflows
The things you'll actually do every day.
Start a new task
workflowbasicsDescribe what you want built or fixed in plain English. Kilocode breaks it into steps.
Click '+ New Task' in the sidebar or use Ctrl+Shift+K Review the plan before execution
safetyworkflowKilocode shows a step-by-step plan before touching your files. Approve, reject, or edit individual steps.
Click 'Approve Plan' or 'Edit Plan' in the task view Use Architect mode for big changes
modesrefactoringArchitect mode maps your codebase and plans multi-file refactors with full context.
Select 'Architect' from the mode dropdown before submitting a task Chat mode for questions without edits
modessafeAsk questions about your codebase without triggering any file edits.
Select 'Chat' mode — reads code but never writes Run auto mode for simple tasks
modesautomationFor clear, low-risk tasks, Auto mode executes without plan approval.
Select 'Auto' from mode dropdown — use carefully Apply a diff from the task result
reviewworkflowAfter Kilocode generates changes, review the diff and apply selectively.
Click file name in task result → review hunk → 'Apply' or 'Reject' Resume a paused task
workflowrecoveryKilocode pauses when it needs input or hits an ambiguity. Add context and continue.
Reply in the task thread and click 'Continue' Switch the model mid-task
modelsworkflowChange the underlying LLM for the current task without starting over.
Click the model selector in the task header ⚡ power_moves
Stuff most people don't know about.
Pin a .kilo rules file
Add project-specific instructions that apply to every task. Like CLAUDE.md for Kilocode.
Create .kilo/rules.md at your project root Persist coding conventions, file layout rules, and banned patterns across sessions.
Mention specific files in your task
Reference exact files so Kilocode focuses context on what matters.
Type @src/lib/models.ts in your task description Prevents wasted tokens on unrelated files and gives sharper output.
Use the task history panel
Every task is stored. Revisit, re-run, or fork previous tasks.
Click the clock icon in the sidebar to open task history Useful for iterating on a task that was close but not quite right.
Ask Kilocode to explain before editing
Use 'explain then ask' phrasing to get a code walkthrough before changes.
Prefix your task: 'First explain how X works, then...' Catches misunderstandings before Kilocode starts writing code.
Set a token budget
Cap how many tokens Kilocode can spend on a task to control cost.
Advanced settings → 'Max tokens per task' Prevents runaway usage on open-ended tasks.
Multi-file context with @folder
Include an entire directory as context.
@src/components/ in your task to include all files under that path Better for refactors where the change spans a whole module.
🔥 common_gotchas
Save yourself 30 minutes of debugging.
Kilocode edits unintended files
Use Architect mode and review the plan carefully. Add .kiloignore to exclude paths.
Task stalls with 'waiting for approval'
Check the sidebar for a pending approval prompt — it won't continue until you respond.
Context window exceeded on large codebase
Use @file mentions to narrow context. Switch to a model with a larger context window.
Auto mode applies changes before review
Switch to Architect or Manual mode for any non-trivial task. Auto is for quick one-liners only.
.kilo/rules.md not being picked up
Ensure the file is at the workspace root (same level as package.json or the top-level folder).
Diff looks correct but apply breaks the file
Review each hunk individually. Kilocode sometimes generates conflicts in files with unusual indentation.
/ commands
/new Start a fresh task in the current project.
💡 Clears previous task context entirely.
/explain Ask Kilocode to explain selected code without editing anything.
💡 Great for onboarding to unfamiliar codebases.
/plan Generate a plan for a task without executing it.
💡 Review and refine the plan before committing to execution.
/undo Revert the last set of file edits made by Kilocode.
💡 Works like Ctrl+Z but for AI edits — shows a diff before reverting.
💡 pro_tips
- › Add .kilo/rules.md immediately on any new project — the earlier the better.
- › Use Chat mode for exploration, Architect mode for implementation.
- › Reference specific files with @filename to keep context tight.
- › Review every plan before approving — the plan quality predicts the output quality.
- › For multi-step tasks, break them into subtasks rather than one giant prompt.
- › If a task goes sideways, /undo and re-run with a tighter description.
- › Kilocode uses the same model throughout a task — pick the right one upfront.
⚙️ configuration
.kilo/rules.md Project-level instructions for every task. Markdown format. Supports headings for sections.
default: none
recommended: Add coding conventions, architecture notes, and paths to avoid editing.
.kiloignore Paths Kilocode should never read or edit. Same syntax as .gitignore.
default: none
recommended: Add secrets/, build/, dist/, node_modules/ if not already in .gitignore.
kilocode.model Default model to use for tasks. Can also be changed per-task.
default: claude-sonnet-4-5
recommended: Use sonnet for most tasks; switch to opus for complex multi-file refactors.
kilocode.autoMode.enabled Whether Auto mode is available for tasks.
default: false
recommended: Leave false unless you trust the task scope. Architect mode is safer.