Hermes Agent adds /debug log sharing and automatic OpenClaw import

• Teknium's repost of the OpenClaw migration demo says Hermes now detects an existing OpenClaw install during setup and can pull over soul, user-profile, model-config, skills, and other transferable state, which lines up with the official hermes claw migrate guide.
• Teknium's log-sharing announcement adds a new hermes debug share command and /debug slash command that upload recent agent, debug, and gateway logs to pastebin-style links for support threads.
• Teknium's skill-loading benchmark post claims Hermes is now about 20 percent more likely to load the right skill, and the Skills Hub shows how much that matters when the catalog already spans coding agents, Apple automations, and creative tooling.
• Teknium's gateway-settings post says Hermes now supports per-gateway platform tool-call notifications and other platform-specific settings, pushing more configuration down to each chat surface.
• the Hermes WebUI refresh, the Hermes Workspace release, and a Telegram mini app demo show the same pattern around the core CLI: the agent is picking up faster setup, easier support, and a growing pile of community front ends.

The migration guide already exposes a full OpenClaw import path, the CLI reference now documents migration and debugging entry points, and the Skills Hub has quietly become a catalog big enough that a 20 percent routing bump is real product surface area. You can also browse the community's Hermes WebUI repo, which claims near 1:1 CLI parity in a browser.

Hermes is leaning hard into switcher flow. According to the migration tweet, install now checks whether OpenClaw is already present and offers a seamless import path for profile state, model config, skills, and other agent data.

The official migration guide fills in the mechanics. hermes claw migrate always shows a preview before making changes, reads ~/.openclaw/ by default, auto-detects older ~/.clawdbot/ and ~/.moltbot/ directories, and also recognizes legacy config filenames.

That makes the migration story more concrete than the tweet alone:

• hermes claw migrate previews imports, then asks for confirmation.
• --dry-run shows the preview without changing anything.
• --preset runs a fuller migration, including API keys.
• Legacy Clawdbot and Moldbot directories are detected automatically.

The new support flow is much simpler than "paste your logs into Discord by hand." Teknium's announcement says hermes debug share and /debug upload the latest agent, debug, and gateway logs and return shareable links.

Hermes already had adjacent support commands in the CLI reference, including hermes dump for a copy-pasteable setup summary and hermes logs for viewing and filtering logs locally. The new share path adds the missing export step for users who were getting stuck before they ever reached a support thread.

Teknium's benchmark post frames this as a quality-of-life update, but the interesting bit is the mechanism: Hermes reportedly used its own prompt improvement and benchmarking loop to get more aggressive about loading the right skill.

The Skills Hub explains why that matters. The catalog already includes:

• Apple integrations like Notes, Reminders, Find My, and iMessage.
• Coding-agent delegation skills for Claude Code, Codex, OpenCode, and Hermes itself.
• Creative and visualization skills like ASCII video, Excalidraw, p5.js, and Manim video.
• A long tail of optional and community-published skills exposed through the same hub.

That also makes the RLM delegation demo more legible. The tweet shows Hermes handing off a 136-page PDF document analyzer workflow through a converted skill, which is exactly the kind of task where better skill selection changes behavior, not just UX copy.

Teknium's gateway update adds per-platform tool-call notifications and other settings at the gateway layer. The follow-up note in the thread says the work came out of an experiment run with DSPy and GEPA, and was not yet fleshed out as a comprehensive system.

That leaves two concrete facts on the table. Hermes is getting more platform-specific configuration, and at least some of that tuning is being generated by the agent's own optimization loop rather than hand-authored product design.

The outer layer around Hermes is moving almost as fast as the core repo. the WebUI refresh post points to a browser client whose GitHub repo claims near 1:1 parity with the CLI, a three-panel layout, and a no-build Python plus vanilla JS stack.

The rest of the ecosystem update reads like a quick inventory:

• Hermes Workspace added a task board or Kanban page and other agent-management UI.
• the Telegram mini app demo shows multi-chat mobile access as a separate front end.
• a community Helm chart repost pushes Hermes toward stricter state safety, external secrets, and Istio-friendly Kubernetes deployment.

That is a lot of surface area for a two-day patch cluster, but it is all pointed at the same boring bottlenecks: setup friction, support friction, and getting the agent onto more screens.