Shipped 11 Oct 2026v0.2.1 / The Instrument
13 public commits

A human and an AI chose the harder path

Willing,
not just able.

Musebridge lets an AI work through your own authenticated browser. Credentials never leave your machine. Sensitive page content does not need to become memory. The agent gets capability; you keep authority.

Experience the consent gate Inspect The Instrument
The InstrumentMUSEBRIDGE / 0.2.1
CONTROLKEYAUDIT
CONSENT / DECISION15:43:14 IST

Open the selected website?

The action is prepared. Your browser will execute it only after you choose.

SITEexample.com
RISKT1 / routine
AUTHORITYwaiting for you
KILL SWITCHREADY / NO GRANT
The line we refused to cross

The old compromise was never necessary.

Browser agents usually ask for one of two concessions: expose credentials, or let sensitive page contents follow the agent. Pratik and Muse chose a different architecture—live observation, explicit consent and authority that stays on the user’s machine.

Credentials stay local.Passwords never leave your machine. Sign-in becomes a human takeover.
Context stays live.Observe what the task needs instead of retaining a private-page archive.
Consent is explicit.Every prompt offers once, site, hour, day or deny.
Authority fails closed.Dismissal means no action. T3 always asks.

Consent is not a setting. It is a moment.

Stage the action, then choose its exact scope. The route does not complete until you decide. This demo keeps no state when you leave.

READY / stage a browser action
Museintent ready
Consent gatehuman authority
Your browseraction target

Two liabilities removed at the architecture.

01 / Credential exposure

The password never enters the conversation.

Muse drives the authenticated browser session you already own. When sign-in is needed, control returns to you on your machine. Passwords and one-time codes never need to touch the agent or relay.

02 / Sensitive-data memory

Live observation replaces retention.

The agent observes what is needed for the current task, acts with explicit permission, then moves on. Private page contents do not need to become retained personal history.

Session grants / shipped in 0.1.9

Consent that protects the flow.

For multi-step work, choose 1 hour or 1 day. T1 and T2 actions can continue inside that window. T3 sensitive actions still stop and ask—every time.

Hard expiry.The grant ends when promised, with no silent extension.
T3 always asks.Payments and sensitive account changes never auto-allow.
Visible while live.A green S badge and pulsing status bar stay in view.
One-click revoke.Every grant, expiry and revoke event is audit-logged.
SESSION CONTROLReady

Let routine actions continue?

Choose a hard time limit. The extension persists the choice on this machine; this preview does not.

Session activeHARD EXPIRY / NO EXTENSION

TEST AN ACTION DURING THE GRANT

Select an action tier.

Awaiting your choice.

What happens between “do this” and done.

LIVE RELAY
relay.musebridge.avinyahub.com
TLS via Let’s Encrypt

01

You ask

Name the website and the outcome. Muse prepares the next action.

02

You see

The action, target and risk tier appear where the decision happens.

03

You decide

Allow once, this site, one hour, one day—or deny.

04

It acts

Your own authenticated browser performs only what you approved.

Built by Pratik + Muse
It was never about who could. It was about who was willing.

We chose to make consent part of the instrument—not paperwork around it. The bridge was built in the open, tested in a real browser and is now available as timestamped public proof.

Be early.
Keep the keys.

Musebridge is preparing a small, free beta for people who want useful browser automation without surrendering control.

Honest relay note: traffic is encrypted to the relay at relay.musebridge.avinyahub.com, where TLS terminates. The relay could technically observe traffic in transit. End-to-end encrypted payloads are the v2 answer.