Has anyone gotten Cline to work well with JetBrains IDEs?

I've been attempting to integrate Cline into my daily development workflow, which heavily relies on JetBrains IDEs (specifically IntelliJ IDEA and PyCharm), for the past few weeks. My primary interest stems from wanting to audit and log AI-assisted code generation for internal compliance reviews, but I've hit several roadblocks that make me wonder if the integration is truly production-ready for our use case.

From an audit-logging perspective, the integration feels somewhat shallow. While the plugin installs without issue, I've encountered several consistent pain points:

* **Context Limitation:** The plugin seems to operate with a very limited view of the project context compared to the VS Code extension. For instance, when asking Cline to generate a function based on existing patterns in other files, it often seems unaware of those patterns unless the files are explicitly opened. This defeats the purpose of having a deep IDE integration.
* **Configuration Drift:** The settings between the standalone Cline application and the JetBrains plugin don't always appear synchronized. I've had to manually ensure API endpoints and model configurations match, which is a compliance red flag for a controlled environment.
* **Lack of Detailed Logs:** This is my biggest concern. The JetBrains plugin provides minimal operational logging of its own. While I can see network calls in my system-level audit trails (like those collected by Splunk or Datadog agents), the *intent* behind a code generation request and the *full context* sent to the LLM is not captured in a structured way within the IDE's own logs. This creates a gap in the audit trail.

My current configuration involves the following, which seems to be the most stable setup I've achieved so far:

```json
// In Cline Desktop app config (approximate structure)
{
"cline": {
"backend": "local",
"model": "claude-3-5-sonnet",
"jetbrains": {
"enabled": true,
"server_url": "http://localhost:3000"
}
}
}
```

And then ensuring the JetBrains plugin points to the same local server URL. Despite this, I still experience intermittent disconnections where the plugin loses its connection to the Cline backend service, requiring a restart of the IDE or the Cline app.

My core questions for the community are:

* Has anyone successfully established a stable, persistent connection between a JetBrains IDE and Cline, particularly on macOS?
* More importantly from an audit perspective, has anyone found a method to capture richer logs from the JetBrains plugin itself? I'm looking for logs that detail the specific code snippets sent as context, the exact prompts used, and the reasoning behind the AI's suggestions—essentially a full SOX-relevant audit trail of the AI's interaction with the codebase.
* Are there any known conflicts with other common JetBrains plugins that might affect Cline's ability to index the project context properly?

I am particularly interested in any workarounds or external logging wrappers you might have implemented to bridge the observability gap.