github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 17:49:24 -05:00
Code Issues 14.6k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #15660] Feature Request: add more details on usage reset / send notification when reset #35748

New Issue
Open
opened 2026-04-22 20:26:06 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-22 20:26:06 -05:00
Owner
Copy Link

Originally created by @robster7674 on GitHub (Apr 18, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15660

Currently the Cloud Usage page is fairly limited in details.

Image

It would be good to have a more detailed date/time on when the limit is actually reset. Also, a section named Notifications that includes not only warnings but also reset confirmations to be sent out when triggered would be good.

Originally created by @robster7674 on GitHub (Apr 18, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15660 Currently the Cloud Usage page is fairly limited in details. <img width="553" height="374" alt="Image" src="https://github.com/user-attachments/assets/26d58912-fcb5-41a6-9107-935b99448936" /> It would be good to have a more detailed date/time on when the limit is actually reset. Also, a section named Notifications that includes not only warnings but also reset confirmations to be sent out when triggered would be good.
GiteaMirror added the feature request label 2026-04-22 20:26:06 -05:00
GiteaMirror commented 2026-04-22 20:26:07 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

🤖 Automated Triage & Analysis Report

Issue: #15660
Analyzed: 2026-04-18T18:13:49.104923

Analysis

  • Type: unknown
  • Severity: medium
  • Components: unknown

Implementation Plan

  • Effort: medium
  • Steps:

This issue has been triaged and marked for implementation.

<!-- gh-comment-id:4274294979 --> @PureBlissAK commented on GitHub (Apr 18, 2026): <!-- ollama-issue-orchestrator:v1 issue:15660 --> ## 🤖 Automated Triage & Analysis Report **Issue**: #15660 **Analyzed**: 2026-04-18T18:13:49.104923 ### Analysis - **Type**: unknown - **Severity**: medium - **Components**: unknown ### Implementation Plan - **Effort**: medium - **Steps**: *This issue has been triaged and marked for implementation.*
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#35748
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?