Profiles

Switch Projects, Not Values.

Keep each project or environment as a named setup. Turn Profiles on and off without rewriting header rows every time your context changes.

Add to Chrome See all features
VibeHeader Profiles for local development, staging QA, website QA, checkout experiments, and production
One setup per context

Keep Local, Staging, and QA Separate.

Each Profile keeps its own name, request headers, enabled state, and Request Filters. The popup always shows which setup you are editing.

Local development

Keep localhost tokens and debug flags away from deployed environments.

Staging and QA

Save the environment headers your team uses repeatedly and scope them to the right hosts.

Short-lived experiments

Turn a checkout or feature-flag setup on for a test, then disable it without deleting the work.

When Profiles overlap

The Result Stays Predictable.

All active Profiles can run together. For each request, VibeHeader first checks the Profile filters, then combines the matching header rules.

  1. Filter first: only Profiles whose enabled filters match the request take part.
  2. Combine distinct headers: different header names can come from different active Profiles.
  3. Resolve duplicates: if two matching Profiles set the same header, the later Profile in the list wins.
  4. Show the conflict: VibeHeader surfaces an override warning rather than hiding the result.
Local by default

Your Project Setups Stay in Your Browser.

Profiles are saved with chrome.storage.local. There is no VibeHeader account, cloud workspace, or extension analytics. When a teammate needs one setup, share that Profile by link and let them review it before import.

See how sharing works Read the privacy policy
FAQ

Profile Rules.

Can multiple Profiles be active at once?

Yes. VibeHeader combines every active Profile whose Request Filters match the request.

Which Profile wins when two Profiles set the same header?

The later Profile in the Profile list takes priority for that header. VibeHeader shows an override warning so the result is visible before you browse.

Do Profiles sync through an account?

No. Profiles are stored locally in chrome.storage.local. VibeHeader does not require an account or provide cloud sync.

Does pausing VibeHeader disable every Profile?

Yes. Pause is the global off switch. Individual Profile toggles let you keep VibeHeader running while enabling only the setups needed for the current task.

Can I share more than one Profile in one link?

A VibeHeader share link contains one Profile at a time, including its enabled valid headers and valid Request Filters.