# Palette > Palette builds and maintains your company's shared context — so your team stays aligned and your AI tools have the context they need. Palette connects to your tools (Slack, Jira, Linear, GitHub, Notion, Google Calendar), talks to your people, and builds a living context map of how your org works: a structured, plain-English representation of how your organization actually operates. Connect your AI tools like ChatGPT and Claude via MCP to get live organizational context. ## Pages - [Homepage](https://palette.team/): Product overview, value proposition, and how Palette works. - [Design Partner Program](https://palette.team/design-partner): Apply for early access to help shape Palette's development. - [Sign Up](https://palette.team/sign-up): Get early access to Palette — shared context for your team and AI. - [GTM OS Starter Pack](https://palette.team/gtm-os): A ready-to-use folder setup that turns Claude Code into your GTM co-pilot. - [Windows Waitlist](https://palette.team/windows-waitlist): Join the waitlist for Palette Desktop on Windows. ## Blog - [Blog](https://palette.team/blog): Sharing our journey on building Palette — shared context for teams and AI. - [Why We're Building Palette](https://palette.team/blog/hello-world): A short introduction to Palette — a shared context layer for your team and your AI, built by a team of six in Copenhagen. - [Launching Palette Desktop](https://palette.team/blog/launching-palette-desktop): Palette Desktop is here — a desktop app for running Claude Code and Codex on shared team folders. For the parts of the company that aren't engineering. ## Changelog - [Changelog](https://palette.team/changelog): Latest updates, improvements, and fixes to Palette. - [Palette Desktop 0.21.0](https://palette.team/changelog/palette-desktop-0-21-0): First update since launch — a new Mistral Vibe provider, hands-on file management in the Files area, Palette account sign-in, and a stack of workspace polish. - [Palette Desktop 0.1.0](https://palette.team/changelog/palette-desktop): Palette Desktop launches — run Claude Code and Codex on shared team folders, with sessions, agent choice, templates, and Palette context built in. - [Briefs](https://palette.team/changelog/briefs): The morning brief your chief of staff would write — TLDR, what needs attention, and today's calendar, delivered to your team's Slack. - [Palette v1.0](https://palette.team/changelog/initial-launch): The first release of the Palette context layer — connect your tools, build a living context map of your org, and serve it to your AI tools via MCP. ## Documentation — About Palette - [Welcome to Palette](https://palette.team/docs/welcome-to-palette): Shared context and workspaces for AI-native teams. Two products that work together: Palette Desktop and the Palette context layer. - [Company](https://palette.team/docs/about-palette): Based in Copenhagen, Denmark. Four co-founders, backed by Emblem and Arcadian. Team, principles, and contact. - [Vision & Manifesto](https://palette.team/docs/palette-manifesto-why-context-is-infrastructure): Why knowledge work is changing, why the individual is now faster than the organization, and why AI-native companies need a maintained context layer. - [FAQ](https://palette.team/docs/frequently-asked-questions): Cross-product FAQ. What Palette makes, how the two products fit together, who it's for, security, design partner program. ## Documentation — Palette Desktop - [Palette Desktop](https://palette.team/docs/palette-desktop-overview): A desktop app for running Claude Code and Codex on the folders your team shares. What it is, who it's for. - [Quick Start](https://palette.team/docs/palette-desktop-quickstart): Download, point at a folder, run your first session, review and save back. A few clicks from install to first session. - [Workspaces](https://palette.team/docs/palette-desktop-workspaces): A workspace is a folder on your computer. What the agent reads and writes, why folders. - [Sharing workspaces](https://palette.team/docs/palette-desktop-sharing-workspaces): Put a workspace on Google Drive, Dropbox, or iCloud. Everyone on your team points their app at the same folder. - [Sessions](https://palette.team/docs/palette-desktop-sessions): A sandboxed clone of your workspace. The agent works in the clone; you review every change before it saves back. - [Chats](https://palette.team/docs/palette-desktop-chats): One conversation with an agent inside a session. Multiple chats per session, different agents per chat, @-references. - [Plan mode](https://palette.team/docs/palette-desktop-plan-mode): The agent maps out what it's going to do before doing it, so you review the approach before any work starts. - [Agents](https://palette.team/docs/palette-desktop-agents): Claude Code and Codex. Pick per chat, bring your own subscription, stay agnostic across vendors. - [Actions](https://palette.team/docs/palette-desktop-actions): The actions list: every skill and command in your workspace, surfaced in one place, shared with your team. - [Shortcuts](https://palette.team/docs/palette-desktop-shortcuts): Pin files, actions, and custom prompts. Your most-used things, one click away from any chat. - [References](https://palette.team/docs/palette-desktop-references): Point a chat at folders outside the workspace. Read-only context from anywhere on your machine. - [Templates](https://palette.team/docs/palette-desktop-templates): Premade folder structures for common teams. gtm-os, startup-os, ops-os. - [Context layer (in Desktop)](https://palette.team/docs/palette-desktop-context-layer): The Palette context layer is built into Palette Desktop. Live organizational context on top of your workspace. - [Working with CLAUDE.md and AGENTS.md](https://palette.team/docs/palette-desktop-working-with-claude-md): The file your agent reads first. What to put in it, how to keep it sharp, how to share with your team. - [Working with HTML files](https://palette.team/docs/palette-desktop-working-with-html-files): When to ask the agent for HTML, previewing inside Palette Desktop, sharing artifacts with humans. - [Palette Desktop FAQ](https://palette.team/docs/palette-desktop-faq): How Desktop differs from Cowork, where data lives, agent support, and how teams collaborate on the same folder. ## Documentation — Context layer - [Palette context layer](https://palette.team/docs/welcome-to-palette-shared-context-for-teams-and-ai): A living map of your organization that your AI tools can read. The problem it solves, who it's for, how it works. - [Quick Start](https://palette.team/docs/quick-start-guide-set-up-palette): Connect tools, let the context layer build, install Palette MCP in your AI tools. - [How the context layer works](https://palette.team/docs/how-palette-works-connected-tools-to-living-context): Full flow: connect tools, interpret events via the signal engine, build a living context map, serve it via MCP. - [Context map](https://palette.team/docs/context-living-map-of-your-organization): Organization, team, and person scopes. Confidence-scored, always current, readable by humans and AI. - [Signal engine](https://palette.team/docs/signal-engine-how-palette-turns-events-into-context): Ingests events from Slack, Jira, Linear, GitHub, Notion, and Calendar, then interprets them into confidence-scored context. - [MCP](https://palette.team/docs/mcp-connect-palette-to-claude-chatgpt-ai-tools): Palette connects your organization's living context to Claude, ChatGPT, and other AI tools via the Model Context Protocol. - [Context to your AI](https://palette.team/docs/palette-mcp-live-context-for-ai-tools): Give Claude and other AI tools live access to your org context via Palette MCP. Interactive prompt examples for you, your team, and across teams. - [Context to your workflows](https://palette.team/docs/optimise-your-workflows-with-palette): Build Claude workflows and skills that use your Palette MCP context. Ground every automation in what's actually happening across your org. - [Slack](https://palette.team/docs/slack-integration): What Palette reads from Slack, what it can do, and what you control. - [Jira](https://palette.team/docs/jira-integration): What Palette reads from Jira Cloud, what it can do, and what you control. - [Linear](https://palette.team/docs/linear-integration): What Palette reads from Linear, what it can do, and what you control. - [GitHub](https://palette.team/docs/github-integration): What Palette reads from GitHub, what it can do, and what you control. - [Notion](https://palette.team/docs/notion-integration): What Palette reads from Notion, what it can do, and what you control. - [Google Calendar](https://palette.team/docs/google-calendar-integration): What Palette reads from Google Calendar and what you control. - [Connect to Claude](https://palette.team/docs/connect-palette-to-claude): Set up Palette MCP with Claude for chat and code. - [Connect to ChatGPT](https://palette.team/docs/connect-palette-to-chatgpt): Bring Palette org context into ChatGPT via Projects (manual upload). - [Connect other tools](https://palette.team/docs/connect-palette-to-cursor-conductor-mcp-tools): Connect Palette to Cursor, Conductor, or any MCP-compatible tool. - [Palette context layer FAQ](https://palette.team/docs/palette-context-layer-faq): How the context layer works, how it stays accurate, how it differs from wikis and dashboards. ## Legal - [Terms of Service](https://palette.team/terms): Terms governing use of the Palette website and services. - [Privacy Policy](https://palette.team/privacy): How Palette collects, uses, and protects personal information. - [Cookie Policy](https://palette.team/cookies): How Palette uses cookies and how to control them.