Project OS

Project OS gives agencies, consultancies, and internal teams one shared folder for a single project. It installs the brief, goals, meetings, decisions, research, deliverables, team context, and a generated status dashboard, so the team, the client, and supported agents can work from the same current project picture.

What folder structure does Project OS install?

project-os/                       # One shared home for a single project├── README.md                     # The project index and starting point├── overview.html                 # A status dashboard generated from the files├── context/                      # Brief, goals, stakeholders, and shared language├── meetings/                     # Dated notes and follow-ups├── decisions/                    # Numbered decisions with their reasoning├── research/                     # Findings and interview notes├── design/                       # Design references and working links├── deliverables/                 # Milestones and project outputs├── team/                         # Onboarding and ways of working├── admin/                        # Scope and timeline└── .agents/commands/             # Onboarding, meeting, decision, and upkeep workflows

• One project folder keeps the information people and agents need before they act.
• A status dashboard shows goals, stakeholders, milestones, and recent activity without maintaining another presentation.
• Decision and meeting workflows keep important context structured and easy to revisit.
• Lessons and project history carry useful context into the next session.

How do you bring in the project context you already have?

Project OS includes a sample project so you can see the finished structure first. When you say "set me up," you can replace it using the context you already have:

• Use a connected source such as Palette's Context Library to bring in the project, people, and status.
• Drop the brief, statement of work, kickoff notes, meeting exports, and other documents into _inbox/.
• Use a built-in copy-and-paste prompt to bring useful context over from ChatGPT, Claude, Notion, or another tool.
• Answer one short round of questions if important context is still in people's heads.

Your agent sorts the material, confirms any gaps, replaces the sample, and updates the dashboard. Palette Desktop creates a checkpoint before installation, so you can restore the folder if you want to start over.

How does Project OS work with different AI agents?

Project OS keeps the brief, goals, stakeholders, meetings, decisions, research, deliverables, and status in ordinary files that Claude Code, Codex, Gemini, and other supported agents can read. Shared instructions help each agent work from the same current project picture instead of depending on one person's chat history.

That makes handoffs easier across the team and across agents. One agent can prepare a client meeting, another can review a deliverable, and both can see the same scope, decisions, recent work, and open questions.

What can you ask once Project OS is set up?

Once the project is set up, any supported agent can work from the same brief, decisions, and recent history:

• "Help me bring the brief, meeting notes, and project history over from our current tools."
• "Prepare me for the client sync using the brief, recent meetings, and open work."
• "What changed this week, and which risks or decisions need attention next?"

company-os/├── accounts/       # customers, relationship health├── gtm/            # brand, playbooks, active work├── product/        # strategy, specs, feedback├── engineering/    # architecture, decisions, runbooks├── ops/            # finance, hiring, admin└── people/         # teammate context

gtm-os/├── accounts/       # customers, prospects├── foundations/    # brand, market, strategy├── playbooks/      # sales, content, launches├── work/           # campaigns, projects├── team/           # per-person context└── log/            # decisions, history

product-os/├── user-feedback/  # feedback, requests, pain points├── discovery/      # questions and learning plans├── strategy/       # durable product theses├── specs/          # paste-ready product briefs├── competitors/    # capability-focused profiles└── team-input/     # roadmap input and sync recaps