This is an early release preview. You may encounter bugs.
HomeRail logo
Unclaimed

Tool voice coding monitoring

HomeRail

Voice-first local agent orchestration runtime for auditable DAG workflows.

B 78/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
Discussion

01 / Summary

About HomeRail.

HomeRail is a TypeScript runtime that turns one-off agent chats into auditable, reusable workflows, run on a homelab, NAS, or home server. Agent work flows node to node along the explicit edges of a DAG (directed acyclic graph) instead of accumulating in a single chat, so every handoff is traced and every run can be inspected, replayed, and evaluated. The design assumes a person's attention is the scarcest resource, so input is meant to be voice where possible and output a generated interface rather than logs or JSON.

The DAG runtime is the most mature part. A Manager service coordinates workflows, and a Node service provisions one Docker Worker container per DAG node, with the workers of one run sharing a workspace. Each node runs in its own context window and receives only the handoff it needs, and templates map a provider and model to each agent, so a stronger model can plan and review while cheaper models do the bulk of the work. Runs produce scorecards and evaluations, and a pattern library covers designs such as quorum, bounded ratchets, standing goal verification, and planner-worker fan-out.

There are three ways to drive it. A voice Manager Agent plans and runs a workflow from a spoken request, with Chinese as the default voice language and text always available. The hr CLI configures, runs, supervises, and replays workflows directly, and an existing coding agent such as Claude Code or Codex can operate that CLI to develop and tune DAG templates. A browser Agent UI renders the voice surface and generated widgets, which are still in exploration.

Workers use harness adapters for the Claude Agent SDK and compatible backends. For the voice Manager Agent, Codex is the recommended harness because it narrates progress from the model's reasoning stream, while an experimental DeepSeek Harness backend maps its reasoning into HomeRail thinking events. Provider credentials live in an encrypted settings store.

  • DAG runtime: multi-agent orchestration with explicit handoffs, per-run workspace isolation, replay, scorecards, and run evaluation
  • Docker workers: one Worker container per DAG node, provisioned by a Node service
  • Per-node models: templates map a provider and model to each agent, with a wildcard default
  • Voice surface: speech recognition, synthesis, and voice activity detection, with intent gathered across turns before acting
  • hr CLI: start, configure, run, smoke-test, supervise, score, evaluate, and replay workflows
  • Coding-agent operation: Claude Code, Codex, or any shell-capable agent can drive the CLI to build and tune DAGs
  • Pattern library: reusable control-flow designs such as quorum, bounded ratchets, and planner-worker fan-out
  • Multi-round DAGs: workflows pause at durable command boundaries and resume selected actors in the same run
  • Offline topology checks: a deterministic profile tests a workflow's shape without a model provider
  • Generative UI: structured, generated views instead of logs, still in exploration
  • Encrypted credentials: provider keys kept in the Manager's encrypted settings store, never in repo files

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

  • No discussions yet.

04 / Build

Build with HomeRail.

Browse the catalog for frameworks, tools, and harnesses, each scored on real GitHub credibility.

Get HomeRail →

Browse the catalog