본문으로 건너뛰기

이 페이지는 아직 사용하시는 언어로 제공되지 않습니다. 영어 원문을 읽고 계십니다.

Browser launch arguments

Who can use this: All roles · All plans

The Launch arguments field passes your switches to ARMANOS Browser, for example --mute-audio.

Add an argument

  1. Open the profile window

    Edit in the profile menu.

    The profile window.
  2. Find the For advanced users block

    It sits under port scan protection.

    The For advanced users block.
  3. Enter the arguments

    One per line: --name or --name=value.

    The Launch arguments field.
  4. Save the profile

    Under the field the app immediately names an argument it will not accept and why.

    The button at the bottom of the profile window.

What is accepted

  • For advanced users

    Leave the field empty if you do not know why you need it.

  • Chromium feature lists

    --enable-features and --disable-features merge into one argument with the ARMANOS list.

  • Not accepted

    Language, User agent, proxy, extensions, window, profile folder, debugging port, incognito mode, logs and file paths.

Checked on every launch

Arguments are stored with the profile and travel with it: to your other computers, to colleagues, into a copy and into a template.

An argument that fails the check never reaches the engine, and the profile still opens.

The profile history shows which arguments were applied on each launch.

The local API

The browser/start request takes args as a list of strings for one launch. The check is the same.

Questions

Why is --user-agent not accepted?
The user agent derives from the profile fingerprint.
Where do I see which arguments applied?
In the profile history, on each launch.

Read next

Was this article helpful?

Last updated: Markdown