Manual

This describes how to use the program: from the first launch to the synchroniser and the local API. Version 3.36.

If you have not installed it yet, start with installation; prices and licence terms are on a separate page. Did not find your answer — write to [email protected], and if something is missing from the program itself — to [email protected].

How the program is built

A profile is an ordinary folder on disk where Chrome keeps its data: cookies, passwords, bookmarks, history, extensions. The program does not replace the browser: it creates such folders, remembers additional details about each one (proxy, note, category, fingerprint) and launches the real Google Chrome, passing it the settings it needs.

Two important properties follow. First, the profiles stay yours: they sit in a folder you chose, and without the program they can be opened by the same Chrome. Second, the browser version is always current — Chrome updated, and so did your profiles.

Where things are kept

Quick start

1. Open the Settings tab and set the profile storage folder — profiles will be put there. The program finds the path to Chrome itself.
2. Go back to Profiles, enter a count and a name prefix, press Create profiles.
3. Tick the profiles, paste proxies into the Proxy for selected field and press Apply.
4. Press Launch — browsers open with your profiles.

Installation and where your data lives

The program is installed by an ordinary installer: language, folder, shortcuts. The language chosen during installation becomes the program's language — you can switch it in the top right corner at any moment.

The program itself goes into Program Files, while your data — settings, notes, categories, licence and logs — goes into your personal user folder. That is not a whim: a program cannot write into Program Files without administrator rights.

If you carry the program around as a folder (on a disk or a flash drive), it keeps working as before: when a config.json sits next to it, all the data stays there too.

Interface scale

On a fresh install the scale is chosen by screen height: up to 1150 pixels — 100%, up to 1400 — 125%, above that — 150%. Earlier everyone got 150%, and on a Full HD screen the program looked needlessly huge.

Your own value stays yours: if you set the scale by hand, an update does not touch it. You change it in Settings; the ceiling is 200%.

Licence

You get to know the program through a trial period: 100 profiles for 7 days. When it ends, access to the program closes until you buy — but your profiles, cookies and sessions stay intact on your disk. You lose the tool, not your data.

How to activate: Settings → Licence…. The window shows the ID of this computer — send it to the bot, get a key and paste it into the same window. The state appears at once: number, plan and term.

After a subscription ends there are a few days to renew — the program warns you in advance with a tray notification. Click it to open the bot. A lifetime licence has no reminders at all: you have already paid.

Starting with Windows

The Start with Windows checkbox in the settings adds the program to startup — it comes up minimised to the tray and does not open a window every time you log in. You can clear it there or in Task Manager on the "Startup" tab: it is the same entry, they cannot disagree.

Managing profiles

Table columns

Narrow columns are labelled with icons rather than words: the word "Launches" is by itself wider than any number in that column, and eight such labels ate half the table. Hovering shows what an icon means.

A column's width is changed by dragging the edge of its header, the order by dragging the header itself, and clicking a header sorts the list.

Which columns to show

The sliders icon to the left of the category filter opens a list of columns grouped by meaning: "Profile", "Network", "Modes", "State". A tick shows or hides a column.

Collapsing panels

Clicking a panel's title ("Proxy for selected", "Modes", "Extensions", "Creating profiles", "Launch") collapses it. The triangle to the left of the name shows the state: ▾ open, ▸ collapsed. A collapsed panel leaves no empty frame — everything below moves up and the table gets more screen. The "Launch" panel keeps its main buttons when collapsed: closing it completely is deliberately not possible.

Bulk action buttons

Selection icons in the table header

Selection control sits right above the checkbox column — three icons the size of the checkbox itself, instead of three buttons that took up half a row.

Tools behind the wrench

To the right of "Close" there is a wrench icon — it separates launching from tools that have nothing to do with launching.

Bookmarks and the URL field

The URL field sets the page that opens when the selected profiles launch. Leave it empty and the profile's start page opens, with its name and colour.

Delay (sec) is the pause between profiles in a mass launch, and it is not a detail. Fifty browsers starting at once hit a site in a volley from one connection: to the platform that looks like an attack. In practice it ended with the whole pool of addresses going into a soft ban by CDN and DNS, and Cloudflare protection refusing even normal visits. A couple of seconds of delay removes the volley completely.

The "↕" button — shift the selection

It clears the current ticks and selects the same number of following profiles. It exists for working in batches: you ticked ten with "Select next 10", launched them, did the work, pressed "↕" — and the next ten are selected. No need to hunt for where you left off.

Categories

A category is a group of profiles: "Shop", "Ads", "Testing". A profile can belong to only one. Category management lives inside the category list itself — there are no separate buttons under the table any more.

A profile can be moved to another category from the right-click menu — the "Move to category" item. For several profiles, tick them and choose "Move selected to category".

The right-click menu

Refresh titles and "Auto"

When many windows are open they look identical on the taskbar — you cannot tell which profile is which. The Refresh titles button writes the profile name into the title of its Chrome window, and the windows become distinguishable by their caption.

The Auto checkbox next to it does this automatically every five seconds: handy when profiles are started and closed as you work. With only a few windows you can leave it off — the titles update on the button.

Closing the program and session memory

If profiles are still open when you close the program, it asks what to do with them. Profiles can live on by themselves: proxies and control are picked up again the next time the program starts. So "Leave open" is a normal answer, not a risk.

The program names the exception itself. A profile in debug mode without the API enabled is controlled through a channel that lives inside the program and closes with it. For such profiles there is a separate button — close only those, leaving the rest alone.

Profiles closed that way are remembered along with their window positions. To open them again — right-click the list and choose "Open the last session's profiles": the profiles come up and the windows return to their former places. The same item is in the tray icon menu. After restoring, the record is erased, so the same thing is not offered twice.

The profile name does not scroll away

When there are many columns, the table does not fit the window and gets scrolled to the right. The checkbox, icon and profile name stay in place — otherwise, having reached the proxy column, you cannot tell whose row it is.

Freezing can be turned off in the columns menu (the icon to the left of the category list), the item "Freeze the name while scrolling". On a small screen that is sometimes more convenient: the frozen part takes up its space permanently.

Trash: deleting is no longer final

A deleted profile is not erased but moved to the trash. The Trash button above the list shows how much is in there and how much space it takes.

For each entry the trash shows the name, the deletion date, the size and its former place. Restore to list brings the profile back with all its cookies, passwords and settings. If a profile with the same name has appeared in the meantime, the returning one lands beside it as "name (2)" — nothing is overwritten.

Erase permanently deletes irreversibly and asks separately. Empty the trash does the same for everything in it.

Proxies

Accepted formats

The program accepts every common variant — the order of login and address does not matter:

Lines with a scheme (socks5://, socks4://, http://) keep their type regardless of what is chosen in the import window — convenient for mixed lists from a provider.

What the buttons do

Anti-detect

The AD column turns fingerprint substitution on for a profile. The program assembles a consistent set: a User-Agent matching your real Chrome version, languages, time zone and geolocation matching the proxy's country. The point is consistency: an American IP with a Moscow time zone is more suspicious than no substitution at all.

The fingerprint is set before the page's first line of code runs. That is not a small thing: a site that reads data the moment it loads would otherwise see the real machine — including the real time zone — and a moment later that same data would change to the substituted values. Such a change tells a checking service more than any single value on its own.

The substitution also works in the page's background processes, including SharedWorker. A site can read the cores, memory and video card from there, and if real values turn up there while the page itself shows substituted ones, the profile gives itself away through a contradiction inside a single tab.

What is substituted, what is not — and why

These are not left out for lack of effort, but by one rule: it makes sense to substitute what sets you apart; what makes you look like everyone else is better left alone.

Fonts on an ordinary Windows machine are identical across millions of computers — they do not set you apart. Giving each profile its own random set would do the opposite: every profile would become rare, and so noticeable. One caveat: that holds for an ordinary system. If a computer has exotic fonts installed — designer sets, rare handwriting fonts — the set becomes rare on its own, and profiles on such a machine really do look alike. It is better not to install such fonts on a working computer.

The screen is not substituted because a window can be resized with the mouse: substitution on a resizable window always creates a mismatch with the real scale. The TLS handshake is done by a real Chrome, and by definition it matches millions of live browsers — there is no better cover than that.

The fingerprint window

Right-click a profile → "Antidetect fingerprint…". The window is split into two blocks, because the fingerprint consists of two independent parts.

Device — the video card, cores, memory, screen, and the noise added to canvas, WebGL and audio. Changed with the "New fingerprint" button. To sites this looks like a switch to a different computer, so on a working profile this is done only deliberately: an account that knows you will see a new device.

Location — country, time zone, language and coordinates. Determined automatically from the proxy, or set by hand. The hardware does not change when the country changes.

The country is recalculated automatically whenever the proxy changes. Setting it by hand turns off that automatic update — the window says so directly, and a button appears next to it to bring automatic detection back.

With a manual choice the program first asks about the proxy itself and shows any mismatch: "the proxy exits in Germany, but you are setting the US." The decision is yours, but it is made with full information: sites check the browser's time zone and language against the IP's country, and a mismatch is a common cause of captchas.

The proxy traffic light: green, yellow, red

When checking a proxy, the program asks two independent databases for the country and puts an icon next to the latency:

Red does not mean "the proxy is broken." It means the directories disagree for this address, and on checking sites the country will not match the time zone no matter which country you set: match one database, and the second will show a mismatch. This is typical of resold datacenter addresses. Tolerable for bulk tasks; for valuable accounts, get a different proxy.

Why signing in to Google works on these profiles

Fingerprint substitution is normally done through the browser's debugging channel. The trouble is that Google sees the very existence of such a channel and refuses to let you in: "This browser or app may not be secure". We tested it directly: it is not about the commands or the quality of the substitution, but about a debugging flag being present in the command line.

So the substitution is delivered by a carrier extension inside the profile itself. There are no debugging flags in the command line at all, and an extension has the same capabilities from inside. Signing in to Google works on such a profile, and both fingerprint substitution and control from scripts keep working.

Checking the fingerprint

The Check fingerprint button in the extra tools answers the question "what does a site really see". The program asks the page itself and compares three columns: what was intended, what the main thread sees and what a Worker sees.

Rows marked "OK" mean a match. navigator.webdriver is shown separately. The profile will be launched if it is closed.

Debug mode (the "DBG" column)

Sometimes you need an ordinary debugging port: to attach Playwright or Puppeteer directly, as to any browser. That is what the DBG column is for. Turning "DBG" on automatically turns on "AD" and "API"; turning "DBG" off does not turn them off.

⚠️ On a profile with "DBG" or "API" on, the browser tells sites it is being automated: navigator.webdriver is true there, and any check can see it. Signing in to a Google account will not work on such a profile. This is a deliberate trade-off: browser control becomes available from outside, but the profile stops looking ordinary. For working with accounts, these boxes are unticked — then the profile runs on the carrier extension, and there is no tell.

Extensions

Installing an extension into a hundred profiles by hand through the web store is impossible: in each one you have to sign in, find the extension, install it, configure it. So the approach here is different — a template profile. You set the extensions up once in one profile, and the program copies their folders into the rest. The extension arrives already installed and configured, no Chrome account sign-in is needed, and the store never opens.

How it works inside

An extension in Chrome is a folder named after its identifier inside a profile. The program takes such a folder from the template and puts it into the chosen profiles, then edits the internal records so the browser sees the extension as installed. Nothing is downloaded from the network, so the rollout is fast and identical for every profile.

The steps

1. With the Template… button, choose the profile that becomes the model. It is an ordinary profile from your list — you can create an empty one specially.
2. Press Open template. Chrome opens with that profile: install the extensions you need from the store and configure them the way you want them in the other profiles.
3. Close the template and press the From template button above the list field — the program writes in the identifiers of every extension it found in the template.
4. Tick the profiles and press Install into selected.

The extension list and the "Parallel" field

In the list field the identifiers are written one per line. They can be edited by hand: remove the unneeded ones, keep only what you want, add someone else's identifier. An identifier is a long string of letters, visible in the extension's address in the Chrome store (…/detail/name/identifier) and on the chrome://extensions page with developer mode on.

Parallel sets how many profiles are processed at once. More is faster but harder on the disk; ten suits most cases. While the rollout runs, pause and stop buttons appear: the process can be interrupted and continued later, and profiles already done are not touched again.

How to tell what happened

The Ext. column in the table shows the progress right in the rows: … means working, ✓ succeeded, ✗ failed. After the rollout the same column shows the number of extensions installed in the profile, so a discrepancy is obvious: if one profile has 3 and the rest have 4, something is missing there.

The extension store in the settings

The "Settings" tab has an Extension store table — your own reference list of identifiers with descriptions. The idea is simple: identifiers are unreadable, and a month later you cannot tell which is which. Write down "Canvas Fingerprint Defender" once and take it from there afterwards. Clicking a row copies the identifier to the clipboard.

Tick the rows you need and press To the extension list — the identifiers travel to the list on the "Profiles" tab, with nothing to paste by hand. You can tick as many rows at a time as you like, and the tick in the column header selects the whole store; clicking it again clears the selection. The program skips those already in the list and tells you how many it added and how many it skipped — no duplicates will appear.

The program installs its own extensions itself

Besides yours, the program installs two of its own, and you need do nothing for that.

The frame with the profile name — a thin strip over the page, so you do not mix up windows when working with a dozen profiles. It is installed into every profile at creation; existing ones get it on their next launch.

The anti-detect carrier — the extension that substitutes the fingerprint from inside. It is installed into a profile when its AD column is on, and removed when it is turned off.

Cookies and moving to another PC

Chrome encrypts cookies and passwords with a key belonging to your Windows account. So simply copying the profile files to another computer does not carry the sessions over — there is nothing there to decrypt them with. The program takes the cookies from the running browser itself.

On the same machine and under the same user things are different: restoring from an archive brings back both the cookies and the passwords as they were. The limitation only concerns moving to someone else's computer, and even there not all sign-in data is lost: the list of sites with logins comes across, only the password field turns out empty. And you usually do not need to sign in again at all: the cookies carry the session itself.

A profile that has not been touched since the last export into the same folder is skipped: the browser is not launched for it, and the log shows "unchanged — previous file kept." Across a hundred profiles that saves not minutes but tens of minutes.

The format is ordinary JSON, the same as EditThisCookie, Puppeteer and anti-detect browsers use. On import four kinds are understood:

Field names are accepted in different spellings: expires, expirationDate or expiry; httpOnly or http_only. Extra fields such as id and storeId are ignored — particular extensions add them and Chrome does not expect them.

Exchange with regular Chrome

The Chrome settings button links the manager to the Chrome already installed on your computer. It's for when you need to move not between computers, but between the "regular browser" and the manager: pull over what's been built up there, or hand off a ready profile to it.

The program finds the installed Chrome itself and shows a list of its profiles — with names, not folders like Profile 7. Service profiles ("Guest", "System") don't make it into the list.

Chrome must be closed during the exchange: it keeps its files open, and the copy would come out incomplete. The program checks for this and offers to close it.

What moves over, and what doesn't

Bookmarks, history, autofill, site settings and extensions move over — together with their own settings.

⚠️ Website sessions and passwords cannot be pulled from regular Chrome. Since version 127, Chrome encrypts them so that outside its own folder they can't be read, and passwords are often kept not in the browser but in the Google account besides. This is the browser's own protection, and it can't be bypassed — not by us, not by anyone. The program says so in the dialog before starting, not after.

The other direction: a manager profile inside Chrome

Here everything is reversed, and it's worth understanding in advance.

A manager profile moves into regular Chrome together with its sign-ins: its cookies aren't locked by App-Bound encryption, so "Replace Chrome" and "Shortcut" give you a logged-in browser right away.

But there's no way back. Once a profile lands in regular Chrome's folder, everything Chrome writes there from then on is encrypted the new way — App-Bound. The old sign-ins keep working, but fresh sessions from such a profile can't be pulled back into the manager. It's not about the Google account or sync: Chrome behaves this way with any profile that lives in its own folder.

So the rule is simple: work in the manager profile, and hand a copy off to regular Chrome. That way portability stays with you.

Extensions move over now, and that was fixed separately

Chrome signs extension records in a way tied to the machine. A profile brought from another computer failed those signature checks: extensions appeared after the first launch and vanished on the second.

Now, on transfer, the outdated signatures are stripped, while the per-extension ones — the ones holding a specific extension's own settings — stay untouched. Extensions stay in place together with their data.

The "Passwords" button

Opens Chrome's password manager for the selected profile — the one place where the browser has its own file-based transfer: "Export passwords" on the old computer, "Import passwords" on the new one.

Chrome will ask you to confirm your Windows sign-in — that's expected, it's its own protection.

⚠️ The export file holds every password in plain text. Delete it right after importing and don't leave it in "Downloads". The program doesn't read this file or send it anywhere: it passes through your own hands — we deliberately don't do this step for you.

Chrome doesn't let you open its passwords page with an outside command. Where the program can't take you there directly, it puts the address chrome://password-manager/settings on the clipboard and asks you to paste it into the address bar.

Exporting and importing profiles

The Export button packs the selected profiles into a zip archive. It contains cookies, passwords, autofill, bookmarks, history and settings, plus the proxies, notes, categories, tags and fingerprints from the manager. Caches are not carried over — Chrome will create them again.

The whole household of the program travels with the profiles too: the proxy library, the synchroniser's sets, scripts, bookmarks, tag colours, the extension store and settings — the path to Chrome, the profile folder, the template profile, the language, the theme. Otherwise you would end up on the new computer with the profiles and an empty program around them.

On import the program asks separately whether to apply the settings. Declining is a normal answer: if someone simply sent you profiles, you do not want their paths and language on top of yours. Paths that do not exist on this computer are not applied in any case.

Nothing is overwritten at the new place. Only what is not already there gets added: proxies matched by "type and address," synchroniser sets by name, bookmarks by link, extensions by identifier, scripts — only new files. Your work on this computer stays untouched.

Appending: a second backup takes minutes

The expensive part of a portable export is not archiving but launching the browser: Chrome only gives up decrypted cookies while it is running, so each profile has to be launched and closed just to get them.

If your archive already sits in the chosen place, the program shows what date it is from and how many profiles it covers, and offers to append to it. Profiles unchanged since last time move over from it ready-made — complete with cookies, proxies and notes — and the browser is only launched for the new and changed ones. The final window shows how many were taken ready-made and how many were rebuilt.

Checking profiles against the archive takes a fraction of a second: the program looks at the profile files' modification time rather than reading their content. An error can only go the safe way — a profile gets rebuilt for nothing, but this check never lets a changed one slip through.

Pause, stop and cancel

Moving a hundred and fifty profiles takes tens of minutes, so the row showing progress has three buttons:

"Stop" combined with appending gives a resume point: stop at the fortieth profile, and the forty already collected stay in the archive — the next run into the same file picks them up ready-made and continues from the forty-first.

The archive is written to a temporary file alongside and replaces the previous one only at the very end. A dropped connection, a cancel or a crash never leaves a stump in place of the backup.

Import: from an archive or straight from folders

There is no separate "Back up selected" button any more: it copied profile folders alongside, taking exactly as much space as the profiles themselves. Restoring from folders has not gone anywhere — Import accepts it, asking first where to load from.

If such names already exist, the program offers to skip them or overwrite. A running profile cannot be overwritten — Chrome keeps its files open, and such a profile would arrive incomplete. The program says in advance which profiles are running and offers to close them.

If something fails, the profiles are named: "failed: bansay7, pdl3." Importing the same archive again with "skip existing" delivers what is missing, without touching the rest.

Put them next to the profile folders — the program finds them itself, picks them up and lists exactly what it restored. It keeps the previous files alongside marked .before_…, so there is something to roll back to if the wrong folder was chosen.

On the new computer press Import and choose the archive. If the archive is portable, after unpacking the program offers to load the cookies — agree, and every profile gets its own.

What moving does not do, and rightly so

⚠️ Proxy passwords sit in the archive in plain text — otherwise they would not work on another machine. Keep the archive as a secret: do not leave it in shared folders or the cloud.

Disk space

Chrome downloads service data into every profile: a local AI model, a speech synthesis engine, Safe Browsing databases, telemetry. Across a large set that is gigabytes with no connection to your accounts.

The Save space checkbox in the settings (on by default) forbids those downloads when profiles launch. The Clear cache button removes what has already accumulated in the selected profiles — cookies, passwords, bookmarks and extensions are untouched.

The window grid

The settings choose how many parts to divide the screen into: 2, 4, 6, 8, 10 or 20 windows. Running profiles are placed into the cells automatically. If there are more profiles than cells, the next ones lie on top of the first.

The grid's shape is chosen for your monitor: an ultrawide gets more columns, a vertical one more rows. The Grid button tidies windows that are already open.

Scripts

Scripts are ordinary files in the scripts folder next to the program. Edit them with anything, keep them in git, run them without the manager. .py, .js, .mjs, .ts, .ps1, .bat and .cmd are supported; the "Runs with" column shows whether the necessary interpreter was found.

On launch a script receives four environment variables:

The script is run over every selected profile in turn. Output goes to the window with timestamps, each profile shows its result and exit code, and the whole protocol is written to logs/scripts/ — the window truncates by scrolling, the file does not.

The window synchroniser

The synchroniser is for when the same thing has to be done in several profiles at once. It has two modes, and they solve different problems.

Mirror: one action into every window

Tick the windows, choose the leading one and set the "Synchronisation on" checkbox. From then on what you do in the leading window is repeated in the rest: press a button and it is pressed everywhere, type text and it is typed everywhere.

We aim not at a screen point but at the page element itself, so the windows can be of different sizes and in different places — that does not affect the repeat. Text is inserted as a value rather than typed as keystrokes, so the keyboard layout and language do not matter.

Handout: its own value for each window

A mirror is useless for registrations: there every account has its own email, its own login, its own number. For that, sets are created on the right — you name them however suits you: "emails", "logins", "numbers". Values are written into a set line by line, one line per window. The Generate button fills a set from a pattern: ivan{n:3}@mail.com gives ivan001, ivan002 and so on.

Spread across windows pins one line to each window without inserting anything — it simply decides who gets what. That is visible in the "Will get" column. Insert into windows puts each window's value into the field where the cursor stands in the leading window.

Shortcuts and stopping

Your hands are in the browser at that point, not in the manager, so everything is done from the keyboard:

An ordinary Ctrl+V works as before — the synchroniser does not touch it.

If the windows drift apart

Pages in different profiles are not always in the same state: something did not finish loading, a captcha appeared, another is on a different step of the form. If on some action most windows cannot find the element they need, synchronisation stops by itself and says why. That is deliberate: carrying on blindly means sending a password into the search field on twenty sites.

The state of each window is visible in the list on the left. The reasons are:

The local API

The API lets scripts and AI agents drive the program. It works on your computer and does not go outside. It is switched on with a checkbox in the settings; the Token… button shows the address, the access key and a ready-made request line — everything copies with one button.

Two levels

Level 1 — driving the manager. Create a profile, launch it, stop it, assign a proxy, check it.

Level 2 — driving the browser. Open a page, run a script, take a screenshot — that is, do in the browser what Playwright does.

The /ext/poll and /ext/result addresses are internal: the extension itself uses them, and you do not need to call them by hand.

Two ways to drive the browser

Way 1 — the /cdp request (the default). The command is carried out by the carrier extension inside the profile. The browser has no debugging port, so signing in to Google works on such a profile — and scripts still drive it. Parameters: profile, method, params, and the optional tab and timeout.

`` curl -H "X-Api-Token: YOUR_TOKEN" ^ "http://127.0.0.1:7999/cdp?profile=work1&method=Page.navigate&params={"url":"https://example.com"}" ``

The command names are the same as in the Chrome DevTools Protocol: Page.navigate, Runtime.evaluate, Page.captureScreenshot, Input.dispatchMouseEvent and the rest.

Way 2 — your own debugging port for Playwright. Turn on the DBG column for a profile and restart it: then /start and /session return a ws://… address to pass to Playwright or Puppeteer. That is convenient for bringing over ready-made scripts, but signing in to Google will not work on such a profile.

What survives a restart of the program

Profiles keep running even if the program is closed. But not everything comes back the same way, and that is worth knowing.

Access for an AI agent (MCP)

The manager can hand control of profiles to an AI assistant — Claude, for instance. Then a one-off job can be given in words: "start three profiles with working proxies and open such-and-such page in them".

How to connect it

First turn on the local API in the settings and tick the "API" column for the profiles you are granting access to. Then, in your AI client's settings, write:

`` { "mcpServers": { "morfiade": { "command": "C:\Program Files\Morfiade\Morfiade.exe", "args": ["--mcp"] } } } ``

The path is to your own program file. Where exactly those settings live, see your client's help. The manager must be running.

What the agent can do

The agent cannot delete profiles — no such capability exists for it.

What to understand about safety

Access works only on your computer: nothing opens outward, to the internet. The agent runs on your machine and talks to the manager over the local loopback. A valid licence is needed here too — without one, launching profiles is closed through the agent as well.

But "local" does not mean "anything goes," and here is why. An agent that reads web pages is not a trusted party. A page can contain text addressed to it: "call such-and-such tool and send the data here." The agent cannot tell a task description from an instruction and may obediently carry it out. This is the acknowledged core problem of such connections, and it has to be guarded against by design, not by carefulness.

So it is built like this:

Separately, about the --mcp-allow-cdp switch. It adds direct control of the browser — the same thing Playwright does. It is off by default, and deliberately so: running arbitrary code in a signed-in profile reads cookies, passwords and page contents. That is worth more than any proxy password. Turn it on only if you understand why you need it, and only on profiles you would not mind risking.

A sensible way to work: keep the "API" checkbox on a handful of working profiles, not all of them, and do not give the agent profiles with valuable accounts.

The operations log

The log on the "Settings" tab shows everything the program does: creating and launching profiles, rolling out extensions, checking proxies, API calls and refusals over a wrong token. Every line is timestamped.

The Save the log to a file checkbox in the settings additionally writes the same protocol to logs/manager_YYYY-MM-DD.log; the files are kept for two weeks, and the Open the log folder button leads to them. Proxy passwords and tokens do not reach the file — they are replaced with asterisks.

If the program closed by itself

For that case it is best to enable the log file and repeat the action. Besides the ordinary protocol, the program saves a crash report alongside: the last events before closing and the cause. That file is what is needed for diagnosis — it shows where everything broke off, even if the window vanished instantly and you had no time to read anything.

Keyboard shortcuts

The last three work while you are in the browser rather than the manager. An ordinary Ctrl+V is not affected.

Common questions

I moved a profile to another computer and the sites do not remember me

An ordinary archive carries bookmarks, history and settings, but not cookies: they are encrypted with a key belonging to your Windows account. Use the Portable (with cookies) mode when exporting — then the sessions move too.

Why cookies from regular Chrome aren't copied

Starting with version 127, Chrome encrypts them with App-Bound Encryption: only Chrome itself can decrypt them, and only where the file originally lived. Copied cookies turn into garbage in the new location, and the browser cleans them out as corrupted. This is protection against session theft, and it can't be bypassed.

The reason isn't the Google account or sync. Chrome treats any profile in its own folder this way, even one that's never signed into an account. And sync doesn't carry cookies at all: it moves bookmarks, history and passwords, but not sessions.

Manager profiles' cookies are transferable — they live from the start in a place they're allowed to be taken from.

I put a profile into regular Chrome, but new sign-ins aren't coming back

That's right. The profile moves into regular Chrome with its sign-ins, but everything Chrome writes from then on in its own folder is encrypted the new way and isn't handed back out.

Work in the manager profile, and hand a copy off to regular Chrome — that way sessions stay transferable.

A cookie disappeared after restarting a profile

If a cookie has no lifetime (a session cookie), any browser deletes it on closing. That is not a lost profile: real sign-ins set cookies with an expiry, and those are kept.

I am going to reinstall Windows, or I am afraid the disk will fail

Prepare in advance — after the reinstall it is too late. Windows encrypts secrets with a key belonging to your account, and a new system will not recover it even if the files are intact.

What is lost in a clean reinstall: the proxy passwords in the program's settings, the cookies and passwords inside Chrome profiles, and the licence binding (you will need to transfer it through the bot). Simply copying folders does not save that: the files copy, but there is nothing left to decrypt them with.

What to do in advance: make an Export of the profiles into an archive. Proxy passwords are in the clear inside it, and the Portable (with cookies) mode preserves the sessions on sites as well. That archive is the real backup — keep it like a secret, preferably on a removable disk.

The API port is taken

The program notices that itself and offers the nearest free one. The port can be changed in the settings at any time — the API restarts on the new one.

The profiles take up too much space

Turn on "Save space" and run "Clear cache" over all profiles once. Account data is not touched.

The proxy shows the wrong country

Check the address with "Check selected" on the "Proxies" tab: it shows the real exit IP and country. The profile's fingerprint is adjusted to exactly that.