langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 12:32:54 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

How to config the Continue assistant to use Dify API in VS Code? #16128

New Issue
Closed
opened 2026-02-21 19:24:45 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:24:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @pwplucky on GitHub (Aug 13, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I use Continue - a open-source AI code assistant in vs code, but how to config the Continue use Dify api?

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @pwplucky on GitHub (Aug 13, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. I use Continue - a open-source AI code assistant in vs code, but how to config the Continue use Dify api? ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 🙋‍♂️ question label 2026-02-21 19:24:45 -05:00
yindo closed this issue 2026-02-21 19:24:45 -05:00
yindo commented 2026-02-21 19:24:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 13, 2025):

Hi @pwplucky! I'm Dosu and I’m helping the dify team.

Dify's API is not a drop-in replacement for OpenAI's API, so you can't directly configure Continue to use Dify just by changing the endpoint and API key. Dify uses different endpoint paths and request/response schemas (for example, /v1/chat-messages instead of /v1/chat/completions), so tools like Continue that expect strict OpenAI compatibility won't work out of the box1 .

To make Continue work with Dify, you'd need to build an adapter or proxy that translates OpenAI-style requests from Continue into Dify's API format and maps the responses back. This involves handling endpoint routing, payload transformation, and authentication (Dify uses Authorization: Bearer <API_KEY>)2 .

If you're interested in contributing, a good starting point is to review Dify's API documentation and OpenAPI specs, and look at how Continue sends requests to OpenAI. You'd then implement a small service that sits between Continue and Dify, translating requests and responses as needed.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 13, 2025): <!-- Greeting --> Hi @pwplucky! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> Dify's API is not a drop-in replacement for OpenAI's API, so you can't directly configure Continue to use Dify just by changing the endpoint and API key. Dify uses different endpoint paths and request/response schemas (for example, `/v1/chat-messages` instead of `/v1/chat/completions`), so tools like Continue that expect strict OpenAI compatibility won't work out of the box[^1]. To make Continue work with Dify, you'd need to build an adapter or proxy that translates OpenAI-style requests from Continue into Dify's API format and maps the responses back. This involves handling endpoint routing, payload transformation, and authentication (Dify uses `Authorization: Bearer <API_KEY>`)[^2]. If you're interested in contributing, a good starting point is to review Dify's API documentation and OpenAPI specs, and look at how Continue sends requests to OpenAI. You'd then implement a small service that sits between Continue and Dify, translating requests and responses as needed. [^1]: [Dify API endpoints and differences](https://github.com/langgenius/dify/blob/e336a8666a95ece8a9f86ac09a5b121b527a567d/api/controllers/service_api/app/completion.py) [^2]: [Dify API authentication and endpoint structure](https://github.com/langgenius/dify/blob/e336a8666a95ece8a9f86ac09a5b121b527a567d/api/extensions/ext_blueprints.py) <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/3bf49fa6-5166-4890-87d4-1b03bb30331a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/3bf49fa6-5166-4890-87d4-1b03bb30331a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/3bf49fa6-5166-4890-87d4-1b03bb30331a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/3bf49fa6-5166-4890-87d4-1b03bb30331a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/3bf49fa6-5166-4890-87d4-1b03bb30331a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/3bf49fa6-5166-4890-87d4-1b03bb30331a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/3bf49fa6-5166-4890-87d4-1b03bb30331a?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/23885)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🙋‍♂️ question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#16128
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?