v1.2 closed three gaps that kept Curated out of enterprise pilots: shared chat history, real ArcGIS auth, and visible usage tracking.
What shipped
- ArcGIS OAuth 2.0 — moved from API keys to proper OAuth with PKCE. Both your ArcGIS Online and ArcGIS Enterprise accounts are now connected as a user identity, with token refresh, scoped permissions, and audit trail. API keys still work for legacy flows.
- Chat history panel — every conversation persists. Open the History tab in the sidebar to find any past prompt, restore the map state, and continue the conversation from where you left off.
- Credit usage tracking — usage is now metered and surfaced in real time. You can see what each prompt cost in compute credits, and admins can see roll-ups per user.
- Message feedback (👍 / 👎) — thumbs up or down on any answer. Feedback feeds directly into how we tune agent prompts.
- Report-an-issue with screenshot capture — flag a wrong answer and Curated grabs the map state, prompt, and current artifact automatically so support can see exactly what you saw.
- Spatial filter (Point-in-Polygon) with synchronized loading indicator — the map and the answer panel now agree on when something is still loading.
Why it mattered
Enterprise security teams won't approve a tool that uses static API keys. Enterprise analysts won't tolerate losing their work when the tab closes. Enterprise finance won't sign without usage visibility. v1.2 is the version where all three said yes.
Migration
API-key-based ArcGIS connections continue to work, but we recommend rotating to OAuth on your next visit to Settings → Connections. Same data, better security posture.