What problem does it solve?
It prevents frontend code from guessing paths and breaking permission rules by guiding authenticated, permission-aware access to app files and backend endpoints.
Core Features & Use Cases
- Frontend API surface via space.api: Read and write app files, manage folders (download URLs), call backend endpoints, and inspect Git history when enabled.
- Permission-aware discovery and access control: Find files via indexed, shard-scoped discovery (file_paths) instead of enumerating in-browser paths; restrict to writable areas when needed.
- Safe logical path and storage boundaries: Enforce correct logical app-rooted paths, block .git metadata, and keep browser storage non-authoritative while placing durable state in app files or explicit APIs.
Use it when a browser-based UI must load configuration or module metadata, search for matching assets by pattern, update user/group state in allowed layers, or trigger secure backend operations without violating determinism and signing boundaries.
Quick Start
Ask the assistant how to call space.api.fileList and space.api.fileRead to discover and load a permission-safe set of matching app files under L2 for the current user, then apply the recommended write approach (replace vs append/insert) when updating them.