Kernel tools first
Hydra can read files, search the web, inspect pages, search local code, manage memory, and attach artifacts before it ever needs a custom extension.
Hydra AI core
Hydra plans, chains, and completes tasks.
It runs a guarded Astraeus -> Thanatos -> Minos -> Hermes loop that validates actions, repairs bad calls, and mixes kernel tools with Verbas one step at a time.
Task completion
Smart chaining is the real feature.
Verbas where action lives
When the task needs smart-home control, media workflows, image generation, camera events, or app-specific logic, Hydra switches to the right Verba.
One step at a time
The chain stays deliberate: choose one action, validate it, run it, update state, then decide whether the next step should continue the task.
Execution loop
Each round commits to one next action.
1. Astraeus (The Seer)
Astraeus turns a user request into an ordered atomic plan and decides whether the turn is chat-only or execution.
2. Thanatos (The executor)
Thanatos executes the active atomic step and selects the exact next tool call needed for that step.
3. Validation and repair
Tool calls are forced into strict JSON, checked against the tool catalog, repaired if malformed, and blocked if the tool is unsupported or disabled.
4. Thanatos state update
After each tool run, state is updated with goal, plan, facts, open questions, next step, and tool history so current-turn execution stays grounded.
5. Minos (The Arbiter)
Minos returns one validation decision (CONTINUE, RETRY, ASK_USER, FAIL, or FINAL) and checks whether the turn still needs another atomic step.
6. Hermes (The voice)
Hermes renders the final user-facing response after execution and validation have converged.
Guardrails
Why Hydra stays controlled.
- Tool-first router: execution, retrieval, setting changes, add/remove requests, and system diagnostics route to tools.
- Beast Mode routing: base servers can handle AI Calls while Chat/Astraeus/Thanatos/Minos/Hermes can route to per-head models.
- Smart chaining: kernel tools and Verbas can be mixed across steps to finish a task instead of stopping after one tool result.
- Atomic execution lock: Thanatos and Minos both focus on one next step instead of merging unrelated actions.
- Fresh-run behavior: ASK_USER ends the current run and a new user message starts a fresh run.
- Recovery text path: validation failures can trigger a short recovery message instead of a broken tool call.
- Ledger and metrics: Redis-backed state keeps history, limits, and validation outcomes visible to operators.
- Memory context: user and room memory summaries can be injected into Minos decisions without bloating the turn.
Default runtime budgets