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

[GH-ISSUE #12081] Re-open of #3002 #70084

New Issue
Closed
opened 2026-05-04 20:17:53 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-04 20:17:53 -05:00
Owner
Copy Link

Originally created by @jazzathedev on GitHub (Aug 26, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12081

Like the people in https://github.com/ollama/ollama/issues/3002, I too was surprised to see that ollama logs all of my prompts. I use ollama for the explicit purpose of not sending data to companies who will log and sell it, despite what they may claim. The surgence of running AI locally is, of course, for privacy. I'm not satisified with the single-session /set nohistory, and as a windows (sadly) user, using chattr to make the files immutable is not feasible.

I, like many others I'm sure, would like a permeanent user config that disables chat logs. If we don't want them, who do they benefit? I don't believe the closing of the old issue as "completed" was the correct outcome. No reason against was given, and only a community made, arguably hacky solution to something rather easy to implement was given.

Originally created by @jazzathedev on GitHub (Aug 26, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12081 Like the people in https://github.com/ollama/ollama/issues/3002, I too was surprised to see that ollama logs all of my prompts. I use ollama for the explicit purpose of not sending data to companies who will log and sell it, despite what they may claim. The surgence of running AI locally is, of course, for privacy. I'm not satisified with the single-session `/set nohistory`, and as a windows (sadly) user, using `chattr` to make the files immutable is not feasible. I, like many others I'm sure, would like a permeanent user config that disables chat logs. If we don't want them, who do they benefit? I don't believe the closing of the old issue as "completed" was the correct outcome. No reason against was given, and only a community made, arguably hacky solution to something rather easy to implement was given.
GiteaMirror added the feature request label 2026-05-04 20:17:53 -05:00
GiteaMirror commented 2026-05-04 20:17:57 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Aug 26, 2025):

Set OLLAMA_NOHISTORY=1.

<!-- gh-comment-id:3223601230 --> @rick-github commented on GitHub (Aug 26, 2025): Set [`OLLAMA_NOHISTORY=1`](https://github.com/ollama/ollama/blob/30fb7e19f806c1b0f0fce19d088dbb126b36acaa/envconfig/config.go#L267).
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#70084
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?