Profiles, Request Filters, and Better Sharing

Start with a header. Add precise URL scope when you need it. Keep each project separate when one setup is no longer enough.

Since the first release, we have received a lot of thoughtful feedback from the VibeHeader community. Different teams kept returning to the same three needs:

Keep projects separate instead of rebuilding one setup whenever the environment changes.
Scope headers precisely so they only run on the hosts, routes, and API URLs where they belong.
Share the complete setup so a teammate receives the same headers and request scope in one link.

So we built VibeHeader 1.1 around those requests: multiple Profiles, precise Request Filters with a URL tester, and filter-aware sharing. The quick path is still the same—add one header, turn it on, and keep working.

We also fixed a popup save reliability bug. Header edits and checkbox changes now persist immediately, so closing the popup right after a change no longer risks dropping the latest state. Background updates and first-wake messaging are more resilient too.

Multiple Profiles

Switch Projects, Not Settings

Save headers and filters by project, then switch without rebuilding the setup. Profiles can be enabled independently, so a local debugging setup and a staging API setup can run together.

VibeHeader showing Local Debug, Staging API, and Checkout QA Profiles — Each Profile keeps its own headers, filters, and enabled state.

Request Filters

Keep Headers Where They Belong

Open a Filter from the page you are testing and VibeHeader suggests three useful starting points:

Current host for one exact host.
Domain + subdomains for a whole site family.
Current URL prefix for one route or API area.

VibeHeader suggesting the current host, domain and subdomains, and current URL prefix — Suggestions are generated from the current page; matching happens against each supported request’s target URL.

Advanced matching

Use Regex—and Test Before You Rely on It

When a host or wildcard is not precise enough, add a regular expression. The built-in URL tester shows whether an example URL matches the enabled Filters before you return to your app.

A VibeHeader regular expression matching an API URL in the built-in URL tester — The tester reports the number of enabled rules that match the URL.

Better sharing

Share the Scope with the Setup

A VibeHeader link can now carry one Profile’s name, enabled valid request headers, and valid Request Filters. Your teammate can preview the setup before importing it.

A shared Staging setup with two request headers and an Import Now action — The shared payload is read from the URL fragment, which browsers do not send to the VibeHeader server. The complete link still contains the configuration, so use a trusted channel.

The same simple starting point

Start with One Header

You do not need a Profile strategy or a Filter to begin. Add a name and value, turn it on, and keep working. The new controls are there when your workflow grows into multiple projects, environments, or URL scopes.

Add to Chrome View source