Now it is very necessary to agree on the uniformity of documentation with various large model manufacturers, otherwise it will lead to errors in the use of users.

[TaoWolf]

Validations

• I believe this is a way to improve. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that requests the same enhancement

Problem

例如，deepseek的官方文档建议在continue中的tabAutocompleteModel的配置文件中api地址应该写“https://api.deepseek.com/beta”，但是如果用户真的这么写的话，在使用过程中就会报错，根本无法使用，因为continue为了用户方便，其实这里已经自动加了beta，最终导致了请求的api地址中会有两层beta（https://api.deepseek.com/beta/beta/xxxxxxxx）。这就是两边文档和功能不同步，对用户造成的最严重的影响之一。注意：如果用户不看日志，是永远不会发现这里产生了错误的，只会觉得contiune为什么不好用了。

For example, the official documentation of “deepseek” suggests that the api address should be written "https://api.deepseek.com/beta" in the configuration file of tabAutocompleteModel in continue, but if the user really writes this, an error will be reported during use, and it cannot be used at all, because continue is for the user's convenience, in fact, beta has been automatically added here, As a result, there will be two layers of beta (https://api.deepseek.com/beta/beta/xxxxxxxx) in the requested API address. This is one of the most serious effects that documents and features on both sides are out of sync for users. Note: If the user does not look at the logs, they will never find that there is an error here, and will only think why Contiune is not working.

Solution