Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

think tags #3901

Open
1 of 2 tasks
withinboredom opened this issue Jan 30, 2025 · 5 comments
Open
1 of 2 tasks

think tags #3901

withinboredom opened this issue Jan 30, 2025 · 5 comments
Assignees
Labels
area:chat Relates to chat interface kind:enhancement Indicates a new feature request, imrovement, or extension "needs-triage"

Comments

@withinboredom
Copy link

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

I noticed that using deepseek-r1 (local via ollama) for chat, the <think> tags are stripped and there is no way to differentiate between thoughts and actual output.

Solution

Maybe put <think> tags in a <summary> block?

@dosubot dosubot bot added area:chat Relates to chat interface kind:enhancement Indicates a new feature request, imrovement, or extension labels Jan 30, 2025
@rantvm
Copy link

rantvm commented Jan 31, 2025

It looks like the tags are not stripped; they get copied when copying the response. The webview probably treats <think> as a <div>, so no special styling happens. I'm of similar mind about replacing the tag with <details>/<summary>.

It also looks like this has been addressed in #3840.

@toxikman
Copy link

toxikman commented Feb 3, 2025

I've updated to v0.9.259-vscode which supposedly includes #3840 and I'm still not seeing the tags or the [Thinking] / [Reasoning] buttons. It's not easy to distinguish between reasoning and answer text. Running ollama in the terminal produces the tags. Tried with both AUTODETECT and direct models of deepseek-r1:14b under ollama provider. MacOS 14.7.1

@kota-iizuka
Copy link

kota-iizuka commented Feb 7, 2025

The implementation of #3840 seems to have an issue where the <think> tag is not displayed correctly when it is sent separately (e.g. <th in k>). Presumably the distilled model cannot process the <think> tag as one token, which causes these split submissions.

@wangjiyang
Copy link

Same issue here. Trying to remove think tag by reverse proxy. But hope it can be done via continue, which is more straight forward.

@RomneyDa
Copy link
Collaborator

@Patrick-Erichsen based on @kota-iizuka's point will probably need to switch to a remark plugin and remove the isReasoning etc. history logic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:chat Relates to chat interface kind:enhancement Indicates a new feature request, imrovement, or extension "needs-triage"
Projects
None yet
Development

No branches or pull requests

6 participants