Add plugin: Cursor Integration

[px39n]

I am submitting a new Community Plugin

• I attest that I have done my best to deliver a high-quality plugin, am proud of the code I have written, and would recommend it to others. I commit to maintaining the plugin and being responsive to bug reports. If I am no longer able to maintain it, I will make reasonable efforts to find a successor maintainer or withdraw the plugin from the directory.

Repo URL

Link to my plugin: https://github.com/px39n/obs_cursor

Release Checklist

• I have tested the plugin on
  • Windows
  • macOS
  • Linux
  • Android (if applicable)
  • iOS (if applicable)
• My GitHub release contains all required files (as individual files, not just in the source.zip / source.tar.gz)
  • main.js
  • manifest.json
  • styles.css (optional)
• GitHub release name matches the exact version number specified in my manifest.json (Note: Use the exact version number, don't include a prefix v)
• The id in my manifest.json matches the id in the community-plugins.json file.
• My README.md describes the plugin's purpose and provides clear usage instructions.
• I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugin's adherence to these policies.
• I have read the tips in https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines and have self-reviewed my plugin to avoid these common pitfalls.
• I have added a license in the LICENSE file.
• My project respects and is compatible with the original license of any code from other plugins that I'm using.
  I have given proper attribution to these other projects in my README.md.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ You did not follow the pull request template. The PR template can be found here
❌ Please don't use the word obsidian in the plugin ID. The ID is used for your plugin's folder so keeping it short and simple avoids clutter and helps with sorting.
❌ Please don't use the word Obsidian in your plugin name since it's redundant and adds clutter to the plugin list.
❌ Please don't include Obsidian in the plugin description
❌ You don't have a manifest.json at the root of your repo, or it could not be parsed.

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ You did not follow the pull request template. The PR template can be found here

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ You did not follow the pull request template. The PR template can be found here
❌ Unable to find a release with the tag 1.0.0. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ You did not follow the pull request template. The PR template can be found here

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[px39n]

NICE!!! Finally XD

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

Required

[1]
Async method 'onload' has no 'await' expression.

[1]
Use sentence case for UI text.

[1]
Avoid setting styles directly via element.style.position. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.left. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2][3][4][5][6][7][8][9][10][11][12][13]
Unexpected console statement. Only these console methods are allowed: warn, error, debug.

[1]
'Server' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1]
'Buffer' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1]
'WebSocket' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1]
Expected the Promise rejection reason to be an Error.

[1][2]
'any' overrides all other types in this union type.

[1][2]
'Disposable' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1][2][3][4][5]
Invalid type "unknown" of template literal expression.

[1][2]
Promise returned in function argument where a void return was expected.

[1]
'Hover' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1]
'MarkdownString' is an 'error' type that acts as 'any' and overrides all other types in this union type.

---

Optional

---

Do NOT open a new PR for re-validation.
Once you have pushed some changes to your repository the bot will rescan within 6 hours
If you think some of the required changes are incorrect, please comment with /skip and the reason why you think the results are incorrect.
To run these checks locally, install the eslint plugin in your project.
Do NOT rebase this PR, this will be handled by the reviewer once the plugin has been approved.

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

Required

[1]
Async method 'onload' has no 'await' expression.

[1]
Use sentence case for UI text.

[1]
Avoid setting styles directly via element.style.position. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.left. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
'Server' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1]
'Buffer' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1]
'WebSocket' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1]
Expected the Promise rejection reason to be an Error.

[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19]
Unexpected console statement. Only these console methods are allowed: warn, error, debug.

[1][2]
'any' overrides all other types in this union type.

[1][2]
'Disposable' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1][2][3][4][5]
Invalid type "unknown" of template literal expression.

[1][2]
Promise returned in function argument where a void return was expected.

[1]
'Hover' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1]
'MarkdownString' is an 'error' type that acts as 'any' and overrides all other types in this union type.

[1]
'Uri' is an 'error' type that acts as 'any' and overrides all other types in this union type.

---

Optional

---

Do NOT open a new PR for re-validation.
Once you have pushed some changes to your repository the bot will rescan within 6 hours
If you think some of the required changes are incorrect, please comment with /skip and the reason why you think the results are incorrect.
To run these checks locally, install the eslint plugin in your project.
Do NOT rebase this PR, this will be handled by the reviewer once the plugin has been approved.

[px39n]

/skip The VS Code extension files (vscode-extension/*) are not part of the Obsidian plugin. The Obsidian plugin is located in obsidian-plugin/. The VS Code extension is a separate companion tool that connects to the Obsidian plugin's WebSocket server. Please only validate files in the obsidian-plugin/ directory.