← Back to overview
Security & Transparency

No telemetry — don't take our word for it

"No telemetry" is easy to write and hard to check. So we checked it the way you would: we recorded every packet on a Debian 12 laptop running the IDEAgent package, once with the plugins disabled and once while using the agent, and traced each connection to the component that opened it. The script, the cleaned logs and the code that cleaned them are published below, so you can check our work or run the same test yourself.

Scope: the IDEAgent package — IDE Gateway Plugin, RAG File Watcher, Gateway, MCP Server, RAG Server and ChromaDB.

Telemetry endpoints identified
None.
Internet traffic from the containers
Expected proxy traffic to LLM providers, initialization pings for local models, and dynamic web search fallback.
Tested on
November 2026 · Debian 12

What leaves your machine, and why

The IDEAgent environment consists of three primary containers. Here is every outbound connection they make, and why:

Component IP Address Destination What it is
Gateway 172.18.0.2 Google LLC (e.g., generativelanguage.googleapis.com) Expected proxy traffic to external LLM providers. The Gateway container acts as the designated proxy for external LLM inference. Use Ollama and this goes away.
MPC-Server 172.18.0.3 HuggingFace (Cloudfront) A brief initialization ping for ETag/metadata checks for the local all-MiniLM-L6-v2 model. No user data or prompts are transmitted. Can be air-gapped by setting HF_HUB_OFFLINE=1 and TRANSFORMERS_OFFLINE=1.
RAG-Server 172.18.0.4 Dynamic external domains (e.g., webawere.nl) Web Search Fallback Mechanism. Queries DuckDuckGo and scrapes top URLs to ingest missing context when local retrieval confidence is low. Not hardcoded telemetry.

The traffic footprint is deterministic and entirely explainable by its architectural design. By applying the provided hardening flags, organizations can enforce strict data residency and network isolation.

The proof: a capture you can repeat

Machine
Debian 12 laptop on a home network, IDEAgent containers in Docker, PyCharm on the host
Method
tshark and shell scripts to capture network logs, docker network data, and system logs.
Script
local_audit.sh — the exact script we ran

Destinations by Domain

Visualizes the top external IP/Domain destinations contacted by the containers.

Top destinations chart

Traffic by Container

Visualizes the volume and distribution of outbound network traffic originating from each specific container.

Traffic by container chart

Raw data

The original logs and analysis data collected during the test are available as a single archive for easy download and scanning.

Download test logs (.zip)

ChromaDB

The RAG Server stores the local index of your code, learnings and docs in ChromaDB. ChromaDB is a third-party database, and it ships with its own anonymized product telemetry (sent to PostHog), controlled by the ANONYMIZED_TELEMETRY setting. This section shows what ChromaDB does on the network inside the IDEAgent package.

How we configure it
Telemetry is disabled. The RAG Server connects to ChromaDB locally over the Docker network on port 8000.
What the capture shows
ChromaDB made zero external connections during the capture. All its traffic was local communication with the RAG Server.

Watch the test

The recorded test run, edited.

Watch on YouTube: IDEAgent security test run ↗

What's inside the containers

For each image: the exact version and digest, the Docker Scout findings and what we decided about each one, and the full dependency list.

Image Version · digest Scout findings (C / H / M / L) Decisions Dependencies / SBOM
Gateway latest (Nov 2026) 0C / 0H / 0M / 0L No vulnerable packages detected -
MCP Server latest
digest: 2a118346aae0
0C / 0H / 0M / 0L No vulnerable packages detected 218 packages
RAG Server latest (Sep 2026) 3C / 14H / 47M / 7L Work in progress (pending base image update) -

How your data is handled

  • API keys stay in your operating system's keystore. The plugin sends them only to the Gateway you run, which presents them only to the provider you selected. Gateway →
  • Your code is indexed into the RAG Server on infrastructure you control. Only the pieces the agent retrieves are sent to a hosted model, and only if you configure one. With Ollama, nothing leaves. MCP & RAG →
  • Secrets in tool results can be redacted before they reach the model. How redaction works →
  • Risky actions wait for your approval. git, sudo and docker commands always ask, even in Auto mode. Human-in-the-loop →

Known limits

What this capture proves, and what it doesn't:

  • It proves which internet addresses the IDEAgent containers contacted over TCP during these runs, when, and how much data went each way, on every interface.
  • Docker images change. The result holds for the versions we tested.

Report a vulnerability

Pending. Security contact to be confirmed.