Keep Browser

Create a tab tree from public URLs and content selected for sharing in this conversation, preserving available names, grouping, hierarchy and order. This tool creates links; it does not research or recommend candidates. Create a public-by-link KeepShare for a NEW tab tree. Anyone with the resulting link can access the shared content and import the same tree; access is not restricted to this chat. Only send public HTTP(S) URLs, never private/authentication links. A public summary page is added as the first tab; its title is the root group name. Supply summary.locale, an optional existing overview and optional per-tab descriptions from the presented content. Anyone with the summary URL can read these names and notes. Reserve one node within the existing limit; never drop selected tabs to make room. Summary notes and names become part of the retry identity and must remain unchanged for the same operation_id. Use exact public URLs from this chat or research, never guess, truncate or complete them from memory. Identify unresolved candidate URLs instead of silently substituting or dropping candidates. Input uses a root label object with nodes nested directly in children, without node IDs or root_id. A tab holds its URL and can contain child tabs; a label groups nodes without adding a URL. For root and child label groups without a user-supplied name, generate concise, descriptive names from their tabs, tree structure and conversation context. Use the requested naming language, or otherwise the conversation language. Prefer names explicitly supplied by the user over generated names when they meet the limits; do not rename a valid supplied label. Root must be a label up to 80 Unicode code points. Root labels cannot contain < or >; non-root labels may contain them. When generating root names for technical topics, express the meaning without these characters. Non-root labels must fit within 200 UTF-16 code units: for example, 😀 uses 2 units and combined emoji can use more. Shorten oversized generated labels; if a user-supplied name violates a label rule, explain the restriction instead of silently replacing it. Oversized labels are rejected, not truncated. Preserve children order. For every selected URL, pair url with display_name in the same tab object, using the place, product, article or page name associated with that URL in this same chat. A short follow-up such as sharing earlier candidates still includes their names, not only group labels. Omit display_name only if no corresponding name is available. These display names are not fetched titles and do not change the original page URLs or app tab names. For summary requests, names also appear on the summary page. summary_status=ready confirms that the page was saved; summary_status=pending means the share link was created but summary activation needs a retry using the same original input. operation_id identifies a creation intent, not an individual call. A fresh UUID identifies a new requested share or changed content. Repeated calls for the same creation intent use the SAME operation_id and identical input, including names, notes and summary when present. Changing the ID loses duplicate protection for that intent. A successful result (status=prepared) contains the HTTPS share_url, share_access and import_flow facts, installation requirements in install_note, and device_import_status=unknown. Success confirms link creation only. This tool cannot detect installed apps, confirm completed device import, or modify existing device tabs. Failure results include wait_reason, retry_after_seconds and retry_not_before_utc. Limits are shared. A returned deadline is the earliest retry time, not a promise of recovery. When both retry fields are null, the retry time is unknown. retry_action describes the service outcome: wait_for_user_retry indicates a later retry after the returned waiting period; review_input indicates invalid input; review_conflict indicates an idempotency conflict; review_result indicates an unresolved result. The service does not schedule background creation or notifications. Changing IDs, source addresses or routes does not remove the applicable limits. A timeout, missing response or retryable error does not establish a new intent. Duplicate protection within the 48-hour retention period depends on the SAME operation_id and identical creation input. attempt_status describes only this attempt. not_sent does not prove a previous uncertain attempt failed to create a share; missing logs alone do not prove non-creation either. A share URL and successful creation are established only by a successful result. After 48 hours the idempotency record can be purged. Retries do not extend that retention. An unresolved attempt repeated with a new ID, changed content or after retention expires can create a duplicate. An already-created share URL remains the reference for redisplaying that result.

create_tab_tree_link