Your work
Supported ChatGPT projects, Codex work, captures, files, and repositories.
How the workspace works
The layers stay separate so the surface remains simple, permissions remain visible, and changing a model never changes who is allowed to build.
Supported ChatGPT projects, Codex work, captures, files, and repositories.
Organizes memory, project state, copy routes, and portable Zeke Cards.
Optional analysis through an enabled, properly authorized model.
Builds in repositories with tools, approvals, checks, and receipts.
Connection state
Supported continuity
Use ChatGPT’s native import when available. CodexPanels never scrapes a private sidebar or asks for another provider’s password.
Open the official import guideChoose the available import option.
Choose setup, projects, and recent items.
Workspace Doctor shows anything still disconnected.
Permission boundaries
Consumer subscription ≠ API access. CodexPanels uses managed access, scoped credentials, enterprise federation, or provider-supported OAuth—not consumer passwords.
Secrets remain managed, server-side, or local.
Available models come from the enabled Gateway catalog.
Workspace owners control access, budgets, and routing.
The builder contract
[model_providers.vercel] name = "Vercel AI Gateway" base_url = "https://ai-gateway.vercel.sh/v1" env_key = "AI_GATEWAY_API_KEY" wire_api = "responses" [profiles.vercel] model_provider = "vercel" model = "<choose-from-live-catalog>"
The environment supplies the key. It never belongs in a panel manifest or pasted chat.
Product boundary
Visual workspaces, AI chats, repositories, Zeke Cards, Codex building, and workflow commerce.
Audiovisual creation, 3D, worlds, devices, local compute, and broader distributed work.