Hermes Wingtips #105#: trust: untrusted want your Hermes Agent to ask before it changes anything through an MCP server? `trust: untrusted` add it under that server in config.yaml. tools the server marks read-only run as normal, and every other tool waits for your /approve.

Hermes Wingtips #104#: /restart want to restart your Hermes Agent while you're away from your computer? `/restart` send it in the chat with your bot. it finishes the task it is working on, then restarts and messages you when it is back.

Hermes Wingtips #79#: `agent[.]disabled_toolsets` Hermes Agent picks its tools per platform: the CLI, Telegram, Discord and the rest each keep their own list of toolsets, set in `hermes tools`. this key is one list above all of them. a toolset named here is removed everywhere at once, on the CLI and on every gateway platform. it is applied after the per-platform lists. `web` takes web_search and web_extract out of every session. `memory` removes the memory tools and also drops the memory guidance from the prompt.

Hermes Wingtips #59#: a rate limit doesn't have to stop your session Hermes Agent can carry a fallback chain: backup provider:model pairs it switches to automatically when your main model hits a rate limit, a server error or an auth failure. ~ hermes fallback opens the same picker as hermes model. add as many backups as you want, they are tried in order. history, tool calls and context all carry over, the agent continues from where it stopped. and it's per turn, your next message starts back on your primary. one last tips: pin a local model last and no provider outage can fully stop you!

Hermes Wingtips #58#: real profile browsing it shipped in Hermes Agent this week, and the same questions keep coming back. the two big ones: (1) "so the agent can see all my browser logins?" it never touches your real browser. it browses a separate copy that you can revoke and delete any time. you stay in control the whole time. (2) "does it work fully local, with a local model?" yes. with any backend and any model, fully local setups included. with this new tool, your agent can easily book flights, check orders, pull invoices and way more!

Hermes Wingtips #57#: `delegate_task` if you keep wiring up multi-agent teams by hand: several profiles, shared folders, a coordinator that ends up doing all the work itself. the built-in `delegate_task` tool is that whole pattern in one command. workers start with zero knowledge of your conversation. put everything they need in the brief itself (paths, constraints, what done looks like), and give the coordinator the briefs, not the workers' tools. that's also the perfect command for running workers on a cheaper model. great for parallel research, code review, comparing approaches, anything you would split across a team!

Hermes Wingtips #56#: switching models from anywhere `hermes model` opens an interactive picker, so it refuses to run through a pipe, a script, or another agent's terminal tool. the fix is that you never needed the picker. in any chat, on any platform: /model grok-4 --provider x-ai --global `--global` persists it to config.yaml and switches the running session in the same move. `--once` is the sibling: it switches for a single turn and restores the previous model afterward, even on an error.

Hermes Wingtips #49#: compaction thresholds when your Hermes Agent stops mid-task to summarize, the number in that warning is not random. compaction fires at a fixed fraction of your main model's context window. the fraction is `compression.threshold` in config.yaml, and it is always read off the model you chat with, never the summarizers' window. on smaller context windows Hermes waits longer by default, so a compaction cannot fire with half the window still free. and if you switch between a huge-context model and a small one, `compression.model_thresholds` sets a different trigger per model, matched on the model name.

Hermes Wingtips #48#: platform toolsets your agent pays a fixed token overhead before it reads a single word of your message, and one of the biggest slice is not the prompt. every tool your platform loads ships its full schema with every call, used or not. if a session never touches the browser, image gen or TTS, `platform_toolsets` in config.yaml hands that platform a smaller set. `hermes prompt-size` shows you the before and after without spending a token.