Skip to content

feat(tools for cursor): add text outputs (keep JSON) and improve status/conversation error handling#1171

Open
LogicOber wants to merge 3 commits intolanggenius:mainfrom
LogicOber:main
Open

feat(tools for cursor): add text outputs (keep JSON) and improve status/conversation error handling#1171
LogicOber wants to merge 3 commits intolanggenius:mainfrom
LogicOber:main

Conversation

@LogicOber
Copy link
Collaborator

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

Release 0.0.2 focuses on output consistency, clearer summaries, and resilient error handling:

  • Output normalization
    • Add Follow-up: emits enriched JSON ({request, response}) then English text (“Add follow-up succeeded”); on failure, emits error JSON ({request, status_code, error}) then English failure text.
    • Delete Agent: emits enriched JSON ({request, response}) then English text (“Delete succeeded”); on failure, emits error JSON ({request, status_code, error}) then English failure text.
  • Agent Status: returns the original JSON and a concise English text summary (ID, Name, Created At, Source Ref/Repository, Status, Summary, Target Branch/URL) for easier use in Dify Workflow/Chatflow.
  • Agent Conversation: returns the original JSON and a short English summary (message count and first message preview). On HTTP errors (e.g., 500/409/404), emits error JSON (status code + details), then a readable English error text, and raises to surface the failure.
  • Documentation: README corrected the API key prefix from “sk_” to “key_”, plus minor clarifications.
  • Quality: all changes linted; no changes to tool parameter schemas.

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

  • Data Collection (only what’s necessary for functionality):

    • The plugin itself does not collect information, so privacy is governed entirely by https://cursor.com/.
  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

…ping JSON

- add_followup: emit enriched JSON {request, response} then English text
  ("Add follow-up succeeded"); on failure emit error JSON {request, status_code,
  error} then "Add follow-up failed (...)".
- delete_agent: emit enriched JSON {request, response} then "Delete succeeded";
  on failure emit error JSON {request, status_code, error} then
  "Delete failed (...)".
- agent_status: keep original JSON and add a concise English summary
  (ID, Name, Created At, Source Ref/Repository, Status, Summary, Target Branch/URL).
- agent_conversation: keep JSON and add a short English summary; on HTTP errors,
  emit error JSON with status code and details, then a readable English error and raise.
- docs(README): fix API key prefix to "key_".

Linted and verified; no tool parameter schema changes.
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