mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-14 14:12:44 +00:00
e1067dbbe5
Main's rewritten test_tui_npm_install.py tests call _make_tui_argv expecting the Ink/npm flow unconditionally; with the dual-engine dispatch merged in, _resolve_tui_engine() auto-selects opentui whenever ui-opentui/dist is built in the repo, routing the call away from the path under test (first subprocess became 'node --version' instead of 'npm run build'). Pin the engine to ink via an autouse fixture, mirroring the existing pinning precedent in test_tui_resume_flow.py.
36 lines
1.5 KiB
Text
36 lines
1.5 KiB
Text
---
|
|
sidebar_position: 7
|
|
title: "Automation Blueprints Catalog"
|
|
description: "Ready-to-run automation blueprints — set one up from the dashboard, CLI, TUI, any messenger, or the desktop app."
|
|
---
|
|
|
|
import AutomationBlueprintsCatalog from '@site/src/components/AutomationBlueprintsCatalog';
|
|
|
|
# Automation Blueprints
|
|
|
|
Automation Blueprints are ready-to-run automations. Pick one, fill in a couple
|
|
of fields, and Hermes schedules it as a cron job — no cron syntax required.
|
|
|
|
Every blueprint works from **every surface**:
|
|
|
|
- **Dashboard / desktop app** — open the Cron page, switch to the **Blueprints**
|
|
tab, fill the form, and click *Schedule it*.
|
|
- **CLI, TUI, and messengers** — type `/blueprint <name>` (e.g.
|
|
`/blueprint morning-brief`) and Hermes asks you for what it needs, one
|
|
question at a time, then schedules it. The name match is forgiving — a
|
|
prefix or near-spelling resolves. Power users can skip the questions by
|
|
passing values inline: `/blueprint morning-brief time=08:00`.
|
|
- **Desktop app** — click **Send to App** on any blueprint and it opens with the
|
|
command pre-loaded in your composer.
|
|
|
|
Blueprints never schedule anything silently — you always confirm before the job
|
|
is created. Manage created jobs anytime with `/cron`.
|
|
|
|
<AutomationBlueprintsCatalog />
|
|
|
|
## Writing your own
|
|
|
|
A blueprint is just a skill with a `metadata.hermes.blueprint` block in its
|
|
`SKILL.md` frontmatter. See
|
|
[Creating Skills → Automation Blueprints](../developer-guide/creating-skills.md) for the
|
|
slot schema and how to publish one.
|