How the Context Library works
Last updated:
The Context Library is a feature of Palette OS. It captures selected activity from company tools, combines it with team check-ins during context generation, and publishes scoped context pages for people and agents to read.
1. Connect company tools
Choose the organization-level tools and sources Palette can access. The current setup guides cover Slack, Jira, Linear, GitHub, and Notion. Access is limited to what your organization authorizes.
Google Calendar is a personal Connector Gateway connection, not an organization-level Context Library connection.
2. Palette captures relevant activity
Events from connected tools are ingested throughout the week and filtered by source. This stage stores relevant activity as source material. It does not yet combine several events into one conclusion.
Team check-ins can add the meaning or correction that tool activity does not contain.
3. Palette refreshes generated context
Once each week, Palette uses captured activity and check-ins to refresh context pages. This generation step is where activity from several sources can be synthesized into plain-English context.
Pages are scoped to the organization, team, or user. Generated fields can include a model-provided confidence value and source citations. Confidence is not a simple count of supporting events.
4. People and agents read permitted context
People can read context pages in Palette. In Palette Desktop, people can browse organizational context and mention a page in chat. MCP-compatible agents can search, list, and read the context available to the signed-in person through Palette MCP.
MCP provides the latest generated context on demand. It does not preload every page into every prompt, and it does not bypass Palette's access controls.
How the flow fits together
| Stage | What it does |
|---|---|
| Connected company tools | Supply selected activity |
| Team check-ins | Add human meaning and corrections |
| Capture pipeline | Filters and stores relevant source activity |
| Weekly generation | Synthesizes source material into scoped context pages |
| Palette Desktop and MCP | Let people and agents read permitted context |
Why Palette separates capture from access
Connecting each source directly to each AI tool gives that tool raw data one integration at a time. The Context Library separates source capture from reading. It composes selected activity into organization, team, and user context, then applies Palette's access controls whenever a person or agent reads it.
Next
Follow the Context Library quick start, read about the context scopes, or connect a supported agent through MCP.