Profiles

A profile keeps what you do in Chrome on an orb’s Desktop: the sites you are signed in to, saved passwords, and site data such as local storage. When another orb uses the same profile, Chrome there starts signed in, so you and the agent do not have to sign in again.

To use profiles, turn on Profiles in Experimental Features.

Open tabs stay with the thread that opened them. A thread’s Chrome starts with a new tab, not the tabs of other threads, and reopens the thread’s own tabs when Chrome restarts.

You can have several profiles, for example one for work accounts and one for a test account. Profile names use 3 to 32 letters, numbers, and hyphens, such as Work or booking-travel.

Choosing a Profile

  • New thread: when you start an orb thread, choose a profile from ⋮ › Profile in the composer. The orb starts with it, and the composer remembers your choice for the next thread. A profile you just created is selected for you.
  • CLI: run amp -ox "<prompt>" --profile <name or ID> to start an orb thread with a profile. See Spawning Orbs.
  • Desktop tab: open the Desktop tab of an orb thread and pick a profile from the menu at the left of the toolbar. If Chrome is open, it restarts with that profile and a new tab.
  • Thread menu: choose ••• › Orb › Profile.

An orb can read and save only the profile chosen for its thread.

The Desktop tab of an orb showing silkcards.com order history, with the profile menu open: Ordering Swag is signed in to 2 sites, and Work, Booking Travel, Office Supplies, New Profile, and No Profile are listed below it The Desktop tab of an orb showing silkcards.com order history, with the profile menu open: Ordering Swag is signed in to 2 sites, and Work, Booking Travel, Office Supplies, New Profile, and No Profile are listed below it

Letting the Agent Choose a Profile

By default only you choose a thread’s profile, in Amp in your browser. To let the agent switch threads to a profile itself, turn on Allow Agent to Select for it in Settings › Profiles. Anything running in your orbs can then select it the same way, since it runs with your Amp credentials.

When a web task needs a sign-in, the agent looks for a profile that fits it. If none does, it suggests a new one, such as booking-travel, and you approve or rename it in a dialog. A profile created this way is allowed for the agent and kept out of multiplayer threads. You can also just ask: “Make me a profile for travel, then find a United flight to Tokyo.”

Inside an orb, the agent or a script then runs amp profile use <name>. The command returns once Chrome has restarted with the profile. amp profile none goes back to a clean profile. To have every orb thread use a profile, add a line like this to your AGENTS.md:

Before using Chrome, run `amp profile use Work`.

Saving

Sign-ins and local storage sync right away: when you sign in or out of a site in one orb, or a site changes what it keeps in local storage, every other orb using the same profile picks it up within a few seconds, without restarting Chrome. Chrome also saves the rest of the profile, such as other site data and saved passwords, every 2 minutes and whenever you switch profiles, if anything changed since that orb last saved it.

If two orbs change the same site’s sign-in at once, the first change to reach Amp wins, except that signing out always wins, so a site never signs you back in. If two orbs change a site’s local storage at once, both changes are kept, unless they changed the same entry; then the first change to reach Amp wins. When two orbs use the same profile at once, each save keeps what the other orbs saved: an orb saves only what it changed itself, such as one site’s data. Saved passwords from both orbs are kept. If both orbs changed the same site’s data, the save that reached Amp first wins. Chrome that is already open keeps what it has until it restarts with the profile.

Profiles work in Linux orbs. macOS orbs do not offer them.

Multiplayer

Anyone who can use a multiplayer thread can use its orb, including Chrome, the terminal, and files. So a thread that uses a profile cannot be made multiplayer. Choose No Profile for the thread first, then wait a few seconds while the orb clears the profile from Chrome.

To use a profile in multiplayer threads anyway, turn on Allow in Multiplayer for it in Settings or from the Desktop tab’s profile menu. If you turn it off while such a thread is multiplayer, Chrome there restarts with a clean profile.

Security

  • Profiles are encrypted at rest, and only your own orb threads can read them.
  • A profile never keeps your Amp sign-in or sign-ins to orb portals.
  • Deleting a profile erases everything saved in it.