Cursor

Cursor offers two paths, and they don’t give the same result:

	Claude Code extension	Cursor’s custom OpenAI key
What goes through Kloria	Everything the Claude Code agent does	Cursor’s chat with a custom model
Models	Claude	Claude and GPT
Cursor’s Agent, Tab, inline edit	Not involved (stay on Cursor)	No: they use Cursor’s models
Cursor plan required	No	Yes, a paid plan

If you want a full agent on your Kloria key, use the Claude Code extension.

Option 1: the Claude Code extension (recommended)

The official Claude Code extension installs in Cursor just like in VS Code. Follow the VS Code page: the steps and the configuration block are the same, in Cursor’s user settings.

Option 2: Cursor’s custom OpenAI key

1. Open the model settings

   Cursor Settings → Models.

2. Enter the key and address

   • In OpenAI API Key, paste your Kloria key.
   • Turn on Override OpenAI Base URL and enter https://api.kloria.dev/v1.

3. Add the Kloria models

   In Add or search model, type a model’s exact ID, for example claude-sonnet-5 or gpt-6.1-sol, press Enter, then enable it.

4. Test in the chat

   Open the chat in Ask mode, pick the model you just added and send a message. The request should appear under Usage Logs in the Kloria console.

Limits of this option

• The custom address applies to all of Cursor’s OpenAI-format requests: while it’s on, Cursor’s built-in models may return errors. Turn the option off to go back to them.
• Cursor’s servers call Kloria, not your machine. Your key therefore goes through Cursor.
• If Cursor shows a network or TLS error while the key works with cURL, set Cursor Settings → Network → HTTP Compatibility Mode to HTTP/1.1.