Browser launch arguments

Open the profile editor: the "For experienced users" block sits under port scan protection. Write one argument per line, as --name or --name=value.

Right under the field the app says which argument it will not accept and why, and which ones sites can notice. The arguments apply only in ARMANOS Browser: the built-in engine does not take them per profile.

Arguments ARMANOS sets itself: language, User agent, proxy, extensions, window size and position, profile folder. A second one of these would override ours, and the profile would stop being itself.

Anything that opens browser control to other programs: the debugging port and allowed origins. Rewriting how addresses resolve, skipping certificate checks and incognito mode are not allowed either.

Anything that writes files: the network log, the browser log, the cache folder and any argument whose value looks like a path on the disk. The network log carries cookies and headers, and in someone else's folder anyone could read them.

--enable-features and --disable-features are merged with ours into one argument. A separate second --disable-features would replace our list, and a site would see one language instead of the profile's full list.

You cannot turn on a feature ARMANOS turns off, or turn off one it turns on: the app names that feature.

The arguments are stored with the profile and travel with it through the account to your other computers and colleagues, into a copy, a template and a transfer file. Before every launch on this computer the app checks them again.

An argument that fails the check does not reach the engine, and the profile still opens. A notification and the profile history name that argument and the reason, and the history also records how many own arguments the launch had.

The browser/start request takes args as a list of strings for one launch. They pass the same check after the profile password, and a forbidden argument gives the refusal launch_args_refused with its name.