Sameh Khamis c1f60cb7e7 Cut the Google requests the HUD summary makes on its own ...

The HUD builds place context for its AI summary whenever the camera
settles, and each build paid for up to four reverse geocodes plus a Nearby
Places search, even when no OpenAI key was configured to use them.

- Ask GET /api/openai/hud-summary/status once; with no summary configured,
  or after an unconfigured reply, make no place lookups for the page.
- Reverse-geocode at most two points: the view center and one viewport
  point.
- Reuse a lookup until the view center moves a quarter of the visible
  width, the camera's distance to it doubles or halves, or the camera
  crosses a lookup height. The reused points are asked again, so only a
  timeout, failure or empty answer spends.
- Repaint the last AI reply when a small pan leaves the context unchanged.

Cached-only hosts and voice context lookups are unchanged.

2026-10-28 14:59:33 -07:00

..

mcp

fix(mcp): serialize shared panel key repair and credit report

2026-10-07 15:12:44 -07:00

providers

Cut the Google requests the HUD summary makes on its own

2026-10-28 14:59:33 -07:00

standalone

fix(maps): avoid 404 on keyless Google tiles-token probe (#1066)

2026-10-25 19:13:38 -07:00