Ever been confused about the difference between an agent and a launcher? No worries – you’re not alone! These two work together in Multilogin web interface, but they have totally different jobs. 

In the Multilogin web interface, the legacy agent connects your computer to Multilogin and starts or updates the launcher. The launcher handles local browser-profile runtime tasks, such as downloading browser cores and starting or stopping browser profiles.

If you use the Multilogin desktop app, you do not need to connect the separate legacy agent – the app has its built-in launcher.

What’s an agent? 

The agent is a small legacy app that you download and install on your device. It quietly runs in the background and makes sure the launcher is good to go. Think of it as the backstage crew making sure the show happens.

What does the agent do?

• Sets up the local Multilogin files and folders needed by the launcher
• Downloads the launcher (if it’s missing or outdated)
• Starts the launcher

What’s a launcher?

The launcher is where all the magic happens. It talks to browsers, manages profiles, and connects with the backend. If the agent is the assistant, the launcher is the main character getting things done.

What does the launcher do?

• Finds and downloads browser cores when needed
• Manages profiles by starting and stopping them
• Keeps profile data in check and uploads it to the cloud

How it all comes together

Here’s how the agent and the launcher team up:

1. You onnect the agent
2. Agent launches and updates the launcher
3. Launcher connects to the database and loads profile data
4. Launcher starts the profile so you can get to work

Without the agent or the desktop client, the launcher wouldn’t even start. Without the launcher, your profiles wouldn’t work. They’re the ultimate duo! Now that you’ve got the scoop, you’ll know exactly what’s up if something isn’t working.