Glossary
Understand profiles, groups, folders, engines, sessions, sync revisions and automation terms.
Use these terms when you compare a profile’s setup, account copy and running browser.
| Term | Meaning |
|---|---|
| Profile | One stored browser identity, configuration and browsing-data directory |
| Profile ID | The stored identifier used by automation; obtain it from a list response |
| Profile number | The register’s short number; v1 calls it serial_number, v2 calls it profile_no |
| Fingerprint | The operating system, user agent, graphics, hardware and noise settings presented to a website |
| User agent | The browser identity string; it must agree with the rest of the fingerprint |
| Engine | The browser binary that opens a profile: SunBrowser or Chroma according to its stored format |
| Kernel | A version of the browser engine, often identified by its Chromium major |
| Pin | The engine major a profile requires; an installed newer major does not replace it automatically |
| Group | A profile’s single group; separate from folders and member groups |
| Folder | An organisational collection; it can have subfolders and a profile can belong to several |
| Member group | A reusable team rank and permission list |
| Rank | Owner, Admin, Manager or Employee; governs what a member may do |
| Profile access | The folders and profiles a member may reach within their rank |
| Session | The signed-in state a browser or site uses; stored cookies can be expired |
| Browser data | Supported cookies, bookmarks, local storage, IndexedDB, extension data and history |
| Gateway | The proxy host and port you connect to |
| Exit IP | The public address seen by the website after the proxy connection |
| Sticky session | A provider credential parameter requesting a held exit; its duration and exit are decided by the provider |
| Proxy template | A rule that composes provider connection parameters when creating a profile |
| Profile template | Reusable setup choices with identifying seeds and credentials removed |
| Account-owned profile | A profile saved to the account and available to connected computers |
| Local-only profile | A profile kept on this computer rather than saved to the account |
| Revision | The version of an account record used to detect competing edits |
| Conflict | A change made on both sides that needs an explicit resolution |
| Device join token | An enrolment credential for joining computers; different from a Local API token |
| Local API token | The credential protecting this computer’s HTTP automation server |
| Workspace API token | A credential for the account service, used by CLI account operations |
| CDP | Chrome DevTools Protocol; automation connects to the endpoint returned by Start |
| MCP | The tool interface an AI client uses to discover and operate Clout profiles |
| Run | A recorded batch with per-profile results; a finished run can still contain failed items |
| Bypass | Traffic sent directly where allowed, rather than through a proxy; balance and measured bytes are separate |
| Read-only | Account writes are refused; it does not mean every existing browser is stopped |
Start with Profiles, Computers and sync or Local API for the corresponding workflow.