vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-20 23:57:11 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[GH-ISSUE #314] [Bug]: DeepSeek deprecated old model names, creating flow fails with new deepseek-v4-pro #102

New Issue
Closed
opened 2026-06-06 22:09:08 -04:00 by yindo · 1 comment
yindo commented 2026-06-06 22:09:08 -04:00
Owner
Copy Link
Copy Source

Originally created by @qzinori on GitHub (May 14, 2026).
Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/314

Originally assigned to: @asdek on GitHub.

Affected Component

External Integrations (LLM/Search APIs)

Describe the bug

What should happen:

  • Expected behavior: When users enter the official supported new model names deepseek-v4-pro or deepseek-v4-flash, the system should use the exact name provided to make API requests without automatically appending any suffix, allowing flows to be created and run successfully.

Additional context:

  • Task/Flow ID: N/A (fails directly during flow creation)
  • Error messages: As shown above
  • Old to new model name mapping:
    • Old: deepseek-chat → New: deepseek-v4-pro
    • Old: deepseek-reasoner → New: deepseek-v4-flash
  • Root cause: PentAGI internal code has hardcoded logic to automatically append /deepseek-chat suffix to all DeepSeek model names, which is incompatible with DeepSeek's latest API naming specification
  • Test environment: Kali Linux 2025.x, Docker 28.5.2, latest stable PentAGI version

Steps to Reproduce

  1. Access PentAGI Web UI at https://localhost:8443
  2. Create a new flow/task with any basic prompt
  3. Observe the 400 error message appears immediately

System Configuration

PentAGI Version: latest from Docker Hub (as of 2026-05-15)
Deployment Type:

  • Docker Compose
  • Custom Deployment

Environment:

  • Operating System: Kali GNU/Linux Rolling (Kernel 6.19.14+kali-amd64)
  • Docker Version: 28.5.2+dfsg4
  • Docker Compose Version: 2.40.3-3
  • Browser: Google Chrome 125.0.6422.141
  • DeepSeek API Endpoint: https://api.deepseek.com

Logs and Artifacts

No response

Screenshots or Recordings

No response

Verification

  • I have checked that this issue hasn't been already reported
  • I have provided all relevant configuration files (with sensitive data removed)
  • I have included relevant logs and error messages
  • I am running the latest version of PentAGI
Originally created by @qzinori on GitHub (May 14, 2026). Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/314 Originally assigned to: @asdek on GitHub. ### Affected Component External Integrations (LLM/Search APIs) ### Describe the bug ## What should happen: - Expected behavior: When users enter the official supported new model names `deepseek-v4-pro` or `deepseek-v4-flash`, the system should use the exact name provided to make API requests without automatically appending any suffix, allowing flows to be created and run successfully. ## Additional context: - Task/Flow ID: N/A (fails directly during flow creation) - Error messages: As shown above - Old to new model name mapping: - Old: `deepseek-chat` → New: `deepseek-v4-pro` - Old: `deepseek-reasoner` → New: `deepseek-v4-flash` - Root cause: PentAGI internal code has hardcoded logic to automatically append `/deepseek-chat` suffix to all DeepSeek model names, which is incompatible with DeepSeek's latest API naming specification - Test environment: Kali Linux 2025.x, Docker 28.5.2, latest stable PentAGI version ### Steps to Reproduce 1. Access PentAGI Web UI at https://localhost:8443 2. Create a new flow/task with any basic prompt 3. Observe the 400 error message appears immediately ### System Configuration PentAGI Version: latest from Docker Hub (as of 2026-05-15) Deployment Type: - [x] Docker Compose - [ ] Custom Deployment Environment: - Operating System: Kali GNU/Linux Rolling (Kernel 6.19.14+kali-amd64) - Docker Version: 28.5.2+dfsg4 - Docker Compose Version: 2.40.3-3 - Browser: Google Chrome 125.0.6422.141 - DeepSeek API Endpoint: https://api.deepseek.com ### Logs and Artifacts _No response_ ### Screenshots or Recordings _No response_ ### Verification - [x] I have checked that this issue hasn't been already reported - [ ] I have provided all relevant configuration files (with sensitive data removed) - [ ] I have included relevant logs and error messages - [x] I am running the latest version of PentAGI
yindo added the bug label 2026-06-06 22:09:08 -04:00
yindo closed this issue 2026-06-06 22:09:08 -04:00
yindo commented 2026-06-06 22:09:09 -04:00
Author
Owner
Copy Link
Copy Source

@asdek commented on GitHub (May 29, 2026):

hi @qzinori,

thank you for the issue, it was fixed with the latest build, now deepseek v4 is fully supported

<!-- gh-comment-id:4580473252 --> @asdek commented on GitHub (May 29, 2026): hi @qzinori, thank you for the issue, it was fixed with the latest build, now deepseek v4 is fully supported
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
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: vxcontrol/pentagi#102
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?