Add reasoning and reasoningBudgetTokens parameters to config schemas and docs

[ferenci84]

Description

Adds reasoning and reasoningBudgetTokens params to config schemas and docs.

Issue: #4918

Checklist

• The relevant docs, if any, have been updated or created
• The relevant tests, if any, have been updated or created

[netlify]

✅ Deploy Preview for continuedev ready!

Name	Link
🔨 Latest commit	ff204ef
🔍 Latest deploy log	https://app.netlify.com/sites/continuedev/deploys/680506ab47a1920008864d8e
😎 Deploy Preview	https://deploy-preview-5041--continuedev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[RomneyDa]

@ferenci84 nice
@sestinj will require config yaml bump

Also before we merge would this potentially conflict with a UI that would allow users to adjust reasoning tokens ad hoc in the future? I know either @FallDownTheSystem or @ferenci84 did a PR with this at some point. Something to consider

[ferenci84]

@RomneyDa Not sure if you think of bumping the version number of the @continuedev/config-yaml, but if so, I think it should be set when the merging is done, because any change I do now, will soon become obsolete.

I didn't find any other modifications related to reasoning. Also verified that adding reasoning and reasoningBudgetTokens works with a yaml config like this:

  - name: Claude 3.7 Sonnet (thinking)
    provider: anthropic
    model: claude-3-7-sonnet-latest
    apiKey: YOUR-API-KEY
    roles:
      - chat
    chatOptions:
      baseSystemMessage: |
        You are intelligent, helpful and an expert developer, who always gives the correct answer and follow instructions.
    defaultCompletionOptions:
      contextLength: 200000
      maxTokens: 32000
      reasoning: true
      reasoningBudgetTokens: 1024

Before this modification, I was not able to get reasoning to work with the yaml config, although it was working with the json.

[chezsmithy]

I opened a similar PR but also included prompt caching.

We have migrated to yaml and then immediately noticed this regression.

#5202

[tomasz-stefaniak]

Thank you @ferenci84 !

[sestinj]

Hi @ferenci84, yesterday we shared some updates with our contributors about how we're aiming to improve the contribution process. Part of this included the addition of a Contributor License Agreement (CLA) to protect both contributors and the project.

I figure there's a good chance you'll open another PR since you've been contributing a lot of great code lately, but still wanted to send this message right away.

Could you please take a moment to sign, or if you have any questions send me a message? (either here or nate@continue.dev would work)

To do so, you just need to post a comment below with the following text:

I have read the CLA Document and I hereby sign the CLA

❤️ Thank you for the work you've done on Continue, and let me know if you have any suggestions on how we can make the project even better!

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}