DevAgentRadar → Repo Harness Rule Patch

Goal: update our repository's permanent harness instructions based on this release.

Update the file that tool actually reads. Do not dump everything into one file.

• Claude Code → CLAUDE.md plus .claude/ (skills, hooks, settings, agents, commands). It does not read AGENTS.md natively; start CLAUDE.md with @AGENTS.md.
• Codex, Copilot, Cursor, Factory Droid, Grok Build, Roo Code, Goose, OpenCode, Amp, Zed, Aider → AGENTS.md.
• Gemini CLI / Antigravity → GEMINI.md. AGENTS.md only if context.fileName is set.
• Cursor glob-scoped rules → .cursor/rules/*.mdc (plain .md is ignored), not a second constitution.
• Codex MCP → .codex/config.toml, not .mcp.json.
• Copilot extra instructions → .github/copilot-instructions.md; custom agents → .github/agents/.
• Windsurf → .windsurf/rules (do not assume AGENTS.md).
• Cline → .clinerules.
• Procedures → a skill (SKILL.md). Enforcement the model must not skip → a hook. Isolated roles → subagents.
• Do not fork the same rule into three tool files.

Context

Assistant: Kilo Code Proposal: Add memory_model to kilo.jsonc and pin Agent Manager tabs with Shift+click Summary: Kilo Code v7.8.7 makes multi-project Agent Manager the default, adds kilo.jsonc memory_model, per-session Integrated Browser tabs, MCP OAuth sign-in, Shift+click tab pinning, and worktrees outside the project folder. Update kilo.jsonc and Agent Manager habits to match. Primary source: https://github.com/Kilo-Org/kilocode/releases/tag/v7.8.7

Why it matters

This pre-release removes the experimental toggle and the old single-project Agent Manager, so the current workspace is always first in a multi-project list. Restored tabs, background sessions, and branch defaults stay with their project, and removing the active project restores the remaining one—pin keepers with Shift+click so they survive that switch. Automatic project memory can now use a separate model through memory_model in kilo.jsonc; if that model is unset or unavailable, memory still uses the session model. Any session can open its own Integrated Browser editor tab via the Open Integrated Browser command or the browser_open tool. OAuth-protected MCP servers sign in through VS Code after Marketplace install, surface recovery actions in the prompt, and accept a pre-registered OAuth client when required. Pre-warmed Agent Manager worktrees now live outside the project folder: .kilo/worktrees/ is created only when you create a worktree, leftovers from earlier versions are removed, and projects on a different drive than home are no longer pre-warmed, so watchers and test runners stop seeing extra checkouts. Use Kilo Settings search (Ctrl+F / Cmd+F) to find Display shortcut hints and experimental Per-Conversation Prompt History.

Suggested actions

1. Open kilo.jsonc and add a memory_model field set to a cheaper or faster model id used only for automatic project memory saves; leave it unset if memory should keep using the current session model.
2. In Agent Manager, keep the current workspace project first, pin long-lived session tabs with Shift+click (the tab context menu now shows that gesture), and confirm restored tabs, background sessions, and branch defaults stay attached to their project after you switch or remove the active project.
3. Run the Open Integrated Browser command in any session, or let the browser_open tool reveal the tab automatically, so each session has its own editor browser tab rather than only Agent Manager sessions.
4. When installing an OAuth-protected MCP server from the Marketplace, complete the VS Code authorization prompt, configure a pre-registered OAuth client if the server requires one, and use the chat prompt recovery actions if a server still needs sign-in.
5. Stop expecting a persistent .kilo/worktrees/ checkout inside the repo: pre-warmed worktrees now live outside the project folder, .kilo/worktrees/ is created only when you create a worktree, leftover pre-warmed trees from earlier versions are removed automatically, and projects on a different drive than your home folder are no longer pre-warmed.

Config surfaces this release may change

• MCP servers — check your repo before applying
• subagent definitions — check your repo before applying

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/kilo-code-v7-8-7-add-memory-model-to-kilo-jsonc-and-pin-agent-manager-ta and mark Applied, Skipped, or Failed. Proposal id: 369e22bf-4440-4b93-8d82-646cfbe2382c

Instructions:

1. Read the existing context files and settings for the tools in this repo.
2. Draft an explicit Git diff. Update ONLY agent harness rules or tool configuration.
3. Call out deprecated flags, obsolete habits, or changed permission boundaries.
4. Do not touch application logic.

Start with the proposed diff and say which layer and which tool's file it belongs in.