Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I believe this is a bug. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: macOS 26.1
- Continue version: 1.2.10
- IDE version: VS Code 1.105.1 (Universal)
- Model: Any
- config:
  
name: redacted
version: 1.0.0
schema: v1

models:
  - name: llama3.1:8b
    provider: ollama
    apiBase: http://redacted:11434
    model: llama3.1:8b
    roles:
      - chat
      - edit
      - apply
      - summarize
    capabilities:
      - tool_use
  - name: gpt-oss:20b
    provider: ollama
    apiBase: http://redacted:11434
    model: gpt-oss:20b
    roles:
      - chat
      - edit
      - apply
      - summarize
    capabilities:
      - tool_use
  - name: qwen2.5-coder
    provider: ollama
    apiBase: http://redacted:11434
    model: qwen2.5-coder
    roles:
      - autocomplete

Description

When using the extension Settings > Rules > Create new rule, the resulting .md file is hard-coded with a file name new-rule.md. We should either be prompted to name this prior to file creation, or the extension should be able to rename them. The user should not have to:

1. right click the open file and reveal in finder
2. the rename there
3. then reload the extension to pick up the change

To reproduce

1. Click the pencil in the chat to open the rules editor
2. Click the + and create a new rule
3. FIle will be named new-rule.md
4. User is not prompted to provide a non-generic file name
5. User has no way to rename the file other than finding it in the local file system and renaming it outside VS Code

Log output