From f15c8e5325ef74bd4528b2d31fc0c5f22f775950 Mon Sep 17 00:00:00 2001 From: marius-kilocode Date: Mon, 22 Jun 2026 12:43:09 +0200 Subject: [PATCH] docs: clarify experimental flag settings --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index f36d4aea2fd..a54eb6aa140 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -53,7 +53,7 @@ All products are clients of the **CLI** (`packages/opencode/`), which contains t In each VS Code extension host, one `KiloConnectionService` is created for the sidebar, every Kilo editor tab, and Agent Manager; it lazily starts and reuses one current `kilo serve` backend at a time. Agent Manager worktree sessions pass a directory context to this shared backend rather than starting one per worktree. State captured by the active service layer, such as Snapshot `trackState`, is shared across those requests; only directory-keyed `InstanceState` data is isolated. -Extension-specific settings should live in the Kilo extension settings, not default VS Code settings, unless they are intentionally VS Code-wide. +Extension-specific settings should live in the Kilo extension settings, not default VS Code settings, unless they are intentionally VS Code-wide. Experimental flags should follow existing flag patterns, not VS Code settings; they usually belong in the Kilo Experimental settings section. ## Package Instructions