Eclipse Integration Guide

Overview

Cup’n’String detects running instances of the Eclipse IDE. It applies process fingerprinting and network governance to secure AI plugins (such as Tabnine or custom LSP endpoints) running inside Eclipse.

Support level

Auto-Discovered

What Cup’n’String detects

• Running Eclipse process signatures
• Active Java virtual machine process parentage
• Network sockets opened by Eclipse plugin helper processes

What it governs

• Outbound API requests to LLM providers from Eclipse
• Baseline secret shielding for IDE environment variables
• Access limits to local model servers

Recommended policies

• Require all Eclipse AI plugins to route API traffic through the local proxy
• Block direct internet connections from Eclipse JVM processes
• Audit workspace paths read by AI extension helpers

Setup outline

1. Ensure the Cup’n’String desktop agent is running.
2. Launch Eclipse.
3. The agent automatically discovers the process and applies baseline network filters.

Verification

Verify that outbound network requests from Eclipse AI tools are captured in the local agent log.

Troubleshooting

If Eclipse is not monitored, ensure it is installed in standard paths and is not running under an unapproved JVM wrapper.

Known limitations

Does not support native inline content decoration or detailed prompt AST auditing within the Eclipse UI.