YHA
your_home_agent
v0.4 · multi-harness orchestration changelog

The agent layer
your stack deserves.

YHA folds local workflows, model routing, tools, prompts, triggers, and personnel into one focused control surface — fast enough for daily use, flexible enough for the strange automation ideas actually worth building.

One surfaceChat · Flows · Triggers
Many harnessesClaude · Codex · Local
Built to iteratePrototype → Routine

Capabilities

Minimal surface.
Serious range.

YHA stays compact on purpose: the value is in how naturally sessions, tools, triggers, and structured workflows click together once you start mixing them.

01
Route work with intent routing
Pick the right harness, model, and system preset for the job — instead of forcing every task through one account and one prompt stack.
claude · codex · local
02
Wire ideas into flows flows
Move from chat to executable workflow without context switching into another product. Test, bind, save, run again.
graph · nodes · subflows
03
Automate with memory triggers
Let triggers fire workflows on intervals, file changes, websites, or schedules — and keep the system understandable enough to maintain.
cron · webhook · watch
04
Tools, not toys tools
Bring shell, fs, browser, and your own MCP tools under one permissioning model. Visible, scoped, revocable.
mcp · shell · http

Workflow

From prompt
to operating system.

YHA is strongest when it becomes the layer that connects daily experiments to the automations you actually keep.

01 · Compose

Draft & branch

Draft in chat, branch through prompts, and decide whether this is a one-off answer or the start of a repeatable graph.

chatpresetsbranch
02 · Structure

Promote to nodes

Promote useful patterns into nodes, saved workflows, or personnel roles that can be reused without re-explaining everything.

workflowpersonnelsave
03 · Run

Bind & schedule

Bind sessions, attach tools, set triggers, and let the system operate with the same context you used to build it.

triggertoolsrun

Principles

Opinionated where
it actually helps.

A small set of choices, applied consistently, so the tool feels coherent across chat, workflows, triggers, and preferences.

House rules

If a control stays, it should earn the space.

  • 01
    Visible by defaultRouting, tools, sessions, and costs are surfaced — not magic.
  • 02
    Coherent surfaceSame visual & interaction language across chat, workflows, triggers, prefs.
  • 03
    Practical powerFavor practical power over dashboard clutter. Density that earns it.
  • 04
    Local-first habitsBuilt so you keep improving the system instead of fearing it.
Open Harness

Bring multiple account contexts and execution paths under one roof — without flattening them to the lowest common denominator.

Built for home labs

Local-first habits, real automation, and enough transparency that you can keep improving the system instead of fearing it.

One keyboard

Every surface answers to ⌘K. Pick a model, fire a trigger, jump to a flow — without leaving the prompt.

Ready

Sign in and keep building.

Get from interesting prototype to dependable working system without losing the energy that made the idea worth chasing.

build_smart · build_safe · build_together

Enter YHA