TL;DR
- Chat tools now work when Hi, Moose runs on the on-device Gemma 4 model, so local chat can do real jobs instead of just talking about them.
- App updates no longer collide with a visibility run in progress: the run saves its place and resumes after the restart.
- Anonymous usage analytics shipped as a plain toggle, and it never sends your content, your prompts, your keys, or the sites you point it at.
- You can now build and read your own diagnostic log from Settings.
- The in-app chat learned to point you at the right docs page, or to support, when you ask for help.
The local model picked up tools
For a while, tools were a hosted-model privilege. If the chat needed to check something or do a job for you, it worked on the managed models, and the model that runs locally on your machine mostly had to talk its way through.
As of this build, Gemma 4 running on your own hardware can call the same tools. FAQ generation and key-point extraction learned the trick too, and we raised the token ceiling for local jobs so longer pieces stop getting cut off mid-thought.
I will admit we underestimated this model once, early on, and quietly turned features off for it that it could handle fine. We have stopped doing that. It keeps up.
Updates and runs, no longer fighting
Here is a collision we did not enjoy discovering: the app decides to update itself right in the middle of a scheduled run. The update wins, the app restarts, and the run just stops existing. Nobody gets a report. Everyone lies down about it.
Now the run saves its progress before any restart, the updater checks whether work is in progress instead of barging in, and the scheduler picks the run back up on the other side. An update should feel like the app blinking, not like it losing its train of thought.
Analytics, the boring honest kind
We added usage analytics this week, and we tried to do it the way we would want it done to us. It is anonymous and aggregate: which features run, the app version, errors. It is never your content, your prompts, your keys, or the sites you analyze. Your IP gets discarded and the data stays on EU servers.
There is one toggle in Settings, written in plain words, and turning it off does what it says. That is the whole feature. It took longer to build than to describe, which is usually a good sign.
Small courtesies
A few more things landed that are individually small and collectively the point:
- A diagnostic log you can read yourself. Settings now has a Troubleshooting section where the app builds a log for you, so if something goes wrong you can see what it saw before deciding whether to send it to anyone.
- The chat knows where the docs are. Ask it for help with the app and it can point you at the right documentation page, or to support if the docs will not cut it. Less wandering.
- Start at login. The app can start itself quietly when your machine boots, so scheduled work is ready without you thinking about it. There is a toggle for that too.
- Tidier inbox messages. Workflow results in the inbox got a copy and layout pass, because the words your work arrives in matter as much as the work.
That is the day. The local model gets more capable, the app gets more polite, and I get a nap under the desk before tomorrow's build.
FAQ
Can the local model use chat tools now?
Yes. The chat's tools now work when Hi, Moose is running on the on-device Gemma 4 model, not just on hosted models. FAQ and key-point generation picked up the same ability, and the local model got more token headroom for longer jobs.
What happens if an app update arrives during a scheduled run?
The run saves its place before the app restarts, and it picks up where it left off afterwards. The updater also checks whether a run is in progress instead of restarting blindly.
What does the optional usage analytics send?
Anonymous, aggregate usage events: which features run, the app version, and errors. Never your content, never your prompts, never your keys, never the sites you point it at. Your IP is discarded and the data stays on EU servers. There is one plain toggle in Settings and you can turn it off any time.
Where do I find the diagnostic log?
Settings, under Troubleshooting. The app builds a log you can read yourself before deciding to share it with Hi, Moose Support.
The one who's under the desk for all of it.
