Browser and desktop use the same main project/file models, but local-machine access, MCP, sync review, window behavior, and export availability differ.
Capability: Project/file editing · Browser: available for supported account/project · Desktop: available, including local project runtime
Capability: Dashboard from Project menu · Browser: navigates web application · Desktop: opens Dashboard as a separate app window
Capability: Runtime Preview · Browser: available through browser route/window behavior · Desktop: available through app host/window behavior
Capability: Preview in Tab context action · Browser: available · Desktop: window behavior differs
Capability: Production MCP endpoint · Browser: unavailable from website alone · Desktop: packaged app serves local Streamable HTTP endpoint
Capability: Local-folder export · Browser: unavailable · Desktop: available to existing local directories
Capability: Sync Changes / Push Changes menu · Browser: not shown in current Project top bar · Desktop: shown; opens review/confirmation flows
Capability: Git export · Browser: handled through configured web/server or desktop route · Desktop: available through desktop/server path
Capability: File uploads/clipboard/native dialogs · Browser: browser permissions and sandbox apply · Desktop: desktop/native integration applies
Capability: Activity marks for local MCP work · Browser: no website MCP endpoint · Desktop: available when editor tracking is enabled
Open tabs, history, selection, expanded rows, Preview window state, and panel sizes belong to the current editor session. Opening the same project in another environment does not imply identical UI state.
Persisted file rows and synchronized project operations can be shared, subject to access and sync status. Always review incoming/outgoing changes before assuming the two sessions are current.
a production MCP connection;
local-folder output;
the desktop Sync Changes/Push review workflow;
host-assisted MCP screenshots, interaction, PDF/video, or related app operations;
native file/blob workflows that the browser cannot access equivalently.
Choose browser when normal web access and editing are sufficient and no local-machine integration is required.
Desktop MCP has no separate current auth token; connect trusted local clients and do not publish the port. Local export can overwrite generated destinations. Browser and desktop remote actions still require account permissions and destination-specific verification.