Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Persistent Goals

Persistent Goals ( ) gives Hermes a standing objective that survives across turns. After every turn a lightweight judge model checks whether the goal is satisfi

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/goals

Persistent Goals ( ) gives Hermes a standing objective that survives across turns. After every turn a lightweight judge model checks whether the goal is satisfi

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. When to use it
  2. Quick start
  3. Commands
  4. Adding criteria mid-goal: /subgoal
  5. Behavior details
  6. The judge
  7. Fail-open semantics
  8. Turn budget
  9. User messages always preempt
  10. Mid-run safety (gateway)
  11. Persistence
  12. Prompt cache
  13. Configuration
  14. Choosing the judge model

Section map

When to use it

Maps when to use it to the Core Features documentation path, with the source page reserved for exact commands and updates.

Quick start

Maps quick start to the Core Features documentation path, with the source page reserved for exact commands and updates.

Commands

Maps commands to the Core Features documentation path, with the source page reserved for exact commands and updates.

Adding criteria mid-goal: /subgoal

Maps adding criteria mid-goal: /subgoal to the Core Features documentation path, with the source page reserved for exact commands and updates.

Behavior details

Maps behavior details to the Core Features documentation path, with the source page reserved for exact commands and updates.

The judge

Maps the judge to the Core Features documentation path, with the source page reserved for exact commands and updates.

Fail-open semantics

Maps fail-open semantics to the Core Features documentation path, with the source page reserved for exact commands and updates.

Turn budget

Maps turn budget to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: When to use it, Quick start, Commands, Adding criteria mid-goal: /subgoal, Behavior details. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: persistent, goals, gives, standing, objective. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for persistent goals before applying exact upstream commands.

Verify firstWhen to use it

Open the source anchor for When to use it and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for When to use it; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Quick start if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page