First run

Select the folder button beside Projects in the left sidebar and choose a local folder. NativePi pins the folder so it is available the next time you open the app. You can also drop a folder anywhere in the window.

Pi asks for trust when a project contains local code or instructions, including extensions or skills. Trusting the folder allows those resources to load with your system permissions. Review the project before approving it.

Open Settings, choose a provider, and complete its authentication flow. Pi performs authentication and writes credentials to its own auth.json. NativePi does not copy credentials into renderer storage.

If you already use the Pi command line, your existing authentication is available immediately.

Create a chat, choose a model and thinking level beneath the composer, then send a prompt. You can change the model or thinking level later, including while a turn is running.

Paste or drop an image into the composer to attach it. Drop another file to insert an @ path mention instead.

• Read NativePi and Pi to understand the ownership boundary.
• Read Sessions and storage before moving conversations between NativePi and the Pi CLI.
• Read Packages and extensions to add Pi capabilities.