github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 08:02:14 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #11813] Missing features needed for Ollam app. #7840

New Issue
Closed
opened 2026-04-12 20:00:26 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 20:00:26 -05:00
Owner
Copy Link

Originally created by @X-DE1 on GitHub (Aug 8, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11813

In the Ollam app.
You can't create a system message in a conversation.
When editing a message, a new chat isn't created so you don't lose messages and replies.
You can't edit Assistant replies.
You can't tell the assistant not to think.

Originally created by @X-DE1 on GitHub (Aug 8, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11813 In the Ollam app. You can't create a system message in a conversation. When editing a message, a new chat isn't created so you don't lose messages and replies. You can't edit Assistant replies. You can't tell the assistant not to think.
GiteaMirror added the feature request label 2026-04-12 20:00:26 -05:00
GiteaMirror commented 2026-04-12 20:00:28 -05:00
Author
Owner
Copy Link

@Ahwar commented on GitHub (Aug 9, 2025):

Thank you for your feedback. To make these issues easier to discuss and address, please provide clear and detailed information for each one. Write each feature request in a new separate issue, I have summarized your request in numbered list so that it is easier to talk about them. Below is my response to your points:

  1. "You can't create a system message in a conversation."

    • You're absolutely right. This is a valid feature request. Please create a separate issue for this so the team can discuss it properly.

  2. "When editing a message, a new chat isn't created so you don't lose messages and replies."

    • This is also a valid point, as many chatbots implement this functionality. Please create a dedicated issue for this feature request as well.

  3. "You can't edit Assistant replies."

    • This feature is unnecessary. Editing assistant replies isn't a standard chatbot feature, and there's no practical use case for it.

  4. "You can't tell the assistant not to think."

    • This request doesn't make sense technically. Models are either:
      • Reasoning models (designed to "think")
      • Simple models (no reasoning capability)
    • If you don't want reasoning, you should simply switch to a non-reasoning model.

Summary:
Only the first two points (1 and 2) are valid feature requests. Please create separate issues for each of them. Points 3 and 4 are not needed as they either aren't practical or don't align with how models work.

<!-- gh-comment-id:3170418422 --> @Ahwar commented on GitHub (Aug 9, 2025): Thank you for your feedback. To make these issues easier to discuss and address, please provide clear and detailed information for each one. Write each feature request in a new separate issue, I have summarized your request in numbered list so that it is easier to talk about them. Below is my response to your points: 1. **"You can't create a system message in a conversation."** - You're absolutely right. This is a valid feature request. Please create a separate issue for this so the team can discuss it properly. 2. **"When editing a message, a new chat isn't created so you don't lose messages and replies."** - This is also a valid point, as many chatbots implement this functionality. Please create a dedicated issue for this feature request as well. 3. **"You can't edit Assistant replies."** - This feature is unnecessary. Editing assistant replies isn't a standard chatbot feature, and there's no practical use case for it. 4. **"You can't tell the assistant not to think."** - This request doesn't make sense technically. Models are either: - Reasoning models (designed to "think") - Simple models (no reasoning capability) - If you don't want reasoning, you should simply switch to a non-reasoning model. **Summary:** Only the first two points (1 and 2) are valid feature requests. Please create separate issues for each of them. Points 3 and 4 are not needed as they either aren't practical or don't align with how models work.
GiteaMirror commented 2026-04-12 20:00:28 -05:00
Author
Owner
Copy Link

@X-DE1 commented on GitHub (Aug 10, 2025):

I agree with your opinions, I will close this issue and open an issue for points 1 and 2.

<!-- gh-comment-id:3172913147 --> @X-DE1 commented on GitHub (Aug 10, 2025): I agree with your opinions, I will close this issue and open an issue for points 1 and 2.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#7840
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?