FAQ

A native Mac workspace for Claude Code and Codex: run up to six live sessions, choose the provider and model per task, search both histories, and switch providers without losing the visible working thread.

Install and sign in to the provider you want to use. Claude sessions run through your local claude binary. Codex sessions connect through the local Codex app-server and use the ChatGPT/Codex account already managed there.

No Atelier API key. Claude uses the authentication or subscription already configured in Claude Code. Codex uses the account and ChatGPT/Codex subscription already configured in Codex. Provider charges and usage limits still follow those plans.

Atelier's workspace state, files and history integrations stay on your Mac. Prompts reach Claude or OpenAI through their installed local tools—there is no Atelier account or Atelier cloud proxy in the middle.

Atelier carries a bounded, provider-neutral checkpoint of the visible work into the new provider and retains both native sessions, drafts and histories. Hidden reasoning, credentials, OAuth sessions and provider-specific caches never cross the boundary.

Atelier shows each provider's real MCP inventory. Compatible project servers can be imported explicitly, but Claude and Codex continue to own their own configuration, credentials and OAuth sessions. Atelier never copies one provider's tokens into the other.

Yes. Shared chat, attachments, history and handoff work across Claude and Codex. Atelier's deeper agents, loops, harnesses, hooks, skills and plugin controls continue to expose Claude Code's native feature surface in the same workspace.

macOS first. Windows and Linux builds are on the bench - they're coming.

Yes - free while in active development, with no account and no license keys. See pricing.

Atelier checks for new builds and updates in place. Every release is listed on the changelog.