elsewire

The self-hosted human-in-the-loop broker

Your agent asks.

For a login, a secret, an approval. Things it should never hold.

Scroll

Elsewire does the asking instead.

A small daemon beside the agent. It drives the login CLI, holds the request, and tells you.

You answer on your phone.

ElsewireSomething is waiting for you.
now

Approve or Deny with your passkey. The agent gets the answer and who gave it.

The secret stays sealed.

You type it in a web app the agent never sees. It goes where it belongs, and nowhere else.

Only the signal passes.

DONE: GitHub CLI login. Continue.

One line comes back: the verdict, who answered, and for a secret a fingerprint.

Logins

Elsewire runs the CLI's own login and shows you the code. You sign in as yourself; the token stays where it lands.

Secrets

You paste a key on your phone. It is delivered once, signed, to the target the operator named. The agent gets a fingerprint.

Approvals

Before a delete, a deploy or a payment: Approve or Deny, with a note if you like. Words and glyphs, never colour alone.

The relay is not trusted with answers.

Pages and answers travel sealed under a key in the link's fragment, and every answer needs a passkey the daemon checks itself. A relay routes; it never holds a key, a device, or anything it could answer with.

The honest part: run Elsewire as its own user, away from the agent. If the agent can read its state directory, nothing here can help you.

Coming soon

Elsewire is self-hosted and Apache-2.0. The source opens soon.