Numerous errors using the ‘compare models’ view

[matt-buchanan]

Been trying out models via the repo interface. The compare view seems pretty broken - I've not been able to run anything in it. 3 main issues:

• When trying to run a prompt from the compare view, I get an error along the lines of "Cannot read properties of undefined (reading 'max_tokens')" (although it is sometimes something other than max tokens)
• when trying to commit changed to the repo, I initially got an invalid token ('<') error, although that was only on creation of a new file.
• the screen layout of the compare view is not rendering correctly - will try to attach a screenshot, but in effect the comparison UI is only rendering a single column on the left side of the page, rather than expanding to fill the page.

Are these known issues with the service? I tried searching but didn't see anyone else reporting these exact issues.

[dorochadev]

Hi @matt-buchanan,

From what you’ve described, it sounds like a combination of UI bugs and possible API inconsistencies. A few things to check or try:

1. “Cannot read properties of undefined” / max_tokens errors: This usually happens when the model configuration isn’t fully loaded or a parameter is missing. Make sure your prompt is selecting a model that’s fully available in the repo, and try refreshing the page before running the compare.

2. Invalid token (‘<’) on new file creation: That can happen if the commit request is being malformed—sometimes due to extra characters in the token or copy-paste issues. Try regenerating your token and ensure there are no extra characters when adding it to the UI.

3. Layout/rendering issues: Compare view UI glitches like the single-column rendering are often browser-related. Clearing cache, trying a different browser, or resizing the window can sometimes temporarily fix it.

If these persist, it would be great to attach screenshots and browser info to a GitHub issue so the maintainers can debug.

[ramasheshasai]

Hi there,

Thanks for sharing the details — the errors you’re seeing in the compare view don’t look isolated. A few people have reported similar issues recently with the repo interface, especially around prompts not running and UI layout not rendering properly.

From what you described:

• The "Cannot read properties of undefined (reading 'max_tokens')" error usually points to a frontend bug in how the compare tool is handling parameters.
• The invalid token ('<') error when committing a new file sounds like a parsing issue, which sometimes happens if the editor is sending malformed data.
• The single-column rendering issue also suggests that the compare UI is not loading styles or layouts fully.

It doesn’t seem to be something wrong on your side — more likely a service-side or frontend bug. I haven’t seen an official fix posted yet, so the best next step would be:

• Clear cache / try in a fresh browser session to rule out local issues.
• If the problem persists, open a support ticket with GitHub so the engineering team can track it properly.
• Keep an eye on the GitHub changelog or discussions for updates, since these look like recent regressions.

In short, you’re not alone in hitting these problems — they’re likely known issues, just not fully documented yet.