---
title: "Supported coding agents"
description: "Cadence works with any major AI coding agent by reading the session logs they already write locally."
url: "https://teamcadence.ai/docs/integrations/agents/"
---
## How support works

Cadence doesn't require your coding agent to integrate with it. Each agent already writes its own local session/transcript log as you work - Cadence's desktop daemon knows where to look for each supported agent, reads those logs, and uploads sessions from repos you've enabled. See [Overview & tray](/docs/desktop/overview/) for how the background scan works.

This means adding support for a new agent is a matter of teaching Cadence where that agent stores its logs, not asking every agent vendor to build a Cadence integration.

## Supported today

- Claude Code
- Codex
- Cursor
- GitHub Copilot
- Cline
- OpenCode
- Kiro
- Amp Code
- Antigravity
- Windsurf
- Pi

If you use one of these, there's nothing to configure beyond normal [onboarding](/docs/installation/) - Cadence finds sessions automatically once a repo is enabled.

## Using more than one agent

Nothing about Cadence assumes a single agent. Switch between agents freely, or use different ones for different repos - sessions are tagged with which agent produced them, and the CLI's `--agent` filter (see [`session list`](/docs/cli/commands/)) lets you slice your own history by agent.

## Don't see your agent?

Agent support is an evolving list. If yours isn't covered yet, reach out - new agents get added by extending log discovery, not by waiting on the agent vendor.