Skip to main content
Use manage_profiles when a browser needs saved login state across sessions. A profile persists cookies and session data, so your agent can reuse authenticated state instead of asking the user to sign in every time. For profile concepts and SDK examples, see Profiles.

​
Actions

ActionDescription
setupCreate or update a profile with a guided live browser session.
listList all profiles.
deleteRemove a profile.
  1. Call setup with a memorable profile_name.
  2. Open the returned live view URL and sign in to the target accounts.
  3. Delete the setup browser when you’re done so Kernel saves the profile changes.
  4. Use profile_name or profile_id with manage_browsers or manage_browser_pools when launching future sessions.

​
Parameters

ParameterDescription
actionOperation to perform: setup, list, or delete. Required.
profile_name(setup, delete) Profile name. For setup: 1–255 chars. For delete: name of the profile to remove.
profile_id(delete) Profile ID to delete. Alternative to profile_name.
update_existing(setup) If true, update an existing profile. Default false.
query(list) Search profiles by name or ID.
limit(list) Max results per page. Must be 1-100.
offset(list) Pagination offset. Must be 0 or greater.

​
Response behavior

By default, list returns the full matching profile inventory so agents can choose a profile without paging. When you pass limit or offset, list returns structured pagination JSON with items, has_more, and next_offset, including explicit empty pages.

​
Set up a profile

{
  "action": "setup",
  "profile_name": "work-accounts"
}

​
Search profiles

{
  "action": "list",
  "query": "work",
  "limit": 20,
  "offset": 0
}