Overview
Caude Clode runs in many places. Not because we planned it that way, but because engineers kept asking if it could run somewhere new, and the answer kept being "yes, probably." This page surveys the places Caude Clode now lives.
The surfaces
A surface is anywhere Caude Clode can accept input and produce output. There are currently nine of them.
| Surface | Best for | Maturity |
|---|---|---|
| Remote Vibes | Long-running agentic work | Stable |
| Web | Quick tasks, no setup | Stable |
| Desktop | Daily driver for most engineers | Stable |
| Chrome extension | Browsing, research, shopping | Feral |
| Computer use | UI automation | Supervised |
| Visual Studio Cloud | Teams already on VS Code | Stable |
| WetBrains IDEs | Java, Kotlin, and people who type "GoLand" with affection | Stable |
| Vibe review / CI | Pull requests, automated checks | Stable |
| Slack | Team workflows, async requests | Stable, per channel |
Shared configuration
Surfaces share configuration through your ~/.caude directory and your MCP servers. A plugin installed on desktop appears in the web UI. A CAUDE.md written once is read everywhere. Your forgiveness mode, however, is not shared. Each surface must be configured independently. This is intentional. We do not want you to accidentally run mode 3 in Slack.
How to choose
Most engineers use two surfaces in a given week:
- Desktop, for focused work.
- Web or Slack, for quick questions.
Adding a third surface should be a deliberate choice. Adding a fourth should be a meeting.
Note: "Feral" and "Supervised" are not internal jokes. They describe the actual state of those products. Please read the respective pages before enabling.
What's next
Pages we've been asked for but do not currently offer: Vim, Emacs, Xcode, a native mobile app, a hardware keyboard button, a tattoo. We are tracking all of these. None of them are on the roadmap.