本页面暂无您所用语言的版本,您正在阅读英文原文。
Team
A second computer and the same accounts: what travels along
ARMANOS 团队7 minUpdated

In short
Settings travel by themselves. Name, group, fingerprint template and proxy arrive through your account.
The session travels on your command. By transfer file or through a shared folder, as you prefer.
The fingerprint stays the same. It travels with the profile, so the device does not change.
Why your accounts want a fresh login
Your cookies, saved logins and site storage are written by the browser into the profile folder on the computer you worked at.
The second computer cannot see that folder, and the only way it fills one is from scratch.
Only the settings reach the second machine through your account: name, group, scenario, fingerprint template, proxy and tags.
The same profile opens there but empty inside, so the platform meets a stranger rather than you.
- 1
Settings travel alone
The profile record lives in your account and reaches every machine you sign in on.
- 2
The session waits
Cookies and logins stay on the first machine until you send them yourself.
- 3
The fingerprint holds
The fingerprint travels with the profile, so it stays the same.
What the account carries and what stays
Your account carries the profile record: name, group, scenario, fingerprint template, proxy, tags and notes.
That is enough for the profile list on the second machine to look exactly like the list on the first.
Everything else lives on the disk of the machine whose browser wrote it, and it travels nowhere on its own.
The table below splits one and the same profile window in two.
| What | Carried by the account |
|---|---|
| Name, group, scenario, tags, notes | Yes, the list on the second machine looks the same |
| Fingerprint template and generation | Yes, so the fingerprint stays the same |
| The profile proxy | Yes, the profile leaves by the same address |
| The pinned browser version | No, it stays on this machine |
| The browser version of a profile without a pinned kernel | No, each computer gives its own: keep the app updated on both and use the same engine on both |
| Cookies, saved logins, site storage | No, they sit on the first machine |
| One-time code key and hand-picked fingerprint values | No, they stay on this machine |
Two roads for a session
There are exactly two, and the choice is yours.
The first is a file, Transfer with session in the profile menu: a closed profile goes into one password-protected archive that you carry on a stick, by mail or however you like.
The second is Session in the folder.
On the Engine screen, in Sessions on two computers, through a folder, you point the app at any directory your own cloud already syncs, and the session of a closed profile goes there by itself.
| Road | When people take it |
|---|---|
| A file under a password | A one-off move or handing a profile over |
| Session in the folder | You switch between two of your own machines daily |
When to pick a file and when a folder
A transfer file suits a single move or a ready profile for a partner. You build it, pass it on and load it on the other side.
A shared folder suits working on two computers in turns. The session leaves by itself when the profile closes and arrives before launch.
Both ways write the same file, so a session written one way can be opened the other way.
What sits inside the transfer file
The archive carries everything that keeps an account logged in, plus the fingerprint of the profile. That is why on the second machine it is the same machine and not one that merely resembles it.
The file is protected by a password of at least 8 characters. A wrong password gives a clear refusal, not a broken profile. The size limit is 400 MB and you rarely reach it: the cache is not included.
- 1
The session travels
Cookies, logins and site storage of both engines sit in one archive.
- 2
The fingerprint travels
The fingerprint and its generation travel with the profile, so the fingerprint matches.
- 3
The cache and components stay behind
The cache and service files stay in place: sites refill them, and the engine downloads its own components.
A copy is not a move
A copy and an archive look alike and carry different things.
A copy is a blank for a new account: its own fingerprint, its own code key and its own login, or two accounts would look like one machine.
Ten fields are common to every transfer road, and the archive adds five more on top of them.
Those five are the whole difference between the same account on a second machine and a new account standing beside it.
| What exactly | Archive | Copy |
|---|---|---|
| Name, scenario, template, tags, notes, opening address | Yes | Yes |
| Run without a window, browser version, address change and interval | Yes | Yes |
| Fingerprint generation and hand-picked values | Yes | No |
| One-time code key and the saved login | Yes | No |
| Proxy exit country | Yes | Yes |
What to do if the platform asks for confirmation
If a platform asks you to confirm the sign-in after a move, the session most likely did not arrive.
Close the profile on the first computer, move the session again and open the profile on the second.
If the confirmation stays, go through it once: the platform will remember the second computer.
How not to lose sign-ins in a move
Close the profile before the transfer: an open profile writes its databases, and the copy would be incomplete.
Do not create the profile from scratch on the second computer: a new profile gets another graphics card and another screen.
Move the whole profile, with the session and the fingerprint: then the account sees the same machine.
The folder carries the session itself
A profile open right now goes nowhere under any circumstances. A running browser is writing its databases, and a copy taken mid-flight would arrive on the second machine broken.
If both sides changed since the last exchange, ARMANOS writes to neither. You see which session came from where and choose yourself.
- 1
Closed profiles travel
The session goes out after you close the profile, not while you are working.
- 2
It arrives before the start
A fresh session comes in from the folder before the profile opens for you.
- 3
The choice stays yours
When both sides changed. On upload the previous pair is then set aside as a copy, and the last three such copies are kept.
What ARMANOS does during an exchange
When you close a profile, the session goes to the shared folder, and a fresh one arrives before launch on the other computer.
The app decides what to send, what to fetch and when to do nothing. A disputed case is shown to you.
If the cloud put a copy next to the file, ARMANOS names it and waits for your choice.
One password protects all sessions in the shared folder. Set it once and keep it to yourself.
How many machines your plan allows
The exchange runs between your own machines, and the number of seats for them sits in the plan. A machine takes a seat at its first sign-in and frees it again at the moment you unlink it.
Seats follow the payment in force, not a number handed out at some point in the past. After a downgrade the extra machine loses its seat and cannot win it back by signing in again.
| Plan | Machine seats |
|---|---|
| Free | 1 |
| Professional | 2 |
| Business | 5 |
| Enterprise | 20 |
How to check the move
Open the profile on the second machine and visit the platform that has remembered you the longest. Getting in with no password and no confirmation means the session arrived whole.
A confirmation prompt leaves two things to check: whether you closed the profile before sending it, and whether the passphrase for the sync files is the same on both.
How to tell the move worked
After a transfer the app names the profile and says whether the session arrived with it.
Open the profile and go into the account: if the platform asks for no confirmation, the move worked.
Run "Test fingerprint": the device should answer the same as on the first computer.
Common questions
- Why did some accounts stay and others ask for a login?
- The ones that stay are the ones you signed into here. What the first machine wrote sits there until the session moves.
- Can I just copy the profile folder by hand?
- Better not. The browser writes its databases while the window is open, and a folder copied mid-flight arrives broken.
- What if I forget the password of a transfer file?
- There is nothing to open the files with: only you know the password. Keep it in a password manager.
- How big is a file with a session?
- Smaller than the profile folder itself: the cache and the browser's service files stay at home, and the engine downloads its own components. The size limit is 400 MB.
- Will the fingerprint stay the same on the second machine?
- It will. The fingerprint and its generation travel with the profile, so on any machine the site sees the same device.
- Can I work in one profile from two computers at once?
- One computer holds the profile, so an account never has two live sessions from two places.
Keep reading
Moving work between machines
The order on both sides and what each road costs.
A profile moves with its session
What goes into one file and what closes it.
Move a profile to another computer
The steps in order, and what a refusal means.
Free fingerprint check
12 values read in your browser, with nothing sent anywhere.
Move one profile
Close it, build a transfer file and load it on the other computer: the app names the profile and tells you whether the session arrived.