Releases: japananh/aimonitor
v1.1.31
v1.1.30
v1.1.29
v1.1.28
v1.1.27
v1.1.26
Lower idle memory for the menu-bar app
The AIMonitor menu-bar app's memory grew the longer it ran — a fresh launch is ~27 MB, but a process left running for days climbed past 190 MB. This release stops that growth.
What changed
The widget polled its local database every 2 seconds for its entire lifetime — running all of its queries and refreshing the whole UI even while the popover was closed and nothing was on screen. That constant churn slowly accumulated memory.
Now each poll only does the work something is actually showing:
- The menu-bar title always stays live (active account + 5h usage).
- Per-account bars and sparklines refresh only while the popover is open.
- The heavy token-usage history is read only while the Token-usage window is open.
- When everything is closed, the poll slows from 2s to 5s.
In testing — accelerated to compress days of polling into minutes — the old build's footprint climbed steadily while the new one held flat.
Upgrade
brew upgrade aimonitorFixes #32
v1.1.25
clickup_get_task now maps the full subtask tree
Previously clickup_get_task returned only a task's own description, so an agent handed an epic URL couldn't discover or read its children — it had to ask a human to paste every child URL, impractical past one level of nesting. It now traverses the descendant tree in a single request.
What's new
clickup_get_taskpassesinclude_subtasks=trueby default and returns ClickUp's flattened descendant array assubtasks— direct subtasks and sub-subtasks, each slimmed to the same shape aslist_tasksand carryingparent/top_level_parent. One GET is enough to rebuild the whole nesting. Passinclude_subtasks=falseto keep the payload small when you don't need the tree.clickup_list_tasksandclickup_search_tasksgain an opt-ininclude_subtasksflag, since ClickUp's list/team endpoints omit subtasks by default.
Upgrade
brew upgrade aimonitor