You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 5, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 5, 2025. It is now read-only.
[Story]: Extend Muxing to Differentiate Between Chat and FIM Requests #1059
We currently support routing logic based on filenames, and now we need to extend that functionality to differentiate between chat requests and Fill-In-Middle (FIM) requests.
Example
A chat that references app.py → Model 1
A FIM request within app.py → Model 2
Implementation Outline
Extend the existing muxing rules to include a check for request type (chat or FIM).
Allow users to configure which model should handle chat requests vs. FIM for specific filenames.
changed the title [-][Story]: Extend muxing for support FIM and Chat requests[/-][+][Story]: Extend Muxing to Differentiate Between Chat and FIM Requests[/+]on Feb 14, 2025
Activity
[-][Story]: Extend muxing for support FIM and Chat requests[/-][+][Story]: Extend Muxing to Differentiate Between Chat and FIM Requests[/+]aponcedeleonch commentedon Mar 3, 2025
Closed by the tickets mentioned above