Providers
Agents in Appenda run through an external coding assistant you already use: Claude Code, Codex, or Cursor. Appenda keeps the chat beside your table and passes table context to whichever runtime you pick.
Each chat tab is tied to one provider runtime: Claude Code, Codex, or Cursor.
Supported providers
| Provider | Best for |
|---|---|
| Claude Code | Anthropic subscription or Claude account |
| Codex | OpenAI Codex access |
| Cursor | Cursor subscription |
You choose the provider when you start a new chat tab. Each tab sticks with that runtime for its whole thread.
How it works
- Open Agents from the title bar.
- Click + on the tab bar and pick Claude Code, Codex, or Cursor.
- Send a prompt. The agent can read and, when allowed, change the open table.
- Complete sign-in if the provider asks for it.
Appenda bundles supported runtimes with the desktop app. You do not install a separate agent binary or point Appenda at a custom path.
Each tab keeps its own transcript and connection. Switching tables does not start a new provider; starting a new tab does.
Workspace policy
Workspace admins control which providers members may use under Settings → Agents → Allowed providers. If a provider is missing from +, your admin may have turned it off for the workspace.
Sign-in is separate
Picking a provider starts the runtime. Sign-in covers provider login and Appenda account access when either side needs it.
Related
- Agents
- Sign-in
- Chat modes
- Approvals
- Connect with MCP if you use an external client instead of the in-app panel