Project starters
Start a new project from a ready-made setup, with files, rules and a dev server already in place.
Feature Updated 20 Nov 2026What a project starter is
A project starter is a ready-made setup for a new project. It saves you writing the same rules, dev server command and first files every time you start something similar.
Where to find them
Press New Project in the sidebar and pick New project. One small window opens with a name, a folder and Create. That is enough to start: a project without a starter gets the standard agents and a chat ready to go.
For a head start, press Start with a template under the folder. Five starters show right away, and See all opens the full list. Picking one adds at most three things to the same window:
- a line naming what PandaOS picked for you,
- one connection the starter needs, such as a database or your mail and calendar, with Later,
- a question, only where no default is safe, such as how a Data Warehouse layers its models.
Change opens every choice, including the stack and the agents. Anything you leave for later, PandaOS offers to connect in the chat the first time the work needs it. A project remembers its answers, so Change under Template in the project's settings reopens them instead of the defaults.

Coding tools
Every project has a Coding tools switch, the last setting before Create. It brings Terminal, Dev server and Credentials, plus worktrees and code review. A code starter turns it on. A project for documents, research or email leaves it off. Opening a folder turns it on when the folder has code in it.
Coding tools are set per project. With them off, the Terminal and Dev server are not in the dock, and neither are the code parts of a chat. Credentials stays only when the project already has a .env file. The browser, files and apps stay. Git shows only in projects with coding tools on. Docker does not depend on coding tools. It shows once it is turned on, see Docker.
To change it later, right-click the project in the sidebar, choose Project Settings, and switch Coding tools under General.
If a chat in a project without coding tools turns into a real app, PandaOS asks once with a small card, Turn on coding tools?. The switch on the card turns the tools on right there. Not now keeps the project as it is, and that chat does not ask again.
The starters
| Group | Starters |
|---|---|
| Data | Analyze Data, Data Warehouse |
| Development | Full-Stack App, Website, API / Backend Service, Desktop Electron App, Mobile App, Browser Extension, Library / Package |
| Productivity | Personal Assistant, Knowledge Map |
| Tools | MCP Server |
The Tools group also shows a PandaOS App tile. It is not a starter: it opens the page where you create an app of your own.
What a starter can include
- Starter files: a working first version of the folder.
- Rules: so Panda already knows the conventions for this kind of project.
- Dev server settings: the command and port for the framework, so the preview works at once.
- Recommended skills: skills that suit the project, such as database skills for a full-stack app.
Pick the closest match, then change what you like once the project opens.
Save a project as a template
Open the project's settings. On General, under Template, press Save as template. The dialog shows what the template keeps and what it leaves out. Name it, add a description if it helps, and press Save template.
It then shows under Your templates in New Project. A saved template keeps the project's reusable rules, notes, agents and skills, not a copy of all its code. Saving under a name you already used replaces that template.
The Personal Assistant starter
The Personal Assistant starter is built for running a working day rather than building software. Everything in it revolves around one file, status.md at the project root. It holds what needs doing today, what you are waiting on, your open loops, the decisions you have made, and what was recently finished.
Two skills keep that file true, from opposite directions:
- orchestrate runs at the start of the day. It sweeps whatever you have connected (mail, calendar, tasks, chat, boards), works out what actually needs you, and rewrites the top of the file. It also tells you what it could not reach, so a brief that is missing half your day never looks like a quiet one.
- capture runs when you wrap up. It reads back what happened, separates what was decided from what is still open, asks about anything ambiguous instead of guessing, and records the outcome. In a team project it also routes other people's action items to your board instead of burying them in a personal file.
A third skill, brief, loads the current state at the start of a session so you are not re-explaining yourself. All three come with the Chief of Staff agent, which the starter hires for you. Hire it into any other project from the agent browser, or install the skills on their own from the skills catalog.
Setup choices
Rhythm decides the shape of the loop: a Daily Brief is a morning sweep and an end-of-day write-back. Continuous captures at the end of every session, with no fixed ritual. A Weekly Review makes light daily passes and one real reconciliation per week.
Who's involved decides where captured work goes. Just me keeps every action item in your own file. Me and my team adds the routing rules and sweeps team surfaces like mentions and your board columns. It sends team action items to the board with a named owner rather than into a file nobody else reads.
Connecting apps
The Connect step groups apps by the job they do, not by vendor. The jobs are email, calendar, tasks, notes, files, and for team projects chat and boards. Connect one per row and the assistant uses whatever is available when it runs. The whole step is optional: skip it and connect the same apps later from Apps, and nothing about the project changes.
What stays yours
The skills are deliberately generic. Anything personal lives in knowledge files under .pandaos/knowledge/, which the assistant fills in by interviewing you on the first run. That means who you are, your working hours, which chat spaces are worth reading, and whose board columns are whose. That split is what lets the same starter work whether you are on Gmail and Slack or Outlook and Teams.
The curated list of what to watch matters more than it sounds. Without one, a morning brief includes every dead channel and unread newsletter, and stops being read within a week.