# Signing in

> Separate sessions per pane, and a signed-in session brought over from your browser.

Every [browser pane](/docs/browser) is in a named session: its own cookies, its own storage, its own logins. Two sessions share nothing, so you can be signed in as one account in `default` and as another in `work`, one pane each.

## Named sessions

A pane opens in `default`. The **Browser menu** lists the sessions with a tick on this pane's; pick another and the page opens again in it — the session a webview is in is fixed when it is built, so the page has to be reopened, and devpit does that rather than showing one name while using another's cookies.

**New session…** takes a name — letters, digits, dashes and underscores — and **Make** puts the pane in it. Nothing is written until a page opens there, so a name you never use leaves nothing behind.

Sessions belong to devpit rather than to a project: every pane that picks `work` is in the same `work`. They are kept under `~/.devpit/browser/`.

## Bring a signed-in session

Rather than signing in again inside the pane, you can bring a login over from a browser this machine already has. In the **Browser menu**, under **Bring a signed-in session**:

1. **Only** — the site to keep, starting as the host of the page you are on. Leave it empty and every cookie in the profile is kept.
2. **From Google Chrome**, **From Firefox** and so on — then the profile, when that browser has more than one.

The cookies land in this pane's session, and devpit says what it took: "Brought 12 cookies from Firefox for github.com. Reload the page to use them."

Nothing is imported because it was found, and nothing moves until you pick a profile. A profile is read whole — the file gives no cheaper way — and only what **Only** names is kept.

| Family | Read from |
|---|---|
| Chromium | Google Chrome, Chromium, Microsoft Edge, Brave, Vivaldi |
| Firefox | Firefox |
| Safari | Safari |

A Chromium profile usually keeps its key in the desktop keyring. devpit asks the keyring through `secret-tool`; on a machine without it, the profile says so under its name and points at `libsecret-tools`, instead of importing nothing and leaving you to guess why.

## Signing out

The last item in the menu names the session this pane is in: **Sign out of “default”**. It removes that session from disk — its cookies, its storage, its logins — and says how much it is about to remove before you press it. It is greyed out while the session is holding nothing. The other sessions are untouched, and the next page opened in this one starts signed out.

There is no undo. Bringing a signed-in session over again is the way back in.
