# Sign in with Cursor — OAuth for Third-Party Apps Using Users’ Cursor Plans

**URL:** <https://forum.cursor.com/t/sign-in-with-cursor-oauth-for-third-party-apps-using-users-cursor-plans/177035>\
**Category:** Feature Requests\
**Tags:** cursor-sdk, login\
**Created:** [November 2, 2026, 11:27am UTC](https://forum.cursor.com/t/sign-in-with-cursor-oauth-for-third-party-apps-using-users-cursor-plans/177035 "2026-11-02T11:27:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![yu-iskw](https://avatars.discourse-cdn.com/v4/letter/y/cab0a1/32.png) [@yu-iskw](https://forum.cursor.com/u/yu-iskw)\
**Post date:** [November 2, 2026, 11:27am UTC](https://forum.cursor.com/t/sign-in-with-cursor-oauth-for-third-party-apps-using-users-cursor-plans/177035/1 "2026-11-02T11:27:15Z")

</div>

### Feature request for product/service

API Keys

### Describe the request

Cursor SDK already supports browser-based authentication (Cursor.auth.login()) and charging SDK usage to a user’s Cursor plan.

However, it would be great to support a dedicated OAuth authorization flow for third-party web applications, similar to OpenAI’s Sign in with ChatGPT.

Ideally:

- Users sign in with Cursor and authorize an external application to consume their existing Cursor plan allowance.
- Developers use Cursor SDK / Agent SDK on behalf of authorized users without collecting long-lived API keys.
- Users can review, limit, and revoke each application’s access and usage.

This would make it much easier to build secure, multi-user web applications powered by Cursor agents while allowing users to bring their existing subscriptions.

Related discussion: [Public API/SDK to integrate Cursor chat models into third-party apps](https://forum.cursor.com/t/public-api-sdk-to-integrate-cursor-chat-models-into-third-party-apps/152866)