Skip to content

Add initial kilo-dev memory bank system documentation #771

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

hassoncs
Copy link
Contributor

Introduces initial documentation for the Kilo Code memory bank system. Includes instructions on core functionality, key files (overview, architecture, tech, tasks), and workflows (initialization, update, task execution). Also adds initial content for the architecture, overview, tasks, and tech memory bank files.

From: https://kilocode.ai/docs/advanced-usage/memory-bank

Kilo Code added 2 commits June 18, 2025 22:10
Terminal sessions now include a `$WORKSPACE_ROOT` environment variable pointing to the workspace root. In multi-workspace setups, this points to the folder containing the active file.

This allows the agent to easily navigate to the workspace root from within the terminal using commands like `cd $WS_ROOT/webview && npx jest`.
This allows for repeatable running of commands that are relative to the workspace root!

Test plan: Tried it out with my local memory bank and now my agent easily re-runs tests in sub directories!
Introduces initial documentation for the Kilo Code memory bank system.
Includes instructions on core functionality, key files (overview, architecture, tech, tasks), and workflows (initialization, update, task execution).
Also adds initial content for the architecture, overview, tasks, and tech memory bank files.
Copy link

changeset-bot bot commented Jun 19, 2025

⚠️ No Changeset found

Latest commit: ef4cb8a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@EamonNerbonne
Copy link
Contributor

Looks sane to me - you want to experiment with memory-bank, I take it?

@hassoncs hassoncs force-pushed the ws-root-env-var branch 2 times, most recently from 96a5426 to d860c38 Compare June 19, 2025 17:29
## Mode System

- **Architect Mode**: Can only edit `.md` files - for documentation and planning
- **Code Mode**: Full file access - primary implementation mode
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add 'ask mode' as well? No file editing powers, can only answer questions about the code base.

@hassoncs hassoncs force-pushed the ws-root-env-var branch 2 times, most recently from 93456e0 to 2613b09 Compare June 20, 2025 16:26
Base automatically changed from ws-root-env-var to main June 20, 2025 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants