Local Project Boundaries
Sparky works inside the project folder you select. Keep separate clients, apps, or sensitive work in separate project folders so context and generated artifacts stay organized.
Security
Built for local-first Windows workflows.
Sparky should be understandable before it is trusted. This page explains how authentication, billing state, local project access, and browser automation are designed.
Authentication
The website is prepared for Clerk authentication. A signed-in user id can be stored with plan records so checkout can activate the right plan type.
Plan Enforcement
The app server tracks plan state, usage counters, and limits. Plan flags such as type-pro-true allow the desktop app to lock or unlock plan-gated features.
Browser Automation
Browser control is explicit and visible in the app. Use it for testing, screenshots, and web QA. Avoid granting access to private accounts unless the task requires it.
Data Storage
Local app state is written under the workspace .nexus folder. Convex tables are available for users, subscriptions, and usage counters when cloud sync is enabled.
Responsible Use
Review generated files before sharing them. Keep API keys and private credentials out of prompts unless your provider configuration and policies allow it.