Skip to content

AGENT MANAGEMENT: feat(control): let a local agent manage the app - #491

Open
sunrisegm wants to merge 1 commit into
leookun:mainfrom
sunrisegm:feat/app-control-api
Open

sunrisegm wants to merge 1 commit into
leookun:mainfrom
sunrisegm:feat/app-control-api

Conversation

@sunrisegm

@sunrisegm sunrisegm commented Sep 30, 2026 •

Copy link
Copy Markdown

Summary

  • Add a separate App control setting that publishes the desktop management routes at http://127.0.0.1:{port}/byok/app/v1.
  • A local agent can configure the app, add models, and call the same paths the window uses (/models, /plugins, /settings, /harness/cursor).
  • The API can be off, open, or protected with a generated or pasted key using either Authorization: Bearer or X-Api-Key. The desktop window keeps using its internal routes.

Test plan

  • Open Settings and confirm the App control card is separate from the model external API.
  • With the API off, GET /byok/app/v1/models returns 403 and the settings window still loads.
  • Enable it without authorization and add a model through POST /byok/app/v1/models.
  • Turn authorization on, generate a key, choose Bearer, and confirm only Authorization: Bearer is accepted.
  • Switch the method to X-Api-Key and confirm Bearer is rejected.

Made with Cursor

Expose the desktop management routes on a separate switchable API so an agent can configure the app and add models without using the model proxy.

Co-authored-by: Cursor <cursoragent@cursor.com>
@sunrisegm sunrisegm changed the title feat(control): let a local agent manage the app AGENT MANAGEMENT: feat(control): let a local agent manage the app Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant