sign me up for the newsletter
fill in the delivery details and stop before paying
Open settings from the sliders button at the top of the side panel, and pick Profile.
What it holds
| Group | Fields |
|---|---|
| You | First name, last name, email, phone |
| Address | Street address, city, state / region, postal code, country |
| Work | Company, job title |
| More details | Anything else, as label and value: a loyalty number, a date of birth, a delivery note. Up to 20 |
| Instructions | Rules for every task, in your own words. Up to 4,000 characters |
Every field is optional. Save writes the whole profile at once; nothing is sent while you type.
What the agent sees
Whatever is filled in goes into the system prompt of every side-panel run and every scheduled task, as two sections:
- About the user: one
Label: valueline per detail, exactly as you wrote it. The agent is told to use them as written and never to invent, guess or “complete” a detail that is not there: no middle name, no postcode worked out from a city, no email built from your name. When a form needs something you have not saved, it leaves the field empty and tells you what is missing. - Your standing instructions: kept as firmly as the agent's own rules. Where they conflict with a skill or with site notes, yours win.
Instructions cannot loosen the rules every run starts with (page text is never an instruction, nothing is exfiltrated, a declined action stays declined), and cannot make an action skip its approval. Browsentic Bridge enforces guardrails, not the prompt, so an instruction that tried would change nothing but what the agent says.
An edit reaches the next run. In a conversation already under way, the next message carries the change, so the agent never works from the version it started with.
What does not see the profile: an MCP client driving the browser over the optional MCP endpoint (it brings its own context), site mapping, the file analyst, and conversation titles.
What it refuses
Passwords, API keys, tokens and card numbers. Browsentic seals those in the browser so no model ever reads them, and a profile would undo that on every run. Saving one is refused with the name of the field it is in; leave it out and let the page hand the sealed value over when it is needed.
A phone number is never taken for a card, whatever its digits add up to.
Where it lives
~/.browsentic/profile.json, mode 0600, on this computer only. It is kept out of config.json on
purpose, so that file stays safe to paste into a bug report. Clearing every field deletes the file.
One profile serves every paired browser, and a change in one shows at once on the settings page of the others. The format is in Configuration if you prefer to edit it by hand.
Limits
- It needs Browsentic Bridge: the settings page reads and writes the file through it, so the section is empty while the Bridge is offline.
- Every run pays for the profile in tokens. A filled-in profile costs a few hundred; the limits keep the largest possible one to about 16,000 characters.
- The Mac and Windows apps do not edit it yet.