scarf

What's New in 2.10

A coordinated catch-up to Hermes v0.15.0 ("The Velocity Release"). v2.10 surfaces the Scarf-relevant slice of the largest Hermes release yet — OpenAI as a first-class provider, the 104-PR Kanban maturation wave, Bitwarden Secrets Manager, MCP mTLS, skill bundles, per-session edit-approval modes, plus ntfy, xAI Web Search, and the xAI model-retirement migration. New v0.15 capability flags gate every surface; pre-v0.15 hosts render byte-identical to v2.9.x. (All flag/config/wire shapes were verified against the v2026.5.28 Hermes source before implementation.)

Providers & models

• OpenAI as a first-class provider — wire ID openai-api, distinct from the OpenAI Codex runtime, in the Models picker. (Bare openai stays a Hermes alias to OpenRouter, so it isn't registered separately.)
• Krea image generation — krea-2-medium / krea-2-large join the image-gen model list.
• xAI May-15 model retirement — retired Grok IDs (grok-4-0709, grok-4-fast-*, grok-3, grok-code-fast-1, …) resolve forward to grok-4.3 so a stored retired model still works, and the Health view warns + offers one-click hermes migrate xai.
• Vercel removed — Vercel AI Gateway (provider) and Vercel Sandbox (terminal backend) were deleted upstream in v0.15 and are dropped from Scarf's pickers.

Kanban — the v0.15 maturation wave

• Server-side sort (priority / created / status / assignee / title / updated) from the board header.
• Promote, Schedule / Park, and Delete-permanently (archive --rm) card actions; new Scheduled and Review columns (collapse when empty).
• Per-task worktree --branch on create + a read-only model-override line in the inspector; --board multi-board plumbing in the service layer.
• Precise chat-scoped board — the chat-header Kanban chip and the board it opens now filter by the originating ACP session_id (stamped automatically by Hermes), replacing the old tenant + time-window approximation, with a "This chat ⇄ All tasks" scope toggle.

Bitwarden Secrets Manager

• New Settings → Secrets tab for the secrets.bitwarden.* block — one bootstrap token (BWS_ACCESS_TOKEN in ~/.hermes/.env) replaces per-provider API keys. EU Cloud / self-hosted server URLs supported.

MCP mTLS + catalog

• mTLS client certificates (client_cert / client_key / ssl_verify) for HTTP + SSE MCP servers, in the server editor.
• A read-only hermes mcp catalog browse sheet for the Nous-approved MCP catalog.

Skill bundles

• A read-only Bundles tab listing the named skill groups in ~/.hermes/skill-bundles/*.yaml — each loadable in Hermes via one /<name> slash command — with each bundle's member skills and instruction.

Per-session edit-approval modes

• A chat-header chip toggles a live session between Default (ask before edits), Accept Edits (auto-allow workspace + /tmp), and Don't Ask via ACP session/set_mode. Distinct from the global approvals.mode / YOLO surface; sensitive paths always still prompt.

ntfy, xAI Web Search + more

• ntfy as the 23rd gateway platform (push notifications via a topic URL, no account), plus new per-platform toggles (Telegram disable_topic_auto_rename / ignore_root_dm, Discord allow_any_attachment, Signal group-only require_mention).
• xAI Web Search as a web_tools.search.backend option (reuses your Grok OAuth / XAI_API_KEY), and an opt-in xAI TTS auto_speech_tags toggle.
• Supply-chain audit — a "Run supply-chain audit" button on the Health view runs hermes audit (OSV.dev) and shows the result inline.

See the full v2.10.0 release notes for the complete list, including the pre-release review fixes and the v2.9 highlights (Hermes v0.14 catch-up: /subgoal + /yolo + /sessions + /codex-runtime slash commands, xAI Grok OAuth + NovitaAI providers, LINE + SimpleX Chat platforms, Brave Search + DuckDuckGo backends, the Hermes Proxy local server) which are all still in play.

Previous releases: see the Release Notes Index on the wiki for v2.7, v2.6, v2.5, v2.3, v2.2, v2.0, v1.6, and earlier.

ScarfGo — the iPhone companion

Same Hermes server you've been running on your Mac — reachable from your phone over SSH. Multi-server, project-scoped chat, session resume, memory editor, cron list, skills tree, settings (read), all native iOS. Pure-Swift SSH (Citadel under the hood — no ssh binary needed on iOS). Per-project chat writes the same Scarf-managed AGENTS.md block the Mac app does, so the agent boots with the same project context regardless of which client opened the session.

Join the public TestFlight — the link is live now but only accepts new beta testers once Apple's Beta Review approves the first build. If you hit a "not accepting testers" splash, bookmark it and try again in 24–48h.

See the ScarfGo wiki page for the full feature tour, ScarfGo Onboarding for the SSH-key setup walkthrough, and Platform Differences for what is and isn't shared between Mac and iOS.

Connect ScarfGo to your Hermes server

ScarfGo speaks SSH directly — no companion service, no developer-controlled server in between. Onboarding takes about a minute:

1. Install via TestFlight. Open the public TestFlight link on your phone, accept the invite, install ScarfGo from TestFlight (just like any other beta).
2. Tap Add Server. Enter the host (IP or DNS), SSH user, port (default 22), and an optional nickname. Same details you'd type into ssh user@host.
3. Generate Key. ScarfGo creates a fresh Ed25519 keypair on the device. The private half lives in the iOS Keychain (kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly) and is excluded from iCloud sync — it never leaves the phone.
4. Add the public key to your Hermes host. Tap Copy public key, then on the host run:

   cat >> ~/.ssh/authorized_keys <<'EOF'
   <paste the line ScarfGo showed you>
   EOF
   chmod 600 ~/.ssh/authorized_keys
   

   This is its own line per device — the convention any second SSH client uses. Mac (Scarf) keeps using your existing ssh-agent / ~/.ssh/config and is unaffected.
5. Tap Test connection. ScarfGo opens an SSH session, probes for the hermes binary, and saves the server on success. If it can't find hermes, see the troubleshooting section — it's almost always a PATH quirk on non-interactive SSH.

Done. Open the Dashboard tab and tap any session to resume it; tap the + in Chat to start a new project-scoped session.

Multi-server, one window per server

Scarf 2.0 is a multi-window app. Each window is bound to exactly one Hermes server — your local ~/.hermes/ is synthesized automatically, and you can add remotes via File → Open Server… → Add Server (host, user, port, optional identity file). Open a second window for a different server and the two run side-by-side with independent state.

Remote Hermes is reached over system SSH — the same ~/.ssh/config, ssh-agent, ProxyJump, and ControlMaster pooling your terminal uses. File I/O flows through scp/sftp; SQLite is served from atomic sqlite3 .backup snapshots cached under ~/Library/Caches/scarf/snapshots/<server-id>/; chat (ACP) tunnels as ssh -T host -- hermes acp with JSON-RPC over stdio end-to-end. Everything in the feature list below works against remote identically to local.

Remote setup requirements

The remote host must have:

1. SSH access — key-based auth via your local ssh-agent. Scarf never prompts for passphrases; run ssh-add once in Terminal before connecting.
2. sqlite3 on the remote $PATH — needed for the atomic DB snap