Agents in Palette Desktop

Palette Desktop is agent-agnostic. Today that means Claude Code and Codex. Tomorrow, whatever comes next.

Claude Code or Codex

Pick your agent per chat. Inside a single session you can have one chat running Claude Code and another running Codex, both on the same folder at the same time.

This matters because:

• The leading model keeps changing. You don't want to bet your team's context on one vendor.
• Different agents are better at different things. Use the right one for the task.
• Your context lives in the folder, not in the agent. Switching agents doesn't cost you anything.

How agents learn about your workspace

Each agent reads a context file in your workspace to learn who you are, what the workspace is for, and how you work.

• Claude Code reads CLAUDE.md
• Codex reads AGENTS.md

Both files live in the root of your workspace folder. They serve the same purpose: tell the agent the things you'd otherwise have to repeat in every chat.

If you turn on the starting guide when creating a new folder, Palette writes the first version of these files for you. You can also edit them anytime, or ask a chat to update them as your workspace evolves.

Bring your own subscription

Palette Desktop runs your agent on top of your folder. You bring your own subscription:

• Claude Pro or Claude Code
• Codex / ChatGPT subscription

Your model usage runs through your own account, same as it would anywhere else. Palette doesn't gate model access and doesn't add a markup on tokens.

Teams tell us they actually use fewer tokens through Palette Desktop than through chat. Sessions and folder context cut a lot of the back-and-forth that chat tools require.