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

[GH-ISSUE #14313] OLLAMA_NOHISTORY Support in GUI #9314

New Issue
Open
opened 2026-04-12 22:10:40 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 22:10:40 -05:00
Owner
Copy Link

Originally created by @Justinius on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/14313

The GUI saves chat to the database and attachments to a different table.

The OLLAMA_NOHISTORY variable doesn't seem to have an effect on this.

To balance the good functionality of the gui with the need for disabling logging in certain environments, could the GUI delete the contents of the database in the following conditons?

  1. When starting a new chat, delete the old chat
  2. When closing/re-opening the gui delete chat
  3. When shutting down/starting ollama.

That would ensure that nothing is on disk when not actively being used.

Originally created by @Justinius on GitHub (Feb 18, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/14313 The GUI saves chat to the database and attachments to a different table. The OLLAMA_NOHISTORY variable doesn't seem to have an effect on this. To balance the good functionality of the gui with the need for disabling logging in certain environments, could the GUI delete the contents of the database in the following conditons? 1) When starting a new chat, delete the old chat 2) When closing/re-opening the gui delete chat 3) When shutting down/starting ollama. That would ensure that nothing is on disk when not actively being used.
GiteaMirror added the appfeature request labels 2026-04-12 22:10:40 -05:00
GiteaMirror commented 2026-04-12 22:10:43 -05:00
Author
Owner
Copy Link

@Justinius commented on GitHub (Feb 19, 2026):

Discussed this with colleague. Keeping this under OLLAMA_NOHISTORY breaks the semantics of that variable, so maybe it should be a new setting still deployable with env vars.

So the existing could still be for cli, and the new one would be gui specific.

<!-- gh-comment-id:3928151690 --> @Justinius commented on GitHub (Feb 19, 2026): Discussed this with colleague. Keeping this under OLLAMA_NOHISTORY breaks the semantics of that variable, so maybe it should be a new setting still deployable with env vars. So the existing could still be for cli, and the new one would be gui specific.
GiteaMirror commented 2026-04-12 22:10:44 -05:00
Author
Owner
Copy Link

@samanebi commented on GitHub (Feb 19, 2026):

Hi . I opened a new PR for this issue . I would be happy if you take a look at it @Justinius

<!-- gh-comment-id:3929486711 --> @samanebi commented on GitHub (Feb 19, 2026): Hi . I opened a new PR for this issue . I would be happy if you take a look at it @Justinius
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 app 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#9314
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?