Skip to content

[WRONG BRANCH] fix(cli): expose Cursor native integration status - #425

Draft
luvs01 wants to merge 1 commit into
mainfrom
codex/propose-fix-for-cli-cursor-status-issue
Draft

[WRONG BRANCH] fix(cli): expose Cursor native integration status#425
luvs01 wants to merge 1 commit into
mainfrom
codex/propose-fix-for-cli-cursor-status-issue

Conversation

@luvs01

@luvs01 luvs01 commented Sep 3, 2026

Copy link
Copy Markdown
Owner

Motivation

  • The management capability metadata claimed ocx integration native would read /api/native-integrations/cursor, but the CLI did not actually request that route, leaving the documented Cursor status unreachable.

Description

  • Add cursor as a read-only action to the integration native CLI flow by updating src/cli/inspect.ts to include ocx integration native cursor [--json] in USAGE and to handle action === "cursor" by calling read("/api/native-integrations/cursor", ...).
  • Add a focused regression test in tests/cli-storage-inspect.test.ts that asserts the CLI issues a single GET /api/native-integrations/cursor request and prints the returned JSON (checks for "privateInference").
  • No changes to existing list or toggle behavior; toggles still PUT to the per-client routes and the list still queries /api/native-integrations.

Testing

  • Ran bun test tests/cli-storage-inspect.test.ts with the repository Bun (v1.4.0) and all tests in that file passed (22 tests, 0 failures).
  • Ran bun run typecheck and bun run skill:surface:check, both of which succeeded.
  • bun run test:changed could not run in this checkout because the comparison dev ref was not resolvable; the change is covered by the focused test added above.
  • Note: an older system bun test (v1.2.14) fails in this repo environment due to a runtime mismatch (node:zlib export), but the repository-pinned Bun v1.4.0 was used for the successful test run.

Codex Task

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 3, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-03T08:22:11.145255Z 3c1a315 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions github-actions Bot added the bug Something isn't working label Sep 3, 2026
@coderabbitai

coderabbitai Bot commented Sep 3, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (2)
  • ^dev$
  • ^preview$

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: 80af1157-dc2e-4d71-8cfb-6dbb298b6146

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot changed the title fix(cli): expose Cursor native integration status [WRONG BRANCH] fix(cli): expose Cursor native integration status Sep 3, 2026
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

⏳ DRAFT

  • wrong target branch (main); retarget to dev.

What to do

  • Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.

@github-actions
github-actions Bot marked this pull request as draft September 3, 2026 08:20

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3c1a315c75

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/cli/inspect.ts
ocx inspect star [--json]
ocx inspect windows-tray [--json]
ocx integration native [list] [--json]
ocx integration native cursor [--json]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Document Cursor in the actual integration help

When users run ocx integration native --help or ocx help integration, parseCliHead intercepts the request before this handler and renders the entry from src/cli/registry.ts; that entry still says native only shows or flips the Claude/Claude Desktop/Codex/Grok toggles and provides no cursor syntax. The docs site likewise contains no CLI invocation, so the newly exposed status action remains undiscoverable through normal help. Update the registry metadata and integration documentation alongside this private usage string.

AGENTS.md reference: AGENTS.md:L343-L344

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aardvark bug Something isn't working codex

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant