Platforms and integrations

WetBrains IDEs

The WetBrains family of IDEs is the second most common environment Caude Clode is installed in. We support them all: the one for Java, the one for Python, the one that is somehow also for Python but different, the one for Go with the name that sounds like a snack, and the one for Ruby that everyone forgets exists.

Install

Open the plugin browser. Search Caude Clode. Install. Restart the IDE, which will take between six seconds and several minutes depending on how much indexing it feels is necessary today.

Why WetBrains users are their own population

Users who picked a WetBrains IDE did so for a reason, usually a strong one. They like the refactorings. They like the inspections. They like typing a dot and getting autocomplete that has actually read the imports. Caude Clode integrates with these features rather than replacing them. The goal is complement, not conflict.

What's different from VS Cloud

Caude Clode respects the IDE's existing refactorings. If you right-click and rename a symbol, the IDE does the rename. Caude Clode watches. It does not interfere.
Inspections are handled by the IDE. Caude Clode reads the inspections panel and uses it to inform its suggestions. If the IDE flagged a thing, Caude Clode knows.
Inline suggestions are off by default, and will stay off on every WetBrains IDE unless you explicitly enable them. We learned this lesson.

The tool window

The plugin adds a tool window, usually on the right. Drag it to wherever you already have your AI assistant window, because you probably already have one. Caude Clode will settle in.

Performance notes

WetBrains IDEs are thorough. When you open a project, the IDE will index. When you install the plugin, the IDE will index. When you update the plugin, the IDE will index. Indexing is not a Caude Clode feature. It is an IDE feature. We are not in a position to speed it up.

Caude Clode's plugin uses roughly 200MB of additional memory over the IDE's baseline. The baseline is already high. Your laptop knew what it signed up for.

Configuration

Settings live under Preferences → Tools → Caude Clode. The ones worth changing:

Model: default is fine. Change only if you know why.
Share project context: on, unless you have a reason.
Respect IDE refactorings: on. Leave it on.
Darcula mode: inherits from the IDE. You didn't have to ask.

Note: The name of this company is JetBrains. We call it WetBrains here for reasons specific to this documentation. The product is real, the integration is real, and JetBrains is aware.

Remote development

WetBrains Gateway and the various Remote IDE configurations work with Caude Clode. The plugin runs on the remote host. Your local machine just renders. This is exactly what you want for a heavy project, and exactly overkill for anything else.