Your First Project
Point PandaOS at a folder to give it full context over your files, code, and local environment.
What a project is
A project in PandaOS is a folder on your machine that you want the AI to understand and work within. It can be a codebase, a client folder, a collection of research documents, or any directory of files you actively work on.
When you open a project, PandaOS gains direct access to its contents: it can read files, understand structure, make edits, and, for code projects, detect the framework and suggest how to run a dev server. This is the foundation of how you work in PandaOS - every conversation happens within the context of a project.
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.
What projects unlock
With a project open, you can start shaping how PandaOS works within that specific context:
- Rules define conventions and preferences PandaOS should follow, like coding style, naming patterns, or formatting requirements. Rules make PandaOS consistent across sessions.
- Connected apps like Supabase, Vercel, or Google Drive extend what PandaOS can do inside your project: query databases, trigger deployments, or pull in reference documents.
- Skills and Agents let you package repeatable workflows so common tasks run with a single command instead of a long prompt.
You don't need to set up any of these immediately. Start by working in a project, and add structure as you find yourself repeating instructions or wishing PandaOS knew something it doesn't.