My Wiki!

**This is an old revision of the document!**

Table of Contents

Kilo Code for VS Code (Insider)

Requirements:

  • I want to have research agent (web) that is available for all project, sothat I can do structured web search on topics.
  • The research agent should store it's research memory as text (.md) files in local project folder structure for to create growing context for the project. ## Custom Modes and Agents

Kilo discovers these files via glob patterns in multiple config directories:

Scope Mode file path pattern Agent file path pattern

Project-local .kilo/modes/.md .kilo/agents/.md

Global (XDG) ~/.config/kilo/modes/.md ~/.config/agents/modes/.md

Legacy global ~/.kilo/modes/.md or ~/.kilocode/modes/.md

Agent Memory

Folder and Manifest Best Practices

Put source documents, manifests, helper files, and output directories in the Manifest instead of pasting large content into the prompt.

Put longer task instructions in workspace files such as README.md, task.md, or AGENTS.md; keep agent instructions focused on behavior and boundaries.

Use stable document IDs and a machine-readable manifest file so generated memos can cite sources and reviewers can inspect the path back to evidence.

Let Memory() manage its own memory artifacts. By default, sandbox memory uses memories/ and sessions/ under the workspace.

Keep generated artifacts under outputs/ so the application can inspect, copy, validate, or archive them after the run.

Keep mount scopes narrow. If you mount a data room, mount only what the agent should read or write.

Treat secrets as runtime configuration injected by your application or sandbox provider, not as prompt text or committed manifest content.

Prefer a small synthetic File(…) or Dir(…) entry for a tutorial, then switch to LocalDir, GitRepo, or storage mounts for production-sized datasets .

This is a visual preview of the sandbox workspace structure

.

The next cell builds the actual Manifest entries manually.

WORKSPACE_TREE = """
/workspace/
  README.md
  manifest.csv
  docs/
    batch_1/
    batch_2/
    batch_3/
  outputs/
  memories/    # Generated by Memory()
  sessions/    # Generated by Memory()
""".strip()

print(WORKSPACE_TREE)

Prepare a Small Evidence Workspace

memvid mcp for vscode

Install npm, uv on windows

Install npm as non admin

Running npm on Windows without administrator rights requires using portable binaries or installing Node.js within your user profile directory. Download the Node.js binary (.zip) and extract it to a folder like C:\Users\YourUser\nodejs. Then, update your user PATH environment variable to include this directory.

Steps to Run npm as Non-AdminDownload Portable Node.js:

Download the Windows Binary (.zip) from the official site.

Extract: Unzip the files into a directory you have write access to, such as C:\Users\YourName\Documents\nodejs.

Update Path (Temporary): Open a command prompt (cmd.exe) and run:set PATH=C:\Users\YourName\Documents\nodejs;%PATH%.

Update Path (Permanent):Search for “Edit environment variables for your account” in Windows search.Select Path, click Edit, then New and add the path to your extracted folder.

Verify: Run node -v and npm -v to ensure they work.

Key Tips for Non-Admin UsageAvoid Global Installs:

  • Do not use npm install -g. Instead, install packages locally within your project folder or use npx to run commands.
  • Portable NPM: If you need a specific npm version, you can download it and link it directly via node bin/npm-cli.js install npm -gf.
  • Fixing “Not Recognized”: If npm is not recognized, it means the PATH was not updated correctly in your terminal session.

Trace: • kilocode_vscode

Navigation