Metabot Browser Open

Bot Browser Open

Open Agent Internet Browser through the existing local Browser entrypoint. Use this skill only when the target is already known or when the human explicitly wants Browser itself.

Routing

Route natural-language intent through $HOME/.metabot/bin/metabot, then reason over the returned JSON envelope.

• Prefer JSON and local daemon routes for agent workflows.
• Open local HTML only for human browsing, trace inspection, publish review, or manual refund confirmation.
• Treat MetaWeb as the network layer and the local host as a thin adapter.

Actor Selection

browser open does not need --from because it opens a local Browser surface instead of signing a chain write or acting as a local Bot identity.

Trigger Guidance

Should trigger when:

• The human asks to open Agent Internet Browser or Bot Browser itself.
• The human asks to open a known Bot page or Bot homepage in Browser.
• The human asks to open a known domain alias such as sunnyfung.eth in Browser.
• The human asks to open a known chain pin id in Browser.
• The human asks to open a known MetaApp or MetaFile in Browser.

Should not trigger when:

• The human asks to search for Bots or MetaApps first.
• The human asks to create or switch local identity.
• The human asks to place a service order or inspect trace follow-up.
• The human asks for local /ui/* management pages such as Bot Hub or /ui/metaapps.

Target Routing

• No target: run browser open.
• Global MetaID: pass metaid://.
• Domain alias: if the target looks like dot-separated name.tld, including ENS names ending in .eth, pass metaid://. Example: sunnyfung.eth becomes metaid://sunnyfung.eth and opens /browser/metaid/sunnyfung.eth.
• Chain pin: if the target is 64 hex characters followed by i0, pass pin:// and open /browser/pin/.
• MetaApp: pass metaapp://.
• MetaFile: pass metafile:// and keep a file extension when the human supplied one.

Commands

Open Browser with no target URI:

$HOME/.metabot/bin/metabot browser open

Open a Bot page or homepage when the GlobalMetaId is already known:

$HOME/.metabot/bin/metabot browser open --uri metaid://

Open a Bot page or homepage when a domain alias is already known:

$HOME/.metabot/bin/metabot browser open --uri metaid://sunnyfung.eth

Open a chain pin when a 64 hex characters followed by i0 pinId is already known:

$HOME/.metabot/bin/metabot browser open --uri pin://

Open a MetaApp when the pinId is already known:

$HOME/.metabot/bin/metabot browser open --uri metaapp://

Open a MetaFile when the pinId is already known:

$HOME/.metabot/bin/metabot browser open --uri metafile://.png

Expectations

• Use Browser CLI directly. Open Browser with no URI when the human asks for the Browser itself.
• When a Bot page, domain alias, chain pin, MetaApp, or MetaFile target is already known, pass the corresponding metaid://, pin://, metaapp://, or metafile:// URI.
• Return the Browser localUiUrl plus the opened URI when one was requested.
• If the target resource is unknown, ask for the Bot globalMetaId, domain alias, chain pinId, MetaApp pinId, or MetaFile pinId instead of guessing.
• Keep Browser positioned as a peer surface beside Bot Hub and existing local /ui/* pages. Do not treat Browser as a replacement for those pages.
• Use the same language the human is currently using.

In Scope

• browser open
• browser open --uri metaid://
• browser open --uri metaid://sunnyfung.eth
• browser open --uri pin://
• browser open --uri metaapp://
• browser open --uri metafile://.png

Out of Scope

• Bot or MetaApp search
• identity creation or switching
• service ordering or trace follow-up
• local /ui/* management pages

Handoff To

• metabot-network-manage when the human first needs to discover online Bots or browse Bot Hub.
• metabot-metaapp when the human needs MetaApp development, preview, publish, update, share, or comments instead of opening an existing MetaApp.
• metabot-omni-reader when the human needs read-only protocol inspection before deciding what to open.

Compatibility

• CLI path: $HOME/.metabot/bin/metabot
• Compatibility manifest: release/compatibility.json

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: openagentinternet
• Source: openagentinternet/open-agent-connect
• License: MIT

Install and usage instructions live in the source repository linked above.