{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"live-share","slug":"live-share","name":"Live Share","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare","page_url":"https://unfragile.ai/live-share","categories":["code-editors"],"tags":[],"pricing":{"model":"free","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"live-share__cap_0","uri":"capability://tool.use.integration.real.time.cursor.and.selection.synchronization.across.distributed.editors","name":"real-time cursor and selection synchronization across distributed editors","description":"Synchronizes cursor positions, text selections, and viewport state across multiple VS Code instances in real-time using a peer-to-peer or relay-based protocol. Each participant's cursor is rendered with distinct visual indicators, enabling awareness of what other collaborators are viewing and editing. The synchronization operates at sub-second latency, propagating keystroke-level changes without requiring manual refresh or conflict resolution.","intents":["I want to see where my pair programming partner is editing in real-time","I need my team to follow along as I navigate through the codebase during a code review","I want to know which lines my colleague is currently viewing without asking"],"best_for":["pair programming teams working synchronously","code review sessions with 2-5 participants","mentoring scenarios where a senior developer guides a junior through codebase navigation"],"limitations":["Cursor synchronization is real-time only — no offline queueing or eventual consistency; connection loss drops all cursor state","No conflict resolution for simultaneous edits at identical line ranges — last-write-wins behavior (UNKNOWN if implemented)","Cursor visibility is binary — cannot selectively hide cursor from specific participants","Viewport following is manual (follow/focus feature) — no automatic scroll synchronization unless explicitly enabled"],"requires":["VS Code 1.x (minimum version unspecified)","Active network connection with P2P or relay connectivity","GitHub or Microsoft account for session authentication","Shared workspace with at least 2 participants"],"input_types":["cursor position (line, column)","text selection range","viewport scroll offset"],"output_types":["rendered cursor indicators in editor","selection highlighting","participant presence indicators in status bar"],"categories":["tool-use-integration","real-time-collaboration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_1","uri":"capability://tool.use.integration.shared.file.editing.with.operational.transformation.or.crdt.based.conflict.resolution","name":"shared file editing with operational transformation or crdt-based conflict resolution","description":"Enables multiple participants to edit the same file simultaneously with automatic conflict resolution using either operational transformation (OT) or conflict-free replicated data type (CRDT) algorithms. Changes made by any participant are propagated to all others with character-level granularity, preserving document consistency without requiring manual merge or lock-based editing. The system maintains a single authoritative document state across all clients.","intents":["I want to edit the same file as my pair partner without one of us being blocked","I need to make edits while my colleague is also editing the same section without losing either change","I want simultaneous multi-person code editing with automatic conflict resolution"],"best_for":["pair programming sessions with active simultaneous editing","code review sessions where multiple reviewers suggest inline edits","team refactoring sessions with 3-5 developers editing the same files"],"limitations":["Conflict resolution algorithm is opaque — behavior for overlapping edits at identical character positions is undocumented (likely last-write-wins or position-based ordering)","No edit history or undo/redo across participants — undo only affects local edits, not remote changes","No branching or divergent editing — all participants converge to single document state (no experimental branches)","Large file edits (>10MB) may experience latency spikes (performance characteristics unknown)","No offline editing — all changes must be synchronized in real-time; connection loss may cause data loss"],"requires":["VS Code 1.x (minimum version unspecified)","Active bidirectional network connection","GitHub or Microsoft account for authentication","All participants must have the same file open in their workspace"],"input_types":["character insertions","character deletions","multi-line paste operations","find-and-replace operations"],"output_types":["synchronized file content across all clients","visual diff indicators showing remote changes","file modification indicator in tab"],"categories":["tool-use-integration","real-time-collaboration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_10","uri":"capability://safety.moderation.read.only.guest.mode.for.code.review.and.observation","name":"read-only guest mode for code review and observation","description":"Enables guests to view and navigate the shared workspace without the ability to edit files or execute commands. In read-only mode, guests can see all files, follow the host's navigation, and inspect code, but cannot make changes. This mode is useful for code reviews, demonstrations, and mentoring where guests should observe without modifying the codebase.","intents":["I want to share my code with reviewers who should only view, not edit","I need to demo code to stakeholders without risking accidental changes","I want to mentor a junior developer by showing them code without letting them modify it"],"best_for":["code review sessions with read-only reviewers","product demonstrations to non-technical stakeholders","mentoring and training sessions where observers should not modify code"],"limitations":["Read-only mode is not enforced at the protocol level — if a guest has write access, they can edit files (UNKNOWN if read-only mode exists)","No granular permissions — cannot restrict specific files to read-only while allowing edits to others","Read-only guests still see all files and can access sensitive information (no file-level access control)","No audit logging of what read-only guests viewed or accessed"],"requires":["VS Code 1.x (minimum version unspecified)","Host to explicitly enable read-only mode (UNKNOWN if this is a configurable option)","Active Live Share session"],"input_types":["read-only mode configuration (host-side)"],"output_types":["read-only indicator for guests","disabled edit controls in guest editors"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_11","uri":"capability://tool.use.integration.cross.platform.collaboration.windows.macos.linux","name":"cross-platform collaboration (windows, macos, linux)","description":"Enables collaboration between developers using different operating systems (Windows, macOS, Linux). The Live Share protocol is platform-agnostic, allowing a Windows user to pair with a macOS user without compatibility issues. File paths, line endings, and other OS-specific details are automatically normalized to ensure consistency across platforms.","intents":["I want to pair program with a colleague who uses a different operating system","I need to collaborate with a team that uses mixed Windows, macOS, and Linux machines","I want to ensure file edits are consistent across different operating systems"],"best_for":["distributed teams with mixed operating systems","open-source projects with contributors on different platforms","organizations with heterogeneous development environments"],"limitations":["Line ending normalization may cause unexpected diffs if not configured consistently (CRLF vs LF)","File path separators are normalized (/ vs \\) but may cause issues with hardcoded paths in code","Shell commands in shared terminals may not be portable across operating systems (bash vs PowerShell)","Performance may vary across platforms due to different file system implementations"],"requires":["VS Code 1.x (minimum version unspecified) on all platforms","Compatible operating systems (Windows 7+, macOS Sierra+, Linux)"],"input_types":["file paths (platform-specific)","line endings (CRLF, LF)","file permissions (Unix-style)"],"output_types":["normalized file paths","consistent line endings","platform-agnostic file metadata"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_2","uri":"capability://tool.use.integration.shared.debugging.session.with.breakpoint.and.variable.inspection.synchronization","name":"shared debugging session with breakpoint and variable inspection synchronization","description":"Enables a host developer to share an active debugging session with remote participants, synchronizing breakpoint state, call stack, variable inspection, and step-through execution across all clients. When the host pauses at a breakpoint, all participants see the same call stack and can inspect variables in real-time. Step operations (step-over, step-into, step-out) are visible to all participants, creating a shared debugging context.","intents":["I want to debug a complex issue with my pair partner watching the same call stack and variables","I need to show my team a production bug by stepping through the debugger together","I want to teach a junior developer how to debug by sharing my debugging session"],"best_for":["pair debugging sessions for complex bugs","mentoring scenarios where a senior developer debugs while juniors observe","post-mortem debugging sessions with 2-4 participants"],"limitations":["Only the host can control debugger (step, continue, set breakpoints) — guests are read-only observers (UNKNOWN if guest breakpoint setting is supported)","Breakpoint state is synchronized only for breakpoints set by the host — guest-set breakpoints may not persist across sessions","Variable inspection is limited to what the host's debugger exposes — no guest-initiated variable watches (UNKNOWN)","Debugging context is language-specific — only works with debuggers supported by VS Code (Python, Node.js, C++, etc.)","No session recording — debugging session cannot be replayed or reviewed asynchronously","Conditional breakpoints and logpoints may not synchronize correctly if they reference local variables (UNKNOWN)"],"requires":["VS Code 1.x (minimum version unspecified)","Active debugging session on host machine","Debugger extension installed for the target language (Python, Node.js, etc.)","Source code accessible to all participants (same workspace shared)","Active network connection"],"input_types":["debugger state (paused/running)","breakpoint locations and conditions","call stack frames","variable values and types","step commands (step-over, step-into, step-out)"],"output_types":["synchronized call stack display","variable inspection panel","breakpoint indicators in editor","execution pointer position","debug console output"],"categories":["tool-use-integration","real-time-collaboration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_3","uri":"capability://tool.use.integration.shared.terminal.instance.with.command.execution.and.output.streaming","name":"shared terminal instance with command execution and output streaming","description":"Exposes a shared terminal instance running on the host machine, allowing all participants to see command execution, output, and interactive prompts in real-time. Commands executed by any participant are visible to all others, and terminal output is streamed to all connected clients. The terminal maintains a shared history and state, enabling collaborative troubleshooting and build processes.","intents":["I want to run build commands and show my team the output in real-time","I need to troubleshoot a deployment issue with my team watching the terminal output","I want to execute commands collaboratively without passing around terminal screenshots"],"best_for":["pair programming sessions requiring build/test execution","deployment and DevOps troubleshooting with 2-3 participants","team code review sessions where tests need to be run live"],"limitations":["Terminal access is shared — guests have full shell access if terminal sharing is enabled (security risk for sensitive operations)","No command history isolation — all participants see all commands executed, including sensitive ones (API keys, passwords may be exposed)","No granular access control — cannot restrict guests to read-only terminal access (UNKNOWN if this feature exists)","Interactive prompts (password input, y/n confirmations) may be confusing with multiple participants (unclear who should respond)","Terminal output is not persisted — no session recording or log export (UNKNOWN)","Environment variables and secrets are visible to all participants if printed to terminal"],"requires":["VS Code 1.x (minimum version unspecified)","Active terminal instance on host machine","Shell access on host (bash, zsh, PowerShell, etc.)","Active network connection","GitHub or Microsoft account for authentication"],"input_types":["shell commands (text)","stdin input (interactive prompts)","environment variables"],"output_types":["terminal output (stdout/stderr)","exit codes","interactive prompts","terminal state (working directory, environment)"],"categories":["tool-use-integration","real-time-collaboration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_4","uri":"capability://tool.use.integration.localhost.web.server.exposure.to.remote.participants","name":"localhost web server exposure to remote participants","description":"Exposes local web servers running on the host machine (e.g., localhost:3000, localhost:8080) to remote participants via a publicly accessible URL. Participants can access the web application running on the host without requiring port forwarding, VPN, or firewall configuration. The exposed URL is temporary and tied to the Live Share session, automatically revoked when the session ends.","intents":["I want to show my team the web app I'm building without deploying it to a staging server","I need to test a web application with my pair partner accessing the same localhost server","I want to demo a frontend change to stakeholders without setting up a public deployment"],"best_for":["web development pair programming sessions","frontend code review sessions with live preview","product demos and stakeholder reviews of in-development features"],"limitations":["Exposed URL is public and temporary — anyone with the URL can access the web server (no authentication layer)","Only HTTP/HTTPS traffic is supported — WebSocket connections may have latency or reliability issues (UNKNOWN)","Server must be running on localhost (127.0.0.1) — cannot expose servers on other network interfaces","Port must be explicitly configured in Live Share settings — automatic port detection is not supported (UNKNOWN)","No request logging or monitoring — cannot see which participants accessed which endpoints","CORS and authentication headers may cause issues if the web app expects requests from specific origins"],"requires":["VS Code 1.x (minimum version unspecified)","Web server running on localhost (Node.js, Python, Ruby, etc.)","Port number configured in Live Share settings","Active Live Share session","Network connectivity to Microsoft's relay infrastructure"],"input_types":["localhost port number (integer)","HTTP/HTTPS requests from remote participants"],"output_types":["publicly accessible URL (https://liveshare.vscode.dev/...)","HTTP responses from localhost server","server logs and output"],"categories":["tool-use-integration","real-time-collaboration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_5","uri":"capability://tool.use.integration.language.service.context.propagation.intellisense.syntax.highlighting.diagnostics","name":"language service context propagation (intellisense, syntax highlighting, diagnostics)","description":"Propagates language service features (IntelliSense, syntax highlighting, error diagnostics, code formatting) from the host's VS Code instance to remote participants' editors. When the host has language extensions installed (Python, TypeScript, C++, etc.), guests automatically receive the same language services without needing to install extensions locally. This includes real-time error checking, autocomplete suggestions, and hover documentation.","intents":["I want my pair partner to see the same IntelliSense and error diagnostics as me without installing language extensions","I need to show my team code completion and type hints for a language they don't have configured locally","I want consistent syntax highlighting and error checking across all participants"],"best_for":["pair programming with developers using different machine setups","code review sessions where guests don't have language extensions installed","onboarding sessions where new team members don't have development environment configured"],"limitations":["Language services are read-only for guests — they cannot trigger IntelliSense or code actions, only view them (UNKNOWN if guest-initiated IntelliSense is supported)","Language service features depend on host's extensions — if host doesn't have a language extension, guests won't see language services for that language","Custom language server configurations on the host are not propagated — guests see default language service behavior","Performance depends on host's language server responsiveness — slow language servers will cause latency for all participants","Language service context is file-specific — switching files may cause brief delays in language service availability"],"requires":["VS Code 1.x (minimum version unspecified)","Language extensions installed on host machine (Python, TypeScript, C++, etc.)","Source code files with recognized file extensions (.py, .ts, .cpp, etc.)","Active Live Share session","Network connectivity for language server communication"],"input_types":["source code files","cursor position (for IntelliSense triggers)","file edits (for real-time diagnostics)"],"output_types":["IntelliSense suggestions","syntax highlighting","error and warning diagnostics","hover documentation","code formatting suggestions"],"categories":["tool-use-integration","real-time-collaboration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_6","uri":"capability://tool.use.integration.session.url.generation.and.guest.invitation.management","name":"session url generation and guest invitation management","description":"Generates a unique, temporary session URL that can be shared with remote participants to join the Live Share session. The URL is automatically copied to the clipboard and can be distributed via email, chat, or messaging platforms. The session URL is tied to the host's VS Code instance and becomes invalid when the session ends or the host closes VS Code. No built-in invitation system exists — distribution is manual.","intents":["I want to quickly generate a shareable link to invite my pair partner to collaborate","I need to send a session URL to multiple team members without manually managing access","I want the session URL to expire automatically when I'm done collaborating"],"best_for":["ad-hoc pair programming sessions","quick code review sessions with small teams (2-5 people)","mentoring sessions where a mentor shares a session URL with a mentee"],"limitations":["No built-in invitation system — session URL must be manually copied and distributed (no email integration)","Session URL is public — anyone with the URL can join (no access control or approval workflow)","No guest limit enforcement — unlimited guests can join a single session (UNKNOWN if there's a practical limit)","No guest management interface — cannot revoke individual guest access without ending the entire session","Session URL is temporary — expires when host closes VS Code (no persistent session links)","No session history or audit log — cannot see who joined or when"],"requires":["VS Code 1.x (minimum version unspecified)","GitHub or Microsoft account for authentication","Active Live Share session","Network connectivity to generate and validate session URL"],"input_types":["session initiation (user clicks 'Start Collaboration Session')"],"output_types":["session URL (https://liveshare.vscode.dev/join/...)","session ID (internal identifier)","session expiration time"],"categories":["tool-use-integration","real-time-collaboration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_7","uri":"capability://tool.use.integration.participant.presence.and.focus.tracking","name":"participant presence and focus tracking","description":"Displays a list of active participants in the Live Share session with their current file and line number. The 'Session Details' viewlet shows which file each participant is viewing and allows the host to 'follow' a specific participant, automatically scrolling to their current location. Participant avatars and names are displayed in the editor, enabling awareness of who is editing which sections.","intents":["I want to see which files my team members are currently viewing","I need to follow my pair partner's navigation to stay in sync","I want to know who is editing which part of the codebase"],"best_for":["pair programming sessions with 2-3 participants","code review sessions where reviewers navigate independently","mentoring sessions where a mentor wants to follow a mentee's progress"],"limitations":["Presence tracking is limited to file and line number — cannot see which specific function or code block a participant is viewing","Follow feature is manual — no automatic following based on participant activity","Participant list is not filterable or sortable — all participants are shown in a flat list","No activity history — cannot see what files a participant viewed previously","Presence updates may lag by 1-2 seconds due to network latency"],"requires":["VS Code 1.x (minimum version unspecified)","Active Live Share session with at least 2 participants","Session Details viewlet visible in VS Code activity bar"],"input_types":["participant file navigation","cursor position changes","follow/focus commands"],"output_types":["participant list with current file and line","participant avatars in editor","follow indicator showing which participant is being followed"],"categories":["tool-use-integration","real-time-collaboration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_8","uri":"capability://tool.use.integration.workspace.wide.file.synchronization.and.access.control","name":"workspace-wide file synchronization and access control","description":"Shares the entire workspace directory with remote participants, enabling them to browse, open, and edit any file in the project. All files are synchronized in real-time, and changes made by any participant are visible to all others. The host can configure which files or folders are shared (UNKNOWN if selective sharing is supported). File access is binary — either the entire workspace is shared or nothing is shared.","intents":["I want to share my entire project with my pair partner so they can navigate and edit any file","I need my team to see the full project structure during a code review","I want to collaborate on multiple files simultaneously without manually syncing them"],"best_for":["pair programming sessions on small to medium projects (<1GB)","code review sessions with full project context","team refactoring sessions affecting multiple files"],"limitations":["All-or-nothing sharing — cannot selectively share specific files or folders (UNKNOWN if this is supported)","Large workspaces (>1GB) may experience slow initial sync and high bandwidth usage","Binary files (images, compiled artifacts) are shared but not editable — may waste bandwidth","No file locking — multiple participants can edit the same file simultaneously (relies on conflict resolution)","No .gitignore respect — all files including node_modules, build artifacts, and secrets are shared (UNKNOWN)","Workspace-wide search and replace operations may cause conflicts if multiple participants trigger them simultaneously"],"requires":["VS Code 1.x (minimum version unspecified)","Workspace folder open in VS Code","Active Live Share session","Network bandwidth sufficient for workspace size"],"input_types":["workspace directory structure","file contents (text and binary)","file metadata (modification time, permissions)"],"output_types":["synchronized file tree in VS Code explorer","file contents accessible to all participants","file modification indicators"],"categories":["tool-use-integration","real-time-collaboration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__cap_9","uri":"capability://safety.moderation.authentication.and.session.lifecycle.management","name":"authentication and session lifecycle management","description":"Manages user authentication using GitHub or Microsoft accounts, establishing the identity of the host and guests. Sessions are created when the host initiates collaboration and destroyed when the host closes VS Code or manually ends the session. Authentication is required only once per VS Code installation; subsequent sessions reuse the cached credentials. Session lifecycle is tied to the host's VS Code instance — if the host closes VS Code, all guests are disconnected.","intents":["I want to authenticate once and then start collaboration sessions without re-entering credentials","I need to ensure only authorized team members can join my collaboration session","I want my session to automatically end when I close VS Code to prevent unauthorized access"],"best_for":["teams using GitHub or Microsoft accounts for identity management","organizations requiring single sign-on (SSO) via GitHub or Microsoft","developers who want simple, one-time authentication setup"],"limitations":["Only GitHub and Microsoft accounts are supported — no LDAP, SAML, or other enterprise authentication","No granular access control — authenticated users can join any session they have the URL for (no role-based access)","Session authentication is tied to host — guests are identified by their GitHub/Microsoft account but have no separate permissions","No session-level access tokens — cannot revoke individual guest access without ending the entire session","Credentials are cached locally — if VS Code is compromised, cached credentials may be exposed","No audit logging — cannot see who authenticated or when"],"requires":["VS Code 1.x (minimum version unspecified)","GitHub or Microsoft account","Network connectivity to GitHub or Microsoft authentication servers","First-time authentication requires browser redirect"],"input_types":["GitHub or Microsoft account credentials (via OAuth)","session initiation command"],"output_types":["authentication token (cached locally)","session ID","participant identity (GitHub/Microsoft username)"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"live-share__headline","uri":"capability://code.generation.editing.real.time.collaborative.code.editing.extension","name":"real-time collaborative code editing extension","description":"Live Share is a real-time collaborative editing and debugging extension for Visual Studio Code, enabling developers to share their workspace seamlessly for pair programming and code reviews.","intents":["best real-time collaborative coding tool","collaborative coding extension for VS Code","real-time debugging tool for developers","pair programming solution for software teams","interactive code review tool for VS Code"],"best_for":["remote teams","pair programming","code reviews"],"limitations":["requires VS Code","no AI features"],"requires":["Visual Studio Code"],"input_types":[],"output_types":[],"categories":["code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":57,"verified":false,"data_access_risk":"high","permissions":["VS Code 1.x (minimum version unspecified)","Active network connection with P2P or relay connectivity","GitHub or Microsoft account for session authentication","Shared workspace with at least 2 participants","Active bidirectional network connection","GitHub or Microsoft account for authentication","All participants must have the same file open in their workspace","Host to explicitly enable read-only mode (UNKNOWN if this is a configurable option)","Active Live Share session","VS Code 1.x (minimum version unspecified) on all platforms"],"failure_modes":["Cursor synchronization is real-time only — no offline queueing or eventual consistency; connection loss drops all cursor state","No conflict resolution for simultaneous edits at identical line ranges — last-write-wins behavior (UNKNOWN if implemented)","Cursor visibility is binary — cannot selectively hide cursor from specific participants","Viewport following is manual (follow/focus feature) — no automatic scroll synchronization unless explicitly enabled","Conflict resolution algorithm is opaque — behavior for overlapping edits at identical character positions is undocumented (likely last-write-wins or position-based ordering)","No edit history or undo/redo across participants — undo only affects local edits, not remote changes","No branching or divergent editing — all participants converge to single document state (no experimental branches)","Large file edits (>10MB) may experience latency spikes (performance characteristics unknown)","No offline editing — all changes must be synchronized in real-time; connection loss may cause data loss","Read-only mode is not enforced at the protocol level — if a guest has write access, they can edit files (UNKNOWN if read-only mode exists)","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.7,"quality":0.9,"ecosystem":0.15000000000000002,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.327Z","last_scraped_at":null,"last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=live-share","compare_url":"https://unfragile.ai/compare?artifact=live-share"}},"signature":"Q8ym8lloxdkyGsuz6mrPDaQurK1IXr/uPWMn3H30GblO4Ctj7la1IQ/Yscr3HsILPxBZRBz4/C+4X61w3UOeAg==","signedAt":"2026-06-19T18:48:30.547Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/live-share","artifact":"https://unfragile.ai/live-share","verify":"https://unfragile.ai/api/v1/verify?slug=live-share","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}