# The new version of Qoder has quite a few issues.

**URL:** <https://forum.qoder.com/t/the-new-version-of-qoder-has-quite-a-few-issues/12571>\
**Category:** Bug Reports\
**Tags:** quest-mode, settings, others\
**Created:** [September 18, 2026, 1:09am UTC](https://forum.qoder.com/t/the-new-version-of-qoder-has-quite-a-few-issues/12571 "2026-09-18T01:09:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![辉辉\_侯](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.qoder.com/%E8%BE%89%E8%BE%89_%E4%BE%AF/32/6158_2.png) [@辉辉\_侯](https://forum.qoder.com/u/%E8%BE%89%E8%BE%89_%E4%BE%AF)\
**Post date:** [September 18, 2026, 1:09am UTC](https://forum.qoder.com/t/the-new-version-of-qoder-has-quite-a-few-issues/12571/1 "2026-09-18T01:09:28Z")

</div>

The new version of Qoder has quite a few issues. Setting aside the bugs on the UI for now, the custom API side is especially problematic. I can’t even properly connect my locally deployed models—whether using the OpenAI protocol or the Anthropic protocol, I run into all sorts of problems. On top of that, there’s no option to configure the maximum output length, and the overall experience is really poor.
