AI Agent QGIS 4 compatibility

The agent inspects the open project, styles layers, runs Processing, edits data and creates layouts from plain-language requests. Changes wait in a visible plan until you press Apply, unless you switch to Auto mode, where they apply themselves and only destructive steps still ask. Everything the agent reads goes to the language model you configure: your prompt, the conversation and its summaries, attached pictures, project notes, layer and field metadata, and tool results such as feature attribute values, exact map and layer extents, layer filters and sources, style categories, Processing and Python results, and rendered map or layout images. There is no switch that holds them back, so use a local model server for projects that must not leave your computer. The first send to each remote endpoint asks for confirmation; agreeing is remembered for that endpoint. Open-data tools contact the Microsoft Planetary Computer, GitHub, geoBoundaries and the public map services of the catalogue (NASA GIBS, EOX, GEBCO, OpenTopoMap, IGN France, PDOK, swisstopo, USGS, Geoscience Australia) only after per-call confirmation; each can be switched off in Settings. Personalisation text from Settings is sent with every request. Optional web tools require per-call confirmation: searches contact DuckDuckGo or Wikipedia, geocoding contacts the Photon demo or custom Nominatim service selected in Settings, and page reads contact the approved public HTTPS host. Geocoding is disabled until a service is selected, and the public OSMF Nominatim instance is not offered. Private hosts and credential-bearing URLs are rejected. Web results are untrusted, may be sent to the configured model and are not cached on disk. Conversation messages and project notes are stored as plain JSON in the QGIS profile. When enabled, applied runs write an unencrypted Markdown journal containing shortened request and agent text, tool names, errors and outcome in the profile's ai_agent_runs directory; owner-only permissions are applied where supported, the path is reported and the file remains until the user deletes it. API keys are stored encrypted in the QGIS authentication database and unlocked by the QGIS master password; only the identifier of the stored entry reaches the settings file. The plugin has no external Python dependencies. OpenAI-compatible providers including Google Gemini, Anthropic and local endpoints are supported. A local server can still store or forward data. The interface is available in English and Russian.