What problem does it solve? Integrating a generated-project run with the Hermes backend requires keeping API keys server-side, normalizing stream events for the browser, and handling cancellation and errors deterministically, which is easy to get wrong without a defined contract. ## Core Features & Use Cases - Server-Only Authentication: Keeps HERMES_API_KEY and raw environment values out of browser code and maps transport or auth failures to user-safe messages. - Stream Event Normalization: Converts Hermes output into normalized text deltas and observable activity events without exposing private reasoning. - Session and Cancellation Management: Strips reserved session placeholders, treats the conversation-level Hermes session as the next-run authority, and preserves cancellation state for active runs. - Use Case: When a user edits a generated Next.js project in AppLoop, the run sends the composed prompt and agentBundle metadata through the gateway, restricts writes to the project workspacePath, and streams safe progress events back to the UI. ## Quick Start Use the hermes-gateway skill to stream a project-edit run to Hermes with server-side authentication and normalized browser-safe events.
