Give Hermes Agent a Workspace for lasting work.

Connect the assistant you already run

Hermes Agent is the Nous Research agent application, distinct from the Hermes model family. Connecting its MCP client lets that running assistant request permitted Workspace operations. It does not select a Hermes model inside Clanker, install the harness on Clanker compute, or create an always-running hosted agent.

Sources: Clanker: Projects, files and saved work · Nous Research: use MCP with Hermes Agent

Use native remote MCP and browser sign-in

Current Hermes documentation provides this native pattern: hermes mcp add --url https://workspace.clankercloud.ai/mcp --auth oauth clanker-workspace. Then run hermes mcp login clanker-workspace from a fresh terminal and complete the browser authorization.

Review the requested permissions. Begin with Read for discovery; approve Edit when you want saved reports. The client manages its OAuth tokens. Use a separate approved connection rather than copying another assistant’s credentials.

Sources: Clanker: connection, permissions and managed Sessions · Nous Research: native OAuth CLI example · Nous Research: MCP configuration and OAuth

Check identity before asking for a report

Use hermes mcp test clanker-workspace to inspect the connection, then ask Hermes to call workspace_status once. Check the actual permissions before reading private files. Discover current tools and select the intended Project. A saved server entry or a listed tool schema alone does not prove authenticated file access.

Sources: Nous Research: use MCP with Hermes Agent · Clanker: live agent instructions

Turn fictional meeting notes into a useful handoff

Create a Project containing dated meeting notes and an approved client brief. Ask Hermes to save weekly-report.md with decisions, blockers and named next actions. Require a source filename beside important claims and “not stated” for missing owners or dates. Save handoff.md identifying the checked inputs, current output and unresolved questions.

Make completion visible in Workspace

Before changes, follow the live instructions to start one managed Session and retain its Session/run identifiers. Record public progress, keep the task alive during waits and use stable action identities. Read back each saved file and its revision before completing the Session. Inspect existing results before retrying an uncertain save.

Open the files in Workspace to review the report. A later task should reread the saved handoff; your private Hermes conversation is not automatically synchronized.

Sources: Clanker: connection, permissions and managed Sessions · Clanker: live agent instructions

Separate connection guidance from runtime acceptance

This setup follows current upstream documentation; authenticated Hermes-to-Clanker acceptance has not been completed here. ChatGPT and Claude connection tests do not certify Hermes. Check client release behavior and finish this small canary first. BYOA is a separate runtime route with its own supported harnesses, provider authentication, limits and saved-state contract.

Sources: Nous Research: MCP configuration and OAuth · Clanker: connection, permissions and managed Sessions

Give your assistant its first Workspace task.

Before you use the result.

• The actual Hermes connection reads one approved source.
• The report preserves missing facts and identifies its sources.
• Saved files and revisions match their readback.
• The managed Session records the real terminal outcome.