Primitive 1: /goal — Making the Goal a First-Class Runtime Object
The /goal command is the most architecturally significant change in v0.13.0. Before this release, the goal was a string in the system prompt or the first user turn. It existed in the context window, subject to the same attention dilution as everything else. By turn 12 of a long session, the model’s effective attention on the original goal string was competing with all the tool results, intermediate reasoning, and accumulated context from the session. Goal drift was the predictable result.
With /goal, the goal becomes a first-class primitive in the Hermes runtime. It is not stored in the context window. It is stored in a separate goal register that the runtime injects into every reasoning step as a structured prefix, independent of context window position. Every tool call, every sub-agent dispatch, every reasoning step is evaluated against the current goal before execution.
Setting a goal looks like this:
# Set the session goal
/goal Refactor the payment module for idempotency across all charge endpoints
# Inspect current goal at any point
/goal status
# Output:
# Goal: Refactor the payment module for idempotency across all charge endpoints
# Set at: turn 1
# Turns elapsed: 0
# Active sub-goals: none
# Last checked: --
The goal register is injected into the reasoning prefix like this (simplified from the v0.13.0 source):
[GOAL REGISTER]
Primary goal: Refactor the payment module for idempotency across all charge endpoints
Sub-goals: none
Turns elapsed since goal set: 14
Relevance check: REQUIRED before each tool dispatch
[REASONING STEP]
Current task: {agent_current_task}
Tool candidate: {tool_name}
Relevance to goal: {required_field}
The “relevance check: REQUIRED” line is not cosmetic. The Hermes runtime enforces it. If a tool dispatch does not include a relevance-to-goal field, the dispatch is blocked and the agent must re-reason about whether the tool call is actually advancing the primary goal. This forces explicit attention to the goal at every decision point, which is what eliminates drift.
Sub-Goal Inheritance
When the agent dispatches a sub-agent, the goal is inherited automatically. The sub-agent receives the parent’s primary goal as a read-only constraint in its own goal register. The sub-agent can set its own sub-goals, but those sub-goals must be consistent with the parent’s primary goal. Attempting to set a sub-goal that the runtime classifies as inconsistent with the parent goal raises a GoalConflict error and surfaces it to the orchestrator.
# Parent agent dispatches sub-agent for a specific subtask
dispatch_agent(
task="Audit the charge() function for idempotency gaps",
goal_inherit=True # default in v0.13.0
)
# Sub-agent receives:
# [GOAL REGISTER]
# Primary goal (inherited, read-only): Refactor the payment module for idempotency
# Sub-goal: Audit the charge() function for idempotency gaps
# Constraint: sub-goal must advance primary goal
In practice, this means a sub-agent that wanders off to fix a different part of the codebase will be flagged before it can return a result that does not advance the parent’s goal. The constraint is enforced at result-return time, not just at dispatch time.
What Long Sessions Look Like Now
Before v0.13.0, I treated any Hermes session longer than about 25 turns as unreliable. The probability of goal drift past that point was high enough that I would check in manually every 20-25 turns and re-anchor the goal. With /goal enabled, I ran a refactoring session on WOWHOW’s WooCommerce integration layer that went to 73 turns without a drift incident. The agent stayed on the original goal throughout, and the /goal status checks I ran at turns 30, 50, and 70 all showed the primary goal unchanged and every tool dispatch recorded as “advances goal.”
That is the practical difference: sessions of 60+ turns become viable without supervision.
Primitive 2: The Ralph Loop — Ending Premature Exit
The Ralph loop is named in the changelog as “Ralph” without further explanation. Based on the implementation (visible in src/core/loop/ralph.py in the v0.13.0 source), it appears to reference Ralph as in “retry, adapt, loop, persist, halt” — though this may be backronym rationalization on the community’s part. What it does is more important than what it is named.
The Ralph loop is a structured retry-and-variant protocol that activates when the agent encounters an obstacle. Before v0.13.0, the default agent loop in Hermes was: attempt task, encounter obstacle, raise obstacle to user. The Ralph loop changes the obstacle response to: attempt task, encounter obstacle, generate variant approach, attempt variant, repeat until variants exhausted, only then escalate.
The loop structure in pseudocode:
def ralph_loop(task, goal, max_variants=5):
attempt = execute(task)
if attempt.success:
return attempt.result
variants = generate_variants(task, attempt.error, goal)
for variant in variants[:max_variants]:
# Re-ground against goal before each variant attempt
if not advances_goal(variant, goal):
continue
result = execute(variant)
if result.success:
return result.result
# Log failure and continue to next variant
log_variant_failure(variant, result.error)
# All variants exhausted — escalate
raise ObstacleEscalation(
original_task=task,
variants_tried=variants,
last_error=result.error
)
Three things matter about this design.
First, variant generation happens against the goal. The agent does not generate arbitrary alternative approaches — it generates approaches that are evaluated for goal relevance before execution. This prevents the loop from “solving” the obstacle by switching to a task that sidesteps the original requirement.
Second, the loop re-grounds against the goal before each variant attempt. This is a separate check from the goal register injection. It is an explicit “does this variant actually advance the primary goal” evaluation that runs before any tool calls are made.
Third, escalation is genuinely a last resort. The agent only escalates to the user when all variants are exhausted. The default max_variants is 5, configurable per session. In my experience, most obstacle types are resolved within 2-3 variants. The escalation rate with Ralph loop enabled, compared to the previous default behavior, dropped from roughly 40% of obstacle encounters to roughly 8% in my usage over the week.
What the Loop Looks Like in Agent Output
With the Ralph loop active, obstacle encounters produce different output than before. Instead of a single “I encountered an error” message, you see a structured attempt log:
[RALPH LOOP] Obstacle encountered on task: Read payment/charge.py
Error: FileNotFoundError — path does not exist
[RALPH] Generating variants (goal: refactor payment module for idempotency)
Variant 1: Search for charge.py across project directories
Variant 2: Check git history for file moves
Variant 3: Inspect payment/ directory structure
[RALPH] Attempting variant 1: Search for charge.py across project directories
Result: Found at src/lib/payments/charge.py (moved in commit a3f9d12)
Status: SUCCESS
[RALPH] Resuming primary task with corrected path
That log entry represents what would previously have been an escalation requiring manual user intervention. The agent found the file had moved, updated its internal path, and continued without surfacing anything to the user.
The Token Cost
The Ralph loop is not free. Each variant generation and variant attempt consumes tokens. In my sessions, enabling the Ralph loop increased token consumption per session by 20-40% on obstacle-heavy tasks. For frontier models (Opus 4.7, GPT-5.5), this is a real cost consideration. For smaller models running locally (Hermes-3-70B via Ollama), the token cost is less significant because inference cost per token is much lower.
The trade-off is straightforward: you pay more tokens per session, but sessions complete without requiring human intervention on routine obstacles. For unsupervised runs where operator time has a cost, the token trade-off is usually favorable. For interactive sessions where you are watching the agent, you might prefer to disable the Ralph loop and handle obstacles manually to avoid the token overhead.
Configuration:
# hermes.config.toml
[loop]
ralph_enabled = true
ralph_max_variants = 5 # default
ralph_log_level = "verbose" # "verbose" | "summary" | "silent"
ralph_goal_check = true # enforce goal relevance on each variant
Where It Does Not Help
The Ralph loop handles obstacles that have viable alternative approaches. It does not help when the obstacle is fundamental — for example, if a required API is down, generating five variant approaches to call the same API does not resolve the obstacle. Hermes handles this by classifying obstacles as “transient” (worth retrying with variants) or “structural” (no variant approach can succeed; escalate immediately). The classification uses the error type and a small heuristic model trained on the Hermes dataset. It is not perfect — I have seen transient errors misclassified as structural and escalated prematurely — but it works correctly about 85-90% of the time in my usage.
Primitive 3: The Hallucination Gate — Trust But Verify in Multi-Agent Work
The hallucination gate is the most operationally significant primitive for anyone running multi-agent boards. It solves silent result corruption, which I described earlier as the scariest failure mode. The gate is disabled by default in v0.13.0 and must be explicitly enabled per board or per agent.
The core mechanism is a verification trace requirement. Every worker agent, when it completes a task, must produce not just a result but a verification trace: a structured log of the evidence it examined, the reasoning it applied, and the specific data points that support the conclusion. The parent agent does not mark the task done until it has checked the verification trace and confirmed that the stated result is supported by the evidence in the trace.
A verification trace looks like this (from actual Hermes v0.13.0 output):
[VERIFICATION TRACE]
Task: Confirm that charge() endpoint is idempotent for duplicate request IDs
Result claimed: charge() is NOT idempotent — duplicate request IDs process twice
Evidence examined:
1. src/lib/payments/charge.py:47 — no idempotency key check present
Quote: "def charge(amount, currency, customer_id):"
Classification: SUPPORTS result (no idempotency parameter)
2. src/lib/payments/charge.py:89-103 — database insert without duplicate check
Quote: "db.execute('INSERT INTO charges VALUES ...')"
Classification: SUPPORTS result (no UNIQUE constraint check)
3. tests/test_charge.py — searched for idempotency tests
Result: No tests found matching 'idempotent' or 'duplicate_request'
Classification: SUPPORTS result (no test coverage for idempotency)
Verification confidence: HIGH
Unsupported claims: none
The parent agent runs a gate check against this trace before accepting the result:
[HALLUCINATION GATE] Checking worker result: charge() not idempotent
Result: charge() is NOT idempotent — duplicate request IDs process twice
Trace evidence items: 3
Supported by evidence: 3/3
Confidence: HIGH
Gate decision: ACCEPT
[ORCHESTRATOR] Task marked complete. Proceeding with: Add idempotency key parameter to charge()
When a result is not supported by the evidence in the trace, the gate rejects it and triggers an automatic re-attempt:
[HALLUCINATION GATE] Checking worker result: no rate limiting on payment API
Result: Payment API has no rate limiting
Trace evidence items: 2
Supported by evidence: 1/2
Unsupported claim: "API has no rate limiting"
Evidence item 2 states: "Rate limit headers not present in test response"
Gap: absence of rate limit headers in one response does not confirm absence of rate limiting
Gate decision: REJECT
[ORCHESTRATOR] Worker result rejected. Reason: unsupported conclusion.
Dispatching re-attempt with constraint: examine API documentation and error responses,
not just response headers
That re-attempt is automatic. The orchestrator does not surface the rejection to the user. The worker retries with a more constrained task that forces it to look at better evidence. Only if the re-attempt also fails the gate does the orchestrator escalate.
Why This Enables Genuine Unsupervised Multi-Agent Work
The hallucination gate is what makes it reasonable to walk away from a multi-worker board and trust the output. Before v0.13.0, multi-agent boards on Hermes produced results I had to review manually before acting on them. Individual workers would state conclusions that looked plausible but were not well-supported by what they had actually examined. The orchestrator had no way to detect this — it just accepted worker results and passed them downstream.
With the gate enabled, the verification requirement forces workers to build their reasoning transparently. A worker cannot state “X is true” without also providing the evidence trail that supports the claim. The gate checks that trail mechanically and rejects conclusions that outrun the evidence.
In a week of running multi-agent boards on WOWHOW’s codebase, I had 3 gate rejections out of 47 completed worker tasks. Two of those rejections caught real errors: a worker that concluded a function was unused based on searching only one directory (it was used in another), and a worker that stated an API call would succeed based on documentation that was outdated. Both would have produced downstream errors if accepted. The gate caught them before the orchestrator built on them.
Configuration and the Self-Improvement Default
The gate is configured at the board level:
# hermes.config.toml
[hallucination_gate]
enabled = true
confidence_threshold = "HIGH" # "HIGH" | "MEDIUM" | "LOW"
auto_retry_on_reject = true
max_retries = 2
require_evidence_items = 2 # minimum evidence items in trace
opaque_rejection_mode = false # set true to hide rejection details from workers
One configuration option deserves special note: opaque_rejection_mode. When this is false (the default), the worker receives the full gate rejection details on retry — it knows exactly why its result was rejected and what evidence gap it needs to address. When it is true, the worker receives only “result rejected, retry” without the specific reason. The documentation notes that opaque mode can be used to prevent workers from “gaming” the gate by manufacturing evidence that technically satisfies the gate criteria without genuinely supporting the conclusion.
There is also a configuration option for self-improvement that is hidden in the default config template and not mentioned in the main documentation: gate_self_improvement = false. When enabled, the gate analyzes its own rejection decisions and updates its checking heuristics over the session to improve accuracy. This is disabled by default because in multi-session use it can produce drift in gate behavior that is hard to reason about. I have not tested it in production. I mention it because it exists and because the default config hides it, which is the kind of thing that can be surprising to discover mid-session.
How the Three Primitives Compose
The primitives are designed to work together, and their interaction is where the real reliability improvement comes from. In isolation, each one addresses a specific failure mode. Together, they form a coherent reliability layer for the agent loop.
The composition model is:
/goal sets the target. Everything the agent does is evaluated against this target. The target is injected at every reasoning step, not just stored in context.- The Ralph loop drives toward the target. When the agent hits an obstacle, it generates and tries variants rather than giving up. Each variant is checked against the goal before execution, so the loop cannot solve obstacles by abandoning the original task.
- The hallucination gate keeps the drive honest. Results from workers must be backed by evidence. The gate rejects conclusions that outrun what the agent actually examined, forcing the loop to be accurate rather than merely productive.
A minimal workflow that uses all three:
# Set the primary goal
/goal Audit payment module for idempotency issues and generate a remediation plan
# Configure the session
/config ralph_enabled=true ralph_max_variants=4
/config hallucination_gate=true gate_confidence=HIGH
# Launch a multi-agent board
/board create payment-audit
# Dispatch workers
/board dispatch worker-1 "Audit charge() for idempotency gaps"
/board dispatch worker-2 "Audit refund() for idempotency gaps"
/board dispatch worker-3 "Check test coverage for idempotency scenarios"
# Walk away
# The orchestrator will:
# 1. Run workers with goal inheritance
# 2. Apply Ralph loop to any obstacles each worker encounters
# 3. Gate-check all worker results before accepting them
# 4. Synthesize accepted results into remediation plan
# 5. Surface only genuine escalations that require human judgment
That workflow, on a moderately complex codebase, will run to completion without human intervention in the vast majority of cases. Before v0.13.0, the same workflow had a meaningful probability of stalling on worker obstacles, drifting from the original goal, or returning results built on unsupported claims from a worker that hallucinated its findings.
Where It Broke: Real Limitations in the First Week
I am not going to claim these primitives are production-ready without caveats. Here is where I ran into genuine problems in the first week.
Ralph Loop Token Cost on Frontier Models
The 20-40% token overhead I mentioned is significant when running on Opus 4.7 or GPT-5.5 at full price. A session that would have cost $3.20 with v0.12.x costs $4.20-$4.50 with the Ralph loop enabled. For obstacle-heavy tasks in large codebases, I have seen sessions run $6-7 instead of $4. This is not a deal-breaker, but it is a real cost increase that affects whether you route tasks to frontier models or smaller models.
My current approach: enable Ralph on sessions running local models (Hermes-3-70B via Ollama) without hesitation. For frontier-model sessions, enable Ralph only on tasks where premature exit would require significant manual re-setup time — tasks where the operator-time cost of a stall exceeds the token cost of the loop.
/goal Does Not Support Compound Goals
The goal register holds a single primary goal string. If your actual objective is compound — “audit for idempotency AND ensure no performance regression” — you cannot represent both conditions as coordinated first-class goals. The workaround is to set sub-goals and manually track their relationship, but this is clunky. I have seen compound goals cause issues where the agent fully satisfies one dimension of the goal and considers the task complete without addressing the second dimension.
This is a known limitation in the v0.13.0 milestone notes. Compound goal support is listed as a v0.14.0 target. For now, the workaround is to decompose compound goals into sequential sessions with single goals each.
Gate Rejections Can Be Opaque
Even with opaque_rejection_mode = false, gate rejection messages can be hard to interpret. The gate produces structured rejection output, but the “evidence gap” classification is sometimes correct in form but unhelpful in practice. I had one rejection where the gate flagged an evidence gap that was actually a naming inconsistency between the worker’s terminology and the gate’s expected schema. The worker had the right evidence but used different field names in the trace, and the gate rejected the result as unsupported. The worker then retried with more evidence (correctly), but it also changed its conclusion slightly to match the additional evidence, which introduced a small inaccuracy in the final output.
This is an edge case, but it illustrates that the gate is not infallible. It can reject valid results and accept invalid ones (though the false-negative rate — accepting invalid results — is much lower than accepting-without-gate was before v0.13.0).
Self-Improvement Is Hidden
I mentioned gate_self_improvement above. The fact that it exists but is hidden from the default config template is the kind of configuration footgun that bites you when someone runs hermes config --defaults --reset and the hidden setting is not in the defaults file. If you are deploying Hermes in a team environment, explicitly set every gate configuration option in your config file so the behavior is documented and not dependent on what the defaults happen to be.
What I Kept After a Week
After a week with v0.13.0, here is my actual running configuration on WOWHOW’s VPS:
# /root/storefront/hermes/hermes.config.toml
[loop]
ralph_enabled = true
ralph_max_variants = 4 # reduced from default 5; faster escalation on genuinely hard obstacles
ralph_log_level = "summary" # verbose is too noisy for regular sessions
ralph_goal_check = true
[hallucination_gate]
enabled = true
confidence_threshold = "HIGH"
auto_retry_on_reject = true
max_retries = 2
require_evidence_items = 2
opaque_rejection_mode = false
gate_self_improvement = false # explicitly disabled; documented for the team
[goal]
inject_frequency = "every_step" # default; inject goal at every reasoning step
sub_goal_conflict_check = true
goal_drift_alert_threshold = 10 # alert if no goal-relevant tool calls in 10 turns
The goal drift alert is useful. It does not stop the agent — it sends a notification to the Telegram bot that is already wired into my monitoring stack — but it gives me a signal to check in if the agent has gone 10 turns without doing anything that advances the primary goal. In practice, this fires about once per 5-6 long sessions, and when it fires, it is usually catching something worth looking at.
What I Left Out
I am not using the full Kanban board UI that was the centerpiece of the v0.13.0 marketing. I run Hermes headlessly via the CLI and the REST API. The Kanban is a useful visualization if you are managing multi-agent boards with human collaborators, but for solo unsupervised runs, the UI layer adds operational overhead (running a browser, managing the Hermes frontend container) without providing reliability benefits. The three primitives work identically in headless mode.
I am also not using the new “agent memory” features that shipped in v0.13.0. Hermes now has a persistent memory layer (based on a local vector store) that agents can write to and retrieve from across sessions. This is genuinely useful for certain use cases — agents that accumulate institutional knowledge about a codebase over many sessions — but I use Graphify for codebase knowledge graphs and have not found Hermes memory to offer enough incremental value over that to switch. This may change in v0.14.0 if the memory layer gets better integration with the goal register.
The Reliability Story Is These Three Primitives
v0.13.0 shipped 864 commits. Most of those commits are real improvements. The Kanban is genuinely better. Performance is up. Bug fix count is high. But if you are evaluating whether to upgrade from v0.12.x, or whether to invest in self-hosting Hermes for production use, the answer depends almost entirely on whether these three primitives address failure modes you are experiencing.
Goal drift, premature exit, and silent result corruption are the three most common ways that capable agent frameworks fail in production on long or complex tasks. The v0.13.0 primitives address each one with a mechanism that is well-designed and works as described in most cases. The limitations are real — compound goals, token cost on frontier models, opaque gate rejections — but they are manageable and do not undermine the core reliability improvement.
The Kanban is the UI story. /goal, the Ralph loop, and the hallucination gate are the reliability story. Those are the ones that matter.
Upgrade and Configuration Notes
If you are upgrading from v0.12.x, note that all three primitives require explicit opt-in. None of them are active by default. The upgrade does not change your existing behavior; you have to enable each primitive in your config file or via session commands.
# Upgrade
pip install hermes-agent==0.13.0
# Or via Docker
docker pull nousresearch/hermes-agent:0.13.0
# Minimal config to enable all three primitives
cat >> hermes.config.toml << EOF
[loop]
ralph_enabled = true
[hallucination_gate]
enabled = true
[goal]
inject_frequency = "every_step"
EOF
The v0.12.x config format is fully compatible with v0.13.0. No migration is required. New configuration blocks are additive.
One final note: if you are running Hermes connected to Claude via the Anthropic API, v0.13.0 is the first version that natively handles the Claude extended thinking budget parameter (thinking.budget_tokens). The Ralph loop variant generation, when running on Claude Opus 4.7, uses extended thinking for variant quality if you have budget tokens configured. This is optional and documented in the v0.13.0 API reference, but it is worth knowing about if you are already using extended thinking in your Anthropic API calls — Hermes will respect the budget parameter you pass rather than using its own default.
The three primitives are the reason I upgraded the day after the release dropped. They are the reason I will keep running Hermes as daily infrastructure rather than treating it as a demo-only tool. If you are on v0.12.x and experiencing goal drift, premature exits, or multi-agent result quality issues, v0.13.0 with these three primitives enabled is the direct answer to those problems.
Comments · 0
No comments yet. Be the first to share your thoughts.