Further Reading for Hermes
Tutorials, documentation and walkthroughs for designing with Hermes, as listed in the published guide.
How to design interfaces with Hermes in OpenDesign: a plan you approve before it executes, the provider key you own, one support-inbox task from brief to reviewed file, and the limits to know before you start.
“A support inbox an agent
can plan and I can approve.”
THREE WAYS INTO THIS HERMES GUIDE
This guide: brief, references, design rules and a reviewed HTML result.
Read this guide SETUPHere is the full path from a clean machine to a Hermes that can build and verify UI.
Go to setup COMPARISONHow Hermes differs from Codex, Claude Code, Cursor for design work, and when to choose another workflow.
See the comparisonOne Complete Hermes Design Task
A single task, shown end to end: the brief and constraints you hand over, the artifact that comes back, and the checks you still run before it is done. The interface below is an illustrative example built for this page, not a recorded Hermes run.
BriefDesign a support inbox for a small team: conversation list with priority, a thread view with suggested replies, and quick actions. Plan the layout first, then execute. Desktop and phone.
data-od-id hooksWrite the brief, select the design system and define the acceptance criteria.
Plans the layout, writes the HTML, CSS and JavaScript and revises it on request.
Provides the design system and skill, renders the preview and stores every version as a file in the project.
Visual hierarchy, spacing on the 8px grid, both breakpoints and every interaction are checked before handoff.
List and thread on the 8px grid; the list column keeps a fixed width so subjects do not reflow.
Sender and subject first, preview second; the accent marks urgent only.
List first, thread on tap; filters become a segmented switch.
Filter to urgent, open a thread, assign it, send the suggested reply.
Fit
Compatibility
This guide covers Hermes as connected through the OpenDesign desktop app. Published references checked on 6 September 2026.
Hermes is Nous Research’s open-source (MIT) autonomous terminal agent. It runs persistently on your own machine, reads your codebase, edits files, runs commands, and plans and delegates multi-step work to isolated subagents. This page is about designing interfaces with Hermes through OpenDesign, not about Hermes’s own interface. OpenDesign’s setup notes list the available agents.
Provider key via BYOK — xAI (Grok, default), OpenAI, or Anthropic. Authenticate with your own provider key (BYOK) — xAI Grok by default, or OpenAI or Anthropic — credentials stay on your machine. This page does not promise a quota or price.
Check the download page for desktop builds. The Node.js and pnpm requirements in the source quickstart apply to running from source, not to installing a desktop package. Minimum compatible Hermes version: not verified here.
Follow the connection instructions shown by your installed version, then run a small task. Confirm that Hermes handled it and that the artifact opens. A download alone does not establish a working connection.
Start with the desktop app
Download first, complete the Hermes setup for your installed version, then check a small result. You do not need to build OpenDesign from source to follow this path.
Choose the package for your computer, install it and open the app.
Download OpenDesignFollow the Hermes instructions in your installed version. Authenticate with your own provider key (BYOK) — xAI Grok by default, or OpenAI or Anthropic — credentials stay on your machine.
Connect xAI Grok to Hermes (OAuth)# 1. Install Hermes (one-line installer from Nous Research)
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
# 2. Run the setup wizard
hermes setup
# 3. Add a provider and authenticate (BYOK)
# default is xAI Grok; OpenAI / Anthropic also supported
hermes auth add # add a provider key or run its OAuth flow
hermes model # pick the provider and model (grok-4.3 by default)From the Hermes setup notes in the published guide; check the vendor documentation for the current command.
Use a small brief so you can judge the whole loop, including one revision.
Build a settings screen with a profile form and a save confirmation. Use my design rules. Check it at desktop and mobile widths.
To run OpenDesign from source, follow the technical quickstart instead.
The Hermes design workflow
The same support inbox task, followed from brief to verified file. Each step lists what you provide, what Hermes does, what OpenDesign contributes and what you check.
Plain language, three to six lines. Name the audience, the job of the screen and the platforms.
A design system and a few hard rules. This is what separates on-brand output from a generic look.
Hermes writes a self-contained HTML file: layout, styles, interactions and stable hooks.
The file renders inside OpenDesign at the widths you asked for. This is where the design is judged.
data-od-id targets for comments and edits.Request changes by pointing at elements in the preview. Every revision is a new file; nothing is overwritten silently.
Resources
Tutorials, documentation and walkthroughs for designing with Hermes, as listed in the published guide.
The artifact types Hermes can produce in OpenDesign, one skill per type.
Brand tokens and components to bind before Hermes generates anything.
Starting points for decks, landing pages and product screens.
Limitations
FAQ
Start with a small task, judge the round trip, then bring the real brief. Choose the option that matches your setup; the page does not detect it.