# Grodmir — Cursor AI gateway setup and coverage limits

> Evaluate the documented Cursor gateway template for requests sent to an OpenAI-compatible endpoint. Cursor-hosted models, Tab and indexing remain outside this connection; the integration has not been verified in a real Cursor application.

Grodmir is an AI gateway for data protection and AI usage governance in organisations.

## How can Cursor connect to the AI gateway?

Grodmir can inspect Cursor requests that reach its configured OpenAI-compatible base URL with a virtual key. Status: not verified in a real Cursor application; the repository contains templates and synthetic hook tests.

[Answer source](https://grodmir.com/en/integrations/cursor#how-can-cursor-connect-to-the-ai-gateway)

## Which Cursor channels bypass the gateway?

Cursor-hosted models, Tab and indexing use other channels. The configured gateway must be reachable from Cursor servers with TLS and authentication; a localhost gateway is insufficient. Repository header support is limited as documented in the guide.

[Answer source](https://grodmir.com/en/integrations/cursor#which-cursor-channels-bypass-the-gateway)

## What must be configured before testing the Cursor gateway?

Configure Override OpenAI Base URL with the customer gateway API endpoint and use a Grodmir virtual key for the intended OpenAI-compatible model. The gateway must be reachable from Cursor servers with TLS and authentication; a workstation localhost address is insufficient. Test the intended model workflow with synthetic data and confirm that corresponding audit metadata appears at the gateway. A configured URL alone does not establish coverage of every Cursor feature.

[Answer source](https://grodmir.com/en/integrations/cursor#gateway-setup)

## How do Cursor file hooks differ from gateway inspection?

The repository hook template runs aiguard repo check --agent cursor for beforeReadFile and beforeShellExecution to check excluded paths locally. Gateway inspection instead evaluates model requests that reach Grodmir. Per-repository headers cannot be attached through the documented Cursor setup, so gateway-side repository markers and path rules need those headers to be supplied another way. The templates and hook command have synthetic tests; their behaviour in a real Cursor application remains unverified.

[Answer source](https://grodmir.com/en/integrations/cursor#hooks-and-inspection)

- [Grodmir — self-hosted AI gateway](https://grodmir.com/en/ai-gateway)
- [Grodmir — MCP proxy for tool data protection](https://grodmir.com/en/mcp-proxy)
- [Grodmir — AI gateway protection limits](https://grodmir.com/en/limitations)
- [What do the Grodmir categories mean?](https://grodmir.com/en/glossary)
- [Grodmir — AI gateway selection criteria](https://grodmir.com/en/how-to-choose-an-ai-gateway)

## How can you verify this behaviour?

- [cursor (EN)](https://grodmir.com/dokumentacja/zrodla/cursor.md)

Content updated: 2026-11-14

Protection covers connected-channel traffic only; detection can miss data and raise false alarms. [Grodmir — AI gateway protection limits](https://grodmir.com/en/limitations)

Source: https://grodmir.com/en/integrations/cursor
