Preloop 0.14.0: Cursor usage import, rate-limit intelligence, agent identity v2
Preloop 0.14.0: Cursor usage import, rate-limit intelligence, agent identity v2
Preloop 0.14.0 shipped on 7 August 2026. Three highlights from the changelog.
Cursor usage import
Cursor Composer and Auto models never traverse the model gateway, so that spend was invisible in Cost analytics. 0.14.0 adds two ingest endpoints: POST /api/v1/usage/import for normalized events, and POST /api/v1/usage/import/csv for the Cursor dashboard Usage CSV export (case-insensitive, order-independent headers, with an optional column_map for other export shapes).
Imported events are attributed to a managed agent and land in the cost ledger as imported_usage rows. Imports are idempotent: every event carries a dedupe fingerprint, so re-importing the same CSV reports skipped_duplicates instead of double-counting. Imported spend surfaces as a separate "Imported usage" section in Cost analytics. It carries a "Not gateway metered" badge and stays out of gateway estimated_cost, budgets, and spend caps.
Rate-limit intelligence
The gateway now captures upstream 429s and provider rate-limit headers (Retry-After, anthropic-ratelimit-*, x-ratelimit-*) as real observations, normalizes them into rate-limit snapshots, and persists them on the usage row.
GET /api/v1/account/gateway-usage/rate-limits reports rate-limited request counts, blocked time, quota-exhausted vs transient breakdown, and per-model and per-session detail. Undocumented provider headers are preserved verbatim rather than presented as normalized facts.
Agent identity v2
The CLI derives session_source_id from host + source type + config path, so a managed agent keeps one durable identity when its display name changes or it is re-onboarded. --no-reuse is the salted escape hatch.
POST /api/v1/agents/{id}/rekey and POST /api/v1/agents/{id}/merge rewrite or consolidate durable principal ids across usage, sessions, budgets, and approvals, with dry-run support. Exposed as preloop agents merge.
The full changelog is in the 0.14.0 release notes.