scarf

What's New in 2.16.1

A focused connection-reliability patch.

• Remotes heal themselves — a remote that "stopped working after a while" was a dead SSH ControlMaster holding its socket: every subsequent ssh hung on the corpse, and only removing and re-adding the server reset it. Scarf now probes the master on chat failures, before reconnect attempts, and on wake from sleep — resetting only provably dead connections, so a plain retry just works. (#123)
• Hermes-in-Docker configs are readable — when ~/.hermes lives inside a container, config reads now fall back through the Hermes CLI wrapper (config path, then a config show probe), so the chat preflight stops demanding a model that's already configured and Settings explains the bind-mount fix instead of "not found". Ships to ScarfGo with the next TestFlight build. (#112)

See the full v2.16.1 release notes.

What's New in 2.16.0

Scarf now targets the Hermes v0.18 line — audited against v0.18.0 (v2026.7.1) and re-audited against the v0.18.1/v0.18.2 patches — and the audits fixed long-standing bugs along the way.

• Search stays in lockstep with v0.18 in-place compaction — Hermes v0.18 can compact a session in place, soft-archiving the summarized messages while keeping them searchable. Scarf detects the new messages.compacted column and widens search to match Hermes exactly; /undo-rewound rows stay hidden, and the chat transcript still shows only the live conversation.
• The Web Tools tab actually works now — it had been writing web_tools.* config keys Hermes never reads (the real block is web.*), so every backend choice was a silent no-op. Both the write and read sides now use the real keys; if you'd set backends before, re-pick them once.
• Cron jobs round-trip losslessly — editing a job in ScarfGo used to rebuild it from an incomplete model, silently stripping repeat counts, per-job tool restrictions, provider routing, and (new in v0.18.2) the scheduler's run_claim double-execution guard. Scarf now preserves every key it doesn't model, so future Hermes job fields can never be stripped again — and the pre-run script + cron expression now use the keys Hermes actually reads (script, expr).
• No false mismatch banner on custom endpoints — custom/custom:* providers serve their own model namespace, so a slash in the model ID no longer triggers the "model/provider mismatch" banner (same class as 2.15.1's aggregator fix, #121).
• New providers: MoA (Mixture of Agents — Hermes's multi-advisor virtual provider, no credentials needed) joins the picker; Google Vertex AI replaces the retired Gemini CLI OAuth provider.
• Under the hood: full eight-surface audit against the tagged v0.18.0 source, repeated against the v0.18.2 rollup (~712 commits) — ACP wire, CLI verbs, config keys, state.db columns, and gateway platforms all verified stable; provider tables pass the mechanical sync gate against both tags; 18 new tests, 799/799 green.

See the full v2.16.0 release notes.

What's New in 2.15.1

A focused patch for anyone running Hermes on an aggregator provider (OpenRouter, OpenCode, KiloCode, Hugging Face, NovitaAI).

• No more false "Model/provider mismatch" banner on aggregator configs — OpenRouter model IDs like xiaomi/mimo-v2.5 are org/model namespaced, and Scarf's preflight misread the slash as a stale provider prefix; both of the banner's one-click "fixes" would have broken a working config.yaml. The check now skips aggregators (including Hermes's bare-openai → OpenRouter alias). (#121)
• The banner's fix buttons are validated — alias-equivalent prefixes (claude/… vs anthropic, x-ai/… vs xai) no longer read as mismatches, and a prefix that isn't any provider Hermes knows can no longer be written into config.yaml; the genuine stale-prefix protection is unchanged.
• Under the hood: Scarf's hand-mirrored Hermes provider tables are now gated by a mechanical sync check (scripts/check-hermes-tables.py), verified against the exact Hermes v0.16.0 tag.

See the full v2.15.1 release notes.

What's New in 2.15.0

Projects grow up — the biggest Projects update since v2.3. A project becomes a first-class object with its own mission-control pane, and gains three new powers. (Skips 2.14; this is a feature release, not a Hermes-compat one.)

• Mini-apps — sandboxed web panels (plain HTML/CSS/JS) that live inside a project and can drive your agent. They run in a locked-down WKWebView (no network, scoped assets, symlink-contained file reads) with default-deny permissions you review on first open. A mini-app's scarf.prompt(...) gets its own isolated, rate-limited hermes acp session — it can't reach your chats. Build one with the scarf-miniapp-author skill, or have Upgrade Project generate a starter. (v1 wires the read + prompt surfaces; kanban:write / file:write / net are declared but not yet enabled.)
• Fleet & Portfolio — run the same repo on more than one machine and Scarf groups them as one logical project, flags config drift across hosts, and lets you Apply to Fleet to push a host's model preset, board, and cron jobs to the others (per-host, non-fatal, version-gated).
• One-click Upgrade Project — bring an existing repo up to the full experience: a fast idempotent structural pass (stable id, board, AGENTS.md block, dashboard) then an agent hand-off that tailors a dashboard, slash commands, cron, and a starter mini-app.
• The cockpit — selecting a project opens one unified pane with everything about it: Dashboard, Sessions, Board, Site, Context, Cron, Memory, Secrets, Templates, Slash, Mini-apps, and Fleet.
• Project chats load your AGENTS.md — opening a chat in a project now spawns Hermes with the project as its cwd, so the agent gets the project's AGENTS.md / CLAUDE.md / .cursorrules automatically (new, resumed, and reconnected chats). Treat a project's context files like its code — only open chats in projects you trust.
• Hardening: remote SSH paths escaped against command injection; window size/position persists again.

See the full v2.15.0 release notes.

What's New in 2.13.0

ScarfGo — the iOS companion — gets Hermes profile switching, plus a remote-chat/Settings reliability fix that anyone running ScarfGo over SSH will feel. The shared-core pieces ride into the Mac app too.

• Switch Hermes profiles from ScarfGo — pick a profile and ScarfGo points its chat, memory, cron, sessions, gateway, and every hermes call at that profile for the selected server. It uses per-connection scoping and never runs hermes profile use, so it doesn't touch the host's active_profile — your Mac, terminal, cron, and running gateway keep their own profile. (Create / rename / delete / import / export stay Mac-only.) (#120)
• Reliable remote chat & Settings on iOS — fixes "Couldn't save model.provider … Transport refused" and empty Settings on a valid host. ScarfGo was opening a new SSH connection per read / CLI call; under a Settings-load or chat-init burst the handshake itself failed. It now pools one connection per server and coalesces concurrent opens (verified against a live sshd: a 24-way burst went from 20/24 connection failures to 0). (#112)
• Skills "What's New" tracks per profile — the pill no longer shows bogus "new / changed" counts after a profile switch; the baseline is now keyed per (server, profile).

See the full v2.13.0 release notes.

What's New in 2.12.0

A coordinated catch-up to Hermes v0.17.0 (2026.6.19) — the largest Hermes release yet, though Scarf needed only a focused slice — plus a remote-chat performance fix everyone on SSH will feel. Every new v0.17 surface is capability-gated, so pre-v0.17 hosts render byte-identical to v2.11.0; all flag/config/wire shapes were verified against the live v0.17 source.

• Remote chat is responsive again — typing into a session on a remote (SSH) host no longer lags or spikes CPU. Watcher-driven reads (credential preflight, sessions list, platforms, projects) that were doing synchronous SSH round-trips on the main thread per message now run off-main with cancel-prior + recency guards. (#119)
• Four broken Health/Settings actions fixed — surfaced by the v0.17 audit: "Run supply-chain audit" (hermes audit → security audit), xAI model migration (was dry-run only — now --apply), browser-tools setup (--assume-yes → --yes), and the no-op WhatsApp