Proxied Space

A Proxied Space is a focused workspace for third-party web apps. It is not the global desktop layout engine and it is not a browser extension. The full management implementation is a productized app at /app-spaces/home that helps a user search, add, preview, and manage Proxied Apps inside one Space. The /app-spaces root can remain a folder/root route, but it should normalize to the home app instead of carrying the complex implementation itself.

What It Contains

The /app-spaces/home app currently includes:

• Space header, search, URL input, and command bar.
• Space template list for AI Research, Founder Ops, Dev Tools, Social Inbox, and Creator workflows.
• App icon rail for the selected Space.
• Proxied App cards backed by curated seed data.
• iframe preview when embedding is recommended.
• External fallback preview when site policy blocks embedding.
• Compatibility badges.
• App Settings modal.
• App Submission modal.
• Install destination menu.
• Quota preview for Free, Pro, and Lifetime packaging.

/app-spaces/slidepad is the quick corner panel version of the same web-app space direction. It focuses on a small icon rail, selected app preview, and fast entry to the full Spaces home app.

How It Differs From A Folder

A folder is desktop organization for shortcuts. A Proxied Space is a workspace object direction: it can group third-party web apps, launch rules, compatibility status, default URLs, install destinations, and future review/submission state.

The current version is mock/local. It does not persist real installations, perform metadata crawling, or sync backend state.

Browser Limitations

Browser-only Próx OS cannot guarantee that every website can run inside an iframe. Many sites intentionally set X-Frame-Options or CSP frame-ancestors headers to block embedding. Authenticated apps may also require their own top-level browsing context.

The browser shell can supervise links that it renders. Cooperative apps can use the shell open-link API. Cross-origin iframe internals are different: the shell cannot fully intercept every click the way a native desktop WebView might.

Early handling is limited to iframe navigation observation, sandbox policy, external fallback, right-click/open menu support, and explicit user actions.

Future Client Enhancements

Future clients may extend this model:

• PWA: better installability and offline shell affordances.
• Browser extension helper: improved link capture and metadata submission with user permission.
• Tauri/Electron desktop client: possible profile/cookie isolation research, system-level link interception, global shortcuts, tray integration, and local indexing.

Cookie/profile isolation and desktop-level global link interception are desktop-client investigations only. They are not promised in the browser shell.