Browse documentation
Getting started
Configure
CLI reference
Extend
On this page
Context and files
Include project files in a request and carry important information through a conversation.
Start in your project folder#
Mirr Code explores the project relative to the folder where you start it. If you have several projects, change to the one you want before running mirr.
Not every file is included in the conversation at once. Mirr Code searches and reads files as needed for the request. If a particular file matters, include its name or path.
Select a file directly#
Type @ in the input box to find and select a file. For example, select the login screen file, then enter:
Add a password reset link below the login button in this file.
Keep the existing button's color and size.
Selecting a file helps distinguish it from similarly named screens. You can search using Korean filenames too.
Continue a long conversation#
Context means information used for the task: your requests, files already read, and decisions made so far. Use /compact to summarize a long conversation and continue. See Sessions and recovery to return to an earlier conversation.
When changing direction, state the new constraint: “Keep the design and fix only the login error.” If another program has changed a file, mention that too.
Protect sensitive information#
Do not paste passwords, authentication tokens, or customers' personal information into requests. Use examples with secrets removed and select only the files needed. See Tools and permissions for file and command access.
