Your first project
Point PandaOS at a folder so it works on your files instead of guessing.
You approve the changes
PandaOS proposes edits and waits for you, unless you widen Permissions.
Open one
- Press New Project.
- Pick how it starts. — Create a new folder, open one you already have, or clone from GitHub.
- Ask for something specific. — A real file, a real question.
What to ask first
For a codebase, ask it to explain the entry point, or to add a small feature and start the dev server so you can see the result. For documents or data, ask for a summary of the folder, or a deck built from your notes.
Then shape it
- Rules teach it your conventions, so it stays consistent between sessions.
- Connected apps let it query a database, trigger a deploy or pull in a document.
- Skills and agents package a repeatable job into one command.
None of this is needed on day one.
Getting started in a project
Once a project is open, ask for something specific to your files. The value becomes clear when PandaOS references real content rather than generating generic answers.
For a codebase, try asking PandaOS to explain the entry point and routing, or to add a feature and start the dev server so you can see the result. For documents or data, try asking it to summarize everything in the folder or create a presentation from your notes.
PandaOS reads the relevant files, proposes changes (which you approve unless you've adjusted Permissions), and shows you the result.