Continue FIM requests not matching mux rule

[danbarr]

Describe the issue

Using Continue, my filename-based mux rules are not being matched.

CodeGate is correctly identifying type of request (FIM), and seems to be picking out the filename correctly - the breadcrumb on the event in the dashboard reads "Prompt on filepath: how-to/install.mdx". I have a mux rule for Chat & FIM requests, with a pattern of *.md* to use openai/gpt-4o-mini. But the event fell through to my default FIM rule which goes to ollama.

In the CodeGate container logs, I see:

2025-03-19T17:16:56.092657Z [warning  ] No path found in messages. Creating hash key from message. lineno=83 module=fim_cache pathname=/app/src/codegate/db/fim_cache.py

Steps to Reproduce

My mux rules:

The event, showing that ollama was used, not openai as expected:

Operating System

MacOS (Arm)

IDE and Version

VS Code 1.98.2

Extension and Version

Continue 1.0.4

Provider

OpenAI

Model

N/A

Codegate version

v0.1.30

Logs

No response

Additional Context

No response