Workspace · SettingsPublic pagesNo need to expose operational preferences. Workspace settingsKeeps execution preferences close to the runtime. Low riskNo deep runtime rewrite required.
Runtime controls now live behind a dedicated route.
This keeps operational settings reachable without crowding the main execution lanes.
Operations
Settings are part of the workspace, not part of public acquisition.
Give controls a stable route so they do not compete with public task pages for space and copy.
Capability boundary
Settings stay local to the browser. TXT is the everyday export format and JSON remains the backup format.
- Defaults mirror into the last-used-settings key for recovery.
- Do not imply server-side accounts or cloud sync for these controls.
- Saved playlists and settings must remain readable after import/export cycles.
Mobile execution
On narrow screens, keep the current task visible first and collapse helper rails into secondary controls.
- Player and inspector remain primary mobile modes.
- Queue, history, and settings should stay reachable without dominating the first screen.
- Avoid introducing extra fixed panels that cover inputs or results.
Storage contract
Saved playlists stay in Local Storage. TXT is the everyday import/export format and JSON remains the backup format.
- Playlist keys: m3u8-playlists, m3u8-recent-playlists.
- Settings key: m3u8-last-used-settings.
- Import TXT for routine work; use JSON only for backup and restore.
Execution surface
Settings runtime
The current settings runtime is mounted below.
M3U8 Toolkit
Loading workspace lane…
Low-interference sponsor slotView ad policy
Sponsor cards stay after the execution surface instead of cutting across the main input or primary action.
Slot IDad-ws-sponsor-primary-workspace-settings
Placementsponsor-card
Modeself-promo
Densitylight