{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"vscode-synapsevscode-vscode-synapse-remote","slug":"fabric-data-engineering-vs-code-remote","name":"Fabric Data Engineering VS Code - Remote","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=SynapseVSCode.vscode-synapse-remote","page_url":"https://unfragile.ai/fabric-data-engineering-vs-code-remote","categories":["code-editors"],"tags":["__web_extension","Data Engineering and Data Science","Fabric","Machine Learning","Microsoft","Spark","Synapse"],"pricing":{"model":"freemium","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"vscode-synapsevscode-vscode-synapse-remote__cap_0","uri":"capability://automation.workflow.browser.based.notebook.creation.and.management","name":"browser-based notebook creation and management","description":"Enables creation, reading, updating, and deletion of Microsoft Fabric notebooks directly within VS Code for the Web without requiring the Fabric portal. The extension integrates a sidebar tree view that displays all notebooks in the current workspace, with inline editor controls for managing notebook lifecycle. Changes are synchronized in real-time to the cloud-based Fabric workspace through authenticated API calls to the Fabric backend.","intents":["Create new notebooks in my Fabric workspace from VS Code Web","Edit existing notebook content without switching to the Fabric portal","Delete or organize notebooks directly in my editor sidebar","View all notebooks in my workspace in a familiar VS Code tree structure"],"best_for":["Data engineers working in browser-only environments","Teams using VS Code Web as their primary IDE","Users who prefer lightweight notebook authoring outside the Fabric portal"],"limitations":["Notebook operations are scoped to the current Fabric workspace only — no cross-workspace management","File system access is restricted to notebook resource files/folders, not general file system","Changes require active network connectivity to Fabric backend; no offline editing capability","Public Preview status means breaking changes possible in future releases"],"requires":["VS Code for the Web (vscode.dev)","Active Microsoft Fabric workspace with appropriate permissions","Modern browser with WebSocket support","Authentication to Fabric workspace (inherited from VS Code Web session)"],"input_types":["notebook metadata (name, description)","notebook content (code cells, markdown cells)","file/folder names for resource management"],"output_types":["notebook objects stored in Fabric workspace","file system entries in notebook resource directory","confirmation of CRUD operations"],"categories":["automation-workflow","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-synapsevscode-vscode-synapse-remote__cap_1","uri":"capability://automation.workflow.kernel.selection.and.notebook.execution","name":"kernel selection and notebook execution","description":"Provides a dropdown kernel selector in the notebook editor's top-right corner that allows users to choose the execution runtime before running notebook cells. The extension communicates the kernel selection to the Fabric backend, which then executes code cells against the selected kernel environment. Execution is triggered via a Run button in the editor interface, with results streamed back to the notebook for display.","intents":["Select which kernel/runtime to execute my notebook against","Run notebook cells and see execution results in the editor","Switch kernels mid-session without leaving VS Code Web","Execute Spark or Python code against Fabric compute resources"],"best_for":["Data engineers running Spark or Python workloads in Fabric","Teams executing multi-language notebooks (Spark SQL, PySpark, Scala)","Users who need quick kernel switching without portal navigation"],"limitations":["Specific available kernels are not documented — depends on Fabric workspace configuration","Debugging is explicitly NOT supported (stated as roadmap feature)","Kernel execution runs remotely on Fabric backend, not locally — no local execution option","No kernel configuration or customization UI exposed in the extension"],"requires":["VS Code for the Web (vscode.dev)","Active Fabric workspace with at least one configured kernel","Network connectivity to Fabric compute backend","Appropriate IAM permissions to execute against selected kernel"],"input_types":["kernel selection (dropdown choice)","notebook cell code (Python, Scala, SQL, R depending on kernel)","execution trigger (Run button click)"],"output_types":["cell execution results (stdout, stderr, structured data)","error messages and stack traces","execution status indicators"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-synapsevscode-vscode-synapse-remote__cap_2","uri":"capability://automation.workflow.notebook.resource.file.system.management","name":"notebook resource file system management","description":"Allows users to add, organize, and delete resource files and folders within a notebook's file system namespace through the VS Code sidebar interface. The extension provides file/folder creation and deletion operations scoped to the notebook's resource directory, enabling users to manage supporting files (data files, config files, dependencies) without leaving the editor. Operations are synchronized to the Fabric workspace's notebook file system storage.","intents":["Add data files or configuration files to my notebook's resource directory","Organize notebook resources into folders for better structure","Delete obsolete resource files without portal navigation","Manage file dependencies for notebook execution"],"best_for":["Data engineers managing notebook-scoped resources and dependencies","Teams organizing multi-file notebook projects","Users who need lightweight file management without leaving the editor"],"limitations":["File system access is restricted to notebook resource directory only — no access to workspace-level file systems or external storage","No file upload/download UI documented — unclear how binary or large files are handled","No file preview or editing capabilities mentioned — resource files are managed but not edited in-place","File operations require active network connectivity to Fabric backend"],"requires":["VS Code for the Web (vscode.dev)","Active Fabric workspace with notebook resource directory","Write permissions to notebook resource file system","Network connectivity to Fabric storage backend"],"input_types":["file/folder names (strings)","file creation/deletion commands","folder hierarchy structure"],"output_types":["file system entries in notebook resource directory","confirmation of create/delete operations","updated resource tree view in sidebar"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-synapsevscode-vscode-synapse-remote__cap_3","uri":"capability://tool.use.integration.portal.to.editor.activation.flow","name":"portal-to-editor activation flow","description":"Implements a seamless activation flow where users can click an 'Open in VS Code (Web)' button in the Microsoft Fabric portal, which triggers the extension to activate and load the selected notebook into the VS Code Web editor. This flow handles authentication handoff from the portal to the extension, workspace context passing, and notebook initialization without requiring manual authentication or workspace selection in the extension.","intents":["Open a notebook from the Fabric portal directly in VS Code Web","Maintain authentication context when switching from portal to editor","Load the correct workspace and notebook without manual configuration","Seamlessly transition between portal and editor workflows"],"best_for":["Users who primarily work in the Fabric portal but want occasional editor access","Teams with mixed portal/editor workflows","Users who prefer not to manually configure workspace context"],"limitations":["Activation flow is one-directional (portal → editor) — no reverse flow documented","Requires the extension to be already installed in VS Code Web","Authentication context is inherited from portal session — if portal session expires, editor session may also expire","No documented fallback if activation fails or extension is not installed"],"requires":["VS Code for the Web (vscode.dev)","Fabric Data Engineering VS Code - Remote extension installed","Active Fabric portal session with authentication","Notebook accessible in current Fabric workspace"],"input_types":["portal button click (Open in VS Code Web)","notebook context from portal (workspace ID, notebook ID)"],"output_types":["notebook loaded in VS Code Web editor","authenticated session in extension","workspace context established"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-synapsevscode-vscode-synapse-remote__cap_4","uri":"capability://search.retrieval.workspace.scoped.notebook.discovery.and.navigation","name":"workspace-scoped notebook discovery and navigation","description":"Displays all notebooks in the current Fabric workspace as a hierarchical tree view in the VS Code sidebar, enabling users to browse, search, and navigate between notebooks without leaving the editor. The tree view is populated by querying the Fabric workspace API and is updated in real-time as notebooks are created or deleted. Users can click on any notebook in the tree to open it in the editor.","intents":["See all notebooks in my Fabric workspace at a glance","Navigate between notebooks without using the Fabric portal","Quickly find and open a specific notebook by name","Understand the structure and organization of notebooks in my workspace"],"best_for":["Data engineers managing multiple notebooks in a single workspace","Teams with large notebook collections","Users who want a unified view of workspace contents"],"limitations":["Notebook discovery is limited to the current workspace only — no cross-workspace browsing","No search or filtering UI documented — users must scroll through tree view to find notebooks","Tree view is read-only for discovery purposes — notebooks must be opened to edit","No sorting options documented — tree view order depends on Fabric backend ordering"],"requires":["VS Code for the Web (vscode.dev)","Active Fabric workspace with at least one notebook","Read permissions on workspace notebooks","Network connectivity to Fabric workspace API"],"input_types":["workspace context (inherited from authentication)","user click on notebook in tree view"],"output_types":["hierarchical tree view of notebooks","notebook metadata (name, last modified, etc.)","selected notebook loaded in editor"],"categories":["search-retrieval","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":39,"verified":false,"data_access_risk":"high","permissions":["VS Code for the Web (vscode.dev)","Active Microsoft Fabric workspace with appropriate permissions","Modern browser with WebSocket support","Authentication to Fabric workspace (inherited from VS Code Web session)","Active Fabric workspace with at least one configured kernel","Network connectivity to Fabric compute backend","Appropriate IAM permissions to execute against selected kernel","Active Fabric workspace with notebook resource directory","Write permissions to notebook resource file system","Network connectivity to Fabric storage backend"],"failure_modes":["Notebook operations are scoped to the current Fabric workspace only — no cross-workspace management","File system access is restricted to notebook resource files/folders, not general file system","Changes require active network connectivity to Fabric backend; no offline editing capability","Public Preview status means breaking changes possible in future releases","Specific available kernels are not documented — depends on Fabric workspace configuration","Debugging is explicitly NOT supported (stated as roadmap feature)","Kernel execution runs remotely on Fabric backend, not locally — no local execution option","No kernel configuration or customization UI exposed in the extension","File system access is restricted to notebook resource directory only — no access to workspace-level file systems or external storage","No file upload/download UI documented — unclear how binary or large files are handled","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.42,"quality":0.35,"ecosystem":0.35000000000000003,"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:34.803Z","last_scraped_at":"2026-05-03T15:20:36.253Z","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=fabric-data-engineering-vs-code-remote","compare_url":"https://unfragile.ai/compare?artifact=fabric-data-engineering-vs-code-remote"}},"signature":"7FB4ix1xyujIen3sKOD7VPNPEK0+qeIfeYN3qTn8XwHAan1cnhML+lj8fgcgVP1ye6G5m+Oq7ems0/HdCEVNDw==","signedAt":"2026-06-21T16:37:51.090Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/fabric-data-engineering-vs-code-remote","artifact":"https://unfragile.ai/fabric-data-engineering-vs-code-remote","verify":"https://unfragile.ai/api/v1/verify?slug=fabric-data-engineering-vs-code-remote","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"}}