Skip to content

Model naming issues #383

@buraktamturk

Description

@buraktamturk

I current have a custom provider is configured with name "somename" and this "somename" provider has models configured let's say "glm-5.1" or "kimi-2.7-code". This "somename" is openai compatible provider.

When I create a new session, the model name sent to the this "somename" is "somename:glm-5.1". On previous releases, I was able to switch model to "glm-5.1" instead of "somename:glm-5.1" using /model command. However, right now this doesn't work. I can't configure the jcode to use "glm-5.1" instead of "somename:glm-5.1".

Additionally, this issue happens when a subagent is spawned. The model calls subagent tool with { ..., "model": "kimi-2.7-code", ... } (this is visible in /observe pane), however, the subagent fails with "model not found" error because it sends "somename:glm-5.1" to the provider.

I had similar issues on previous releases but I was able to overcome them by using "/model glm-5.1", now even if I pick that one, the agent is using "somename:glm-5.1" as model.

I am looking for a solution to this naming issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingduplicateThis issue or pull request already existspriority: highP1 - important bug or impactful feature, fix soontriage: fixed-pending-releaseFixed in code/committed; will close automatically on next releasetriage: reproducibleClear repro + clear fix path

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions