Connect GIS tools without hiding execution boundaries.

Choose the correct host package.

Host packages are versioned, have explicit asset identities and are distributed through a verified GitHub release channel. QGIS plugins typically use a plugin ZIP; ArcGIS Pro uses a native add-in plus appropriate Python/ArcPy components; the portable SDK offers separate wheel and source packages. Review the exact release notes before installing.

A response is not a completed geoprocessing operation.

Reliable GeoAI begins with a discoverable typed tool, accessible source data and a configured inference provider. The agent should propose a bounded plan, show side effects for review, execute only after authorization, capture a durable receipt and verify that spatial outputs were produced.

• Provider: local models require an installed runtime; external providers require explicit configuration and consent.
• Tools: limit commands to registered, typed operations and authorized GIS data.
• Approval: expose exact input versions, parameters and expected effects to the operator.
• Execution: distinguish a valid plan from a real native-host GIS tool call.
• Output: reopen data and validate counts, geometry, CRS and errors before reporting completion.

Release publication does not imply universal integration success.

Native pairing, QGIS plugin panel behavior, ArcGIS Pro add-in workflows, provider selection and adaptive agent execution must be tested in their respective environments. No claim of a fully functioning autonomous GIS assistant should be inferred solely from the availability of release ZIPs.

GeoTwins Harness is not the GIS-host SDK.

The Harness 0.8 Preview 1 independently packages a native Windows agent workspace, constrained file operations, model-provider diagnostics and a local session journal. It does not inherit GIS host permissions or replace QGIS, ArcGIS Pro, Python SDK or AGOT installation.