Infibrowser
INFIBROWSER FOR DEVELOPERS

Your tools.
Closer to the web.

Build small integrations that meet people where they browse. Start with a manifest. Add a useful command. Ask for only the permissions it needs.

Start building →Get the example ↓
YOUR FIRST INTEGRATION

From an idea
to a command.

A search shortcut is a useful place to start. Describe your integration, declare tabs.create, and open your service with the query the user supplies.

  1. Download the complete example manifest.
  2. Change the name, ID, and HTTPS destination.
  3. Validate it, then install it in the desktop app.
  4. Run your command from Integrations.
QUICK START
git clone git@github.com:Vrifni/infibrowser.git
cd infibrowser
npm ci
npm run plugin:validate -- \
  examples/search-github/infibrowser.json
npm start

REPOSITORY ACCESS REQUIRED DURING PRIVATE PREVIEW.

SMALL API. EXPLICIT BOUNDARIES.

Useful by design.
Permission by permission.

API v1 is a declarative integration format. Commands open fixed HTTPS destinations with encoded inputs. Plugins do not execute code inside the browser process.

tabs.create

Open a destination.

Create a tab when the user runs your command. Use {query} to pass text to your service.

activeTab

Work with the current page.

Use {url} and {title} after an explicit confirmation. Page-sharing commands are blocked in private tabs.

manifest_version: 1

A contract you can read.

Strict validation, a JSON Schema, a CLI validator, and a complete example. Disable or remove integrations at any time.

BUILD WITH A CLEAR PICTURE

What’s here.
What comes next.

Available: desktop command integrations, installation review, query templates, optional page context, enable/disable, and removal.

Future work: sandboxed executable extensions, content-script capabilities, extension signing and distribution, mobile integrations, and broader WebExtensions compatibility.

No public marketplace or compatibility guarantee is implied by the preview API.

Read the API contract ↗

Start with one useful thing.

The full contract, examples, and security model are in the docs.

Open documentation ↗