Features

Below is what works in version 3.36. Not "on the roadmap", not "coming soon": where something is missing, the same paragraph says so plainly.

Profiles: creating, ordering, finding

A Chrome profile is a separate folder with its own cookies, passwords, history and extensions. Morfiade creates them by the hundred and keeps them from turning into a heap.

• Bulk creation — give a prefix and a count, get shop1 … shop200. A category named after the prefix appears on its own.
• Categories — a filter above the table; move one profile or a whole selected batch with the right mouse button. Deleting a category leaves the profiles alone.
• Human sorting — pir2 comes before pir10, not after it as plain string sorting would have it.
• Search by name, note and category.
• Tags — several per profile, unlike a category. A profile can be "warming up", "US" and "for sale" at once; the filter picks by any of them, and tags can be applied to a whole checked batch.
• Notes on every profile — whose account it is, what for, when it was last used. Visible right in the table and edited there.
• The name does not scroll away. The checkbox, icon and name are frozen on the left: when there are many columns and the table scrolls sideways, you always see which profile you are working with.

Trash

Deleted profiles do not vanish — they go to the trash and stay there until you decide otherwise.

They come back whole: cookies, proxy, notes and tags. Nothing is deleted on a schedule or "expires" after thirty days: only a person empties the trash. A profile with live sessions is often months of work, and we would rather take up disk space than one day explain where it went.

Launching: in batches and on a grid

• Several at a time — profiles open as a group, not one by one. The program waits between launches: Chrome does not like being poked ten times at once.
• A window grid — windows are laid out across the screen without overlapping; size and number of columns are adjustable.
• The interface does not freeze — heavy work happens on separate threads, and the status list is refreshed from a cache.
• Closing — one, the selected ones, or all at once, with processes shut down properly.

Window synchroniser

You opened twenty profiles — from there you either repeat the same thing twenty times by hand, or do it once in the main window.

There are two modes, switched on separately.

Mirror. What you do in the main window is repeated in the rest: typing, clicks, scrolling, navigation.

Handout. Each window gets ITS OWN value from your list. Create a set — "Emails", "Logins", "Phones", as many as you need — enter the values line by line, put the cursor in a field and press the shortcut. The first profile gets the first line, the second the second, and so on.

Others have synchronisers too. The difference is what they aim at:

Each line there is a concrete consequence, not a quibble.

• We aim at the element, not the point. So windows can be different sizes, maximised, with different numbers of tabs, and the page layout can differ slightly. Where a click coordinate is repeated instead, all of that breaks the synchronisation, and the vendors say so honestly in their own manuals.
• We set the value on the field directly. So any language works. Where text is "typed" with keys, everything depends on the keyboard layout: Russian, Chinese and Portuguese arrive in the follower windows mangled.
• The value is pinned to the profile. Repeat the handout and the same profile gets the same line. Close the windows, reopen them, change the order — nothing drifts. An account has one email, and it should not depend on the order the windows happened to open in. The table shows in advance who will get what.

It stops on its own when something goes wrong

That matters more than any convenience. If, over several actions in a row, most windows answer "no such element", the pages have drifted apart: something did not finish loading, a captcha appeared somewhere, another window is on a different step of the form. Carrying on at that moment is not an option — a password would go into the search field on twenty sites at once.

At that point Morfiade stops by itself and says why it stopped.

Plus an emergency stop on a single key — Pause. When twenty windows are doing the wrong thing, reaching for a three-key combination is already too late.

Ordinary Ctrl+C and Ctrl+V keep working as they did.

A proxy for every profile

The proxy belongs to the profile, not to the program as a whole: every window has its own way out to the network.

The forwarder closes together with the profile — both when you close the window from the program and when you close Chrome yourself.

Extensions

• A store inside the program — an extension is added once and from then on installed into any profile by copying, with no trip to the web store and no confirmation dialogs.
• Selective installation — tick the profiles you want, install the extension into all of them at once.
• What is installed is visible per profile.

Anti-detect: an honest fingerprint, not a random one

Switched on with a checkbox on each profile separately — off by default, changing nothing.

The idea everything is built around: it is not the substitution that gives you away, it is the inconsistency. The proxy is in Germany but the time zone is Moscow; the headers say Windows but WebGL reports an Apple graphics card; the fingerprint changes on every launch. Each such contradiction stands out more than an honest, unmodified browser.

So the fingerprint is assembled deterministically — from the profile's permanent seed and the country the proxy actually comes out in:

• time zone, language and geolocation — from the proxy's country, all three consistent with each other;
• Client Hints at the HTTP level — headers that cannot be faked from JavaScript at all; a mismatch between the browser string and these headers is the first thing anyone reads;
• canvas, WebGL and audio — deterministic noise: different for every profile, but unchanged from launch to launch within one profile;
• core count, memory, window size — plausible values for Windows, not random ones;
• the country can be set by hand, and the fingerprint frozen so it is not reassembled.

What we deliberately do not do, and why:

• we do not pass Windows off as Mac or Linux. You have a real Chrome on a real Windows; claiming another system means arguing with the graphics card, the fonts and the engine's behaviour. The contradiction gives you away harder than the truth.
• we do not touch the TLS fingerprint. Ours is genuine already and should not be somebody else's: a real Chrome is the best hiding place for a real Chrome.
• we do not rescue a bad IP. If the proxy address is in a known datacentre range, the captcha will keep asking you regardless of the fingerprint. That was tested for real, against live protection: residential proxies helped, settings did not.

Moving between computers, and backups

• Profile export — together with cookies, proxies, categories and notes.
• Import on another computer: the sessions stay alive, there is no need to sign in to the accounts again.
• Cookies from other programs work. Import understands JSON in the form other profile managers, EditThisCookie and Puppeteer hand out, as well as a plain cookies.txt. You do not have to move in from scratch. One caveat: copying the Cookies file itself out of someone else's folder is useless — Chrome encrypts it with that machine's Windows key, so a proper export is what you need.
• Backups — by a button, of the selected profiles or all of them.
• Export and backups work even with a closed licence: holding someone's own data hostage is not something we consider acceptable.

Automation: scripts and a local API

The "Scripts" tab runs your own scripts: .py, .js, .mjs, .ts, .ps1, .bat, .cmd. The output is visible in the window, and a run can be interrupted.

A script receives the address and token of the program's local API through environment variables — MPC_API_URL, MPC_API_TOKEN, MPC_PROFILE, MPC_WS. Through the API it can list profiles, start them and close them.

And the same is available to an AI agent. The API is open and documented, and when a profile starts it hands over that profile's debugging channel — so the agent does not "press buttons" blindly, it drives the browser directly, the way Playwright does. That can work two ways: the agent does the job itself, working things out as it goes — or it does it once, you save the result as a script, and from then on you run it without any AI at all.

That is exactly where this differs from the ready-made scenario builders competitors offer: there you assemble an action out of prepared blocks and run into the ones they did not put in the box. Here the only limit is what the browser can do.

Connecting an AI assistant directly

The program can act as an MCP server — the common way AI assistants connect to external tools. You add Morfiade to your assistant's settings and then just say what you want: "show profiles without a proxy", "open ten of them on this page", "check whether the proxies are alive".

Eighteen operations are available to the agent: profiles, proxies, tags, notes — and handing out values across windows.

That last one is what does not exist anywhere else. For others, MCP ends at managing profiles, because the handout does not exist in their program either. Here you can say:

The boundaries are set firmly, and they are not up for discussion with the agent:

• the agent sees only the profiles you allowed it to — by a checkbox, one at a time;
• deletion goes to the trash only. The agent reads web pages, and a page may contain "delete such-and-such profiles", which it will carry out as read. With a trash bin that stops being a catastrophe: the profiles sit there whole and come back with one call;
• cookies and passwords are out of the agent's reach — no such operations exist;
• direct browser control is off and is enabled with a separate switch at startup, deliberately.

Small things you notice only when they are missing

• Five colour themes and interface scaling up to 200% — for large monitors and for small ones.
• Six interface languages: Russian, English, Spanish, Portuguese, Vietnamese, Chinese.
• A tray icon and running in the background.
• Disk savings — files common to all profiles are not duplicated.
• Updates on a button, and they are quiet: it asks once at the start, then installs itself and reopens. Open profiles are closed properly — Chrome saves the tabs — and after the update the program offers to reopen them in the same places. Before installing, the update's signature and the file's checksum are verified; data and licence stay where they were.

Requirements

Ready to try — what installing needs. Want to compare with cloud services — Morfiade and Dolphin Anty, Morfiade and GoLogin, Morfiade and AdsPower.