Add cursor rules for DeepSeek V4.1 Flash - #367

🏁 Script executed:

#!/bin/bash
set -e
printf '%s\n' '--- changed file ---'
cat -n rules/deepseek-v4-1-flash-coding-agent.mdc
printf '%s\n' '--- related model/API references ---'
rg -n -i 'deepseek|v4|vision|0910|437|429' rules README.md .github 2>/dev/null | head -n 240

Repository: PatrickJS/awesome-cursorrules

Length of output: 9467

🌐 Web query:

site:api-docs.deepseek.com DeepSeek API models deepseek-v4-flash vision image input

💡 Result:

The standard deepseek-v4-flash model does not support vision (image) input; attempting to use images with this model will result in a 400 error [1][2]. To use vision capabilities, you must specifically use the experimental model named deepseek-v4-flash-vision-exp [3][1]. This model is designed to accept images alongside text, allowing for tasks such as image description, text reading from screenshots, and chart analysis [1]. Key details regarding image input for deepseek-v4-flash-vision-exp: - Supported formats: JPEG, PNG, GIF, and WebP (detected from content, not filename/MIME type) [1]. - Input methods: Images can be provided via base64 data URLs, external http(s) URLs, or by referencing a file_id uploaded via the DeepSeek Files API [1][4]. - Usage restrictions: Images are supported only in user messages (or developer messages in the Responses API) [1][2]. Including images in system or assistant messages will return a 400 error [1][2]. - API compatibility: It follows the standard OpenAI-compatible Chat Completions format where content is passed as an array of blocks rather than a plain string [1]. - Billing: Images are tokenized for billing purposes, charged at the same rate as the standard V4-Flash model [4].

Citations:

• 1: https://api-docs.deepseek.com/guides/vision/
• 2: https://api-docs.deepseek.com/guides/responses_api/
• 3: https://api-docs.deepseek.com/
• 4: https://api-docs.deepseek.com/news/news260821/

🏁 Script executed:

#!/bin/bash
set -eu
printf '%s\n' '--- target rule ---'
cat -n rules/deepseek-v4-1-flash-coding-agent.mdc | sed -n '1,35p'
printf '%s\n' '--- related rule conventions ---'
cat -n rules/ai-agent-specialist.mdc | sed -n '1,12p'

Repository: PatrickJS/awesome-cursorrules

Length of output: 2632

🌐 Web query:

site:deepseek.com DeepSeek API documentation rate limits concurrency proxy data privacy

💡 Result:

The DeepSeek API documentation, services, and policies are summarized below based on current official information: Rate Limits and Concurrency DeepSeek API is designed to support very high usage, with the service infrastructure architected to handle up to 1 trillion tokens per day [1]. Regarding rate limits and concurrency, the official documentation states that there are no hard limits on requests or concurrent connections; users are encouraged to scale their usage as needed to ensure service quality [1]. If a request encounters a rate limit error (HTTP 429), the documentation advises users to pace their requests reasonably or consider switching to alternative LLM providers as a temporary measure [2]. Proxy Usage The DeepSeek API is designed to be compatible with standard OpenAI and Anthropic API formats [3][4][5]. Developers can configure their clients (such as OpenAI/Anthropic SDKs or compatible tools) by setting the base_url to https://api.deepseek.com or https://api.deepseek.com/anthropic, which inherently allows for the use of standard HTTP proxies if supported by the client library [3][4]. Data Privacy DeepSeek's data processing is governed by its Privacy Policy and Model Mechanism disclosure: - Data Storage and Processing: Personal data collected by DeepSeek may be stored on servers located in the People's Republic of China [6]. - Context Caching Security: For the context caching feature, user caches are logically isolated and invisible to other users [1]. Data in the cache is temporary and cleared after a period of inactivity [1]. - Model Training: DeepSeek states that if user input is utilized in optimization training, it undergoes strict de-identification, anonymization, and encryption to ensure it cannot be linked to specific individuals [7]. DeepSeek maintains that it does not use user data for personalized recommendations or profiling [7]. - Developer Responsibility: DeepSeek explicitly notes that its Privacy Policy does not cover the data processing rules for end-users of applications built by third-party developers using the DeepSeek platform; those developers are responsible for disclosing their own privacy policies to their users [8]. Top Results: [2][3][6][1][8][7]

Citations:

• 1: https://www.deepseek.com/news/context-caching/
• 2: https://api-docs.deepseek.com/quick_start/error_codes/
• 3: https://api-docs.deepseek.com/
• 4: https://api-docs.deepseek.com/quick_start/pricing-details-usd
• 5: https://api-docs.deepseek.com/guides/reasoning_model
• 6: https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy-2025-02-14.html
• 7: https://cdn.deepseek.com/policies/en-US/model-algorithm-disclosure.html
• 8: https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html

🏁 Script executed:

#!/bin/bash
set -eu
printf '%s\n' '--- target file ---'
cat -n rules/deepseek-v4-1-flash-coding-agent.mdc
printf '%s\n' '--- nearby rules mentioning retry, proxy, or tool calls ---'
rg -n -i -C 2 'retry|backoff|proxy|tool.call|tool call|idempot|429|connection drop' rules --glob '*.mdc' | head -240

Repository: PatrickJS/awesome-cursorrules

Length of output: 23294

🏁 Script executed:

cat -n rules/deepseek-v4-1-flash-coding-agent.mdc

Repository: PatrickJS/awesome-cursorrules

Length of output: 1932

🌐 Web query:

DeepSeek API official documentation retries tool calls idempotency 429 connection errors

💡 Result:

For the DeepSeek API, managing retries, idempotency, and error handling is primarily a client-side responsibility [1][2]. Retry Policy and Error Handling: - HTTP 429 (Rate Limit), 500 (Server Error), and 503 (Service Overloaded) are considered transient [1][3][4]. You should implement bounded retries with exponential backoff and jitter for these codes [1][5][2]. - Do not retry 400 (Invalid Format), 401 (Authentication), 402 (Insufficient Balance), or 422 (Invalid Parameters), as these require manual intervention or request correction [1][3][4]. - Network-related errors, such as timeouts or connection resets (often surfaced as APIConnectionError in OpenAI-compatible SDKs), should be treated as transient and are safe to retry, provided you use an idempotency key to prevent duplicate operations [6][4]. - Always honor a Retry-After header if it is present in the response [1][5]. Idempotency: - The DeepSeek API supports an Idempotency-Key header [6]. Including this header is critical for any non-idempotent operation (such as function or tool calls) to ensure that retries do not result in duplicate side effects [6][7]. - Use a unique key for each logical operation (e.g., a UUID generated at the start of the task) rather than per network attempt [6]. - Note: Idempotency is not supported for streaming requests (stream=true); do not include an Idempotency-Key when streaming, as it will cause a 400 error [6]. Tool Calls and Idempotency: - For agentic workflows, consider implementing additional application-level idempotency guards [7]. While the API supports the Idempotency-Key header, tools with side effects (like database writes or ordering systems) should ideally implement their own verification logic (e.g., checking if an order ID already exists) to guarantee safety against retries [7]. Rate Limits: - DeepSeek's rate limits are typically enforced as account-level concurrency limits rather than requests-per-minute (RPM) [3][5]. If you encounter persistent 429 errors, evaluate your concurrency (in-flight request count) rather than simply increasing retry frequency [5][2]. Top Results: [8], [1], [3], [5], [6], [4], [2]

Citations:

• 1: https://chat-deep.ai/docs/deepseek-retries-idempotency/
• 2: https://markaicode.com/howto/how-to-configure-deepseek-production-settings/
• 3: https://chat-deep.ai/docs/deepseek-error-codes/
• 4: https://theneuralbase.com/deepseek-api/learn/advanced/unified-error-handling/
• 5: https://deepseek-usa.ai/docs/deepseek-api-rate-limits/
• 6: https://theneuralbase.com/deepseek-api/learn/advanced/request-idempotency/
• 7: GitHub discussion 2811 in deepseek-ai/deepseek-harness (link omitted to avoid creating a cross-reference)
• 8: https://api-docs.deepseek.com/

🏁 Script executed:

sed -n '1,80p' rules/deepseek-v4-1-flash-coding-agent.mdc

Repository: PatrickJS/awesome-cursorrules

Length of output: 1757

🌐 Web query:

site:api-docs.deepseek.com quick_start rate_limit deepseek-v4-flash deepseek-v4-flash-vision-exp concurrency

💡 Result:

The DeepSeek API documentation does not explicitly publish specific numerical rate limits or concurrency caps for the deepseek-v4-flash, deepseek-v4-flash-vision-exp, or other models [1][2]. Limits are generally managed dynamically based on account status, usage patterns, and server load [1]. For developers getting started, DeepSeek provides an OpenAI-compatible API interface that allows access to these models [1][3][4]. Key points regarding these models: - Model Access: You can access deepseek-v4-flash and the experimental deepseek-v4-flash-vision-exp by setting the model name parameter in your API request to the corresponding string [1][2]. - Integration: Since the API follows the OpenAI-compatible standard, you can integrate these models into various tools (like Crush or WorkBuddy) by configuring the base_url to https://api.deepseek.com and providing your API key [3][4]. - Rate Limiting: If you encounter issues related to rate limits, the standard behavior is to implement exponential backoff in your application to handle HTTP 429 (Too Many Requests) errors gracefully. For the most accurate and up-to-date information regarding your specific account's quotas, it is recommended to check the developer dashboard on the official DeepSeek open platform.

Citations:

• 1: https://api-docs.deepseek.com/
• 2: https://api-docs.deepseek.com/zh-cn/
• 3: https://api-docs.deepseek.com/zh-cn/quick_start/agent_integrations/workbuddy
• 4: https://api-docs.deepseek.com/zh-cn/quick_start/agent_integrations/crush

🏁 Script executed:

python3 - <<'PY'
from urllib.request import urlopen
from html.parser import HTMLParser

url = "https://api-docs.deepseek.com/quick_start/rate_limit/"
try:
    data = urlopen(url, timeout=15).read().decode("utf-8", "replace")
except Exception as exc:
    print(f"FETCH_ERROR: {exc}")
else:
    text = HTMLParser().feed(data) if False else data
    import re
    text = re.sub(r"<script\b[^>]*>.*?</script>", " ", data, flags=re.S|re.I)
    text = re.sub(r"<style\b[^>]*>.*?</style>", " ", text, flags=re.S|re.I)
    text = re.sub(r"<[^>]+>", " ", text)
    text = re.sub(r"\s+", " ", text)
    for term in ("concurr", "rate limit", "429", "2500", "20"):
        pos = text.lower().find(term.lower())
        print(f"{term}: {text[max(0, pos-300):pos+700] if pos >= 0 else 'NOT_FOUND'}")
PY

Repository: PatrickJS/awesome-cursorrules

Length of output: 315

🏁 Script executed:

curl -k -L --max-time 20 -sS https://api-docs.deepseek.com/quick_start/rate_limit/ |
  tr '\n' ' ' |
  sed -E 's/<script[^>]*>.*<\/script>/ /Ig; s/<style[^>]*>.*<\/style>/ /Ig; s/<[^>]+>/ /g; s/[[:space:]]+/ /g' |
  grep -Eio '.{0,250}(concurr|rate limit|429|2500|20).{0,500}' |
  head -20

Repository: PatrickJS/awesome-cursorrules

Length of output: 3207

🏁 Script executed:

#!/bin/bash
printf '%s\n' '--- target rule ---'
cat -n rules/deepseek-v4-1-flash-coding-agent.mdc | sed -n '1,100p'
printf '%s\n' '--- repository references to DeepSeek protocol/base URLs ---'
rg -n -i -C 2 'deepseek|api\.deepseek\.com|/anthropic|chat/completions|/v1/messages' --glob '!node_modules' --glob '!dist' --glob '!build' .

Repository: PatrickJS/awesome-cursorrules

Length of output: 4660

🏁 Script executed:

#!/bin/bash
cat -n rules/deepseek-v4-1-flash-coding-agent.mdc | sed -n '1,100p'
rg -n -i -C 2 'deepseek|api\.deepseek\.com|/anthropic|chat/completions|/v1/messages' --glob '!node_modules' --glob '!dist' --glob '!build' .

Repository: PatrickJS/awesome-cursorrules

Length of output: 4579

🌐 Web query:

site:api-docs.deepseek.com DeepSeek Anthropic API base URL https://api.deepseek.com/anthropic OpenAI compatible

💡 Result:

The DeepSeek API provides specific base URLs for both OpenAI and Anthropic compatible formats [1][2]. For Anthropic compatible integrations, the official base URL is https://api.deepseek.com/anthropic [1][3]. For OpenAI compatible integrations, the base URL is https://api.deepseek.com [1][2]. Official documentation indicates that by configuring these base URLs, users can utilize the respective SDKs or compatible software to access DeepSeek models [1][3]. In some integration scenarios, such as the GitHub Copilot CLI, the Anthropic-compatible endpoint is specifically recommended to ensure proper handling of model output mechanisms like reasoning content [4].

Citations:

• 1: https://api-docs.deepseek.com/guides/reasoning_model
• 2: https://api-docs.deepseek.com/zh-cn/
• 3: https://api-docs.deepseek.com/
• 4: https://api-docs.deepseek.com/zh-cn/quick_start/agent_integrations/copilot_cli

🏁 Script executed:

printf 'target exists: '; test -f rules/deepseek-v4-1-flash-coding-agent.mdc && echo yes || echo no
sed -n '1,80p' rules/deepseek-v4-1-flash-coding-agent.mdc

Repository: PatrickJS/awesome-cursorrules

Length of output: 1776

🌐 Web query:

site:api-docs.deepseek.com "chat/completions" "api.deepseek.com" "v1/messages"

💡 Result:

The DeepSeek API follows the standard OpenAI-compatible Chat Completions API format, primarily using the endpoint https://api.deepseek.com/chat/completions [1][2]. While you mentioned "v1/messages" in your query, please note the following technical details based on official DeepSeek documentation: 1. Primary Endpoint: The standard endpoint for chat requests is https://api.deepseek.com/chat/completions [1][2]. This is the URL used for OpenAI-compatible SDKs [3][4]. 2. Anthropic API Support: DeepSeek also supports the Anthropic API format, which uses the base URL https://api.deepseek.com/anthropic [5][6]. If you are specifically looking for an endpoint structure related to "messages" (as in the Anthropic API's /v1/messages endpoint), you would use the Anthropic-compatible path [5]. 3. Implementation: You can interact with DeepSeek's models (such as deepseek-v4-pro or deepseek-v4-flash) by setting your base_url to https://api.deepseek.com (for OpenAI compatibility) or https://api.deepseek.com/anthropic (for Anthropic compatibility) [4][5]. If you are encountering a "v1/messages" reference, it is likely in the context of the Anthropic-compatible API, where the standard request path is /v1/messages [5]. Ensure your client configuration points to the correct base URL for the desired API format [4][5].

Citations:

• 1: https://api-docs.deepseek.com/zh-cn/api_samples/chat_curl
• 2: https://api-docs.deepseek.com/api/create-chat-completion/
• 3: https://api-docs.deepseek.com/zh-cn/
• 4: https://api-docs.deepseek.com/
• 5: https://api-docs.deepseek.com/guides/anthropic_api/
• 6: https://api-docs.deepseek.com/guides/reasoning_model_api_example_streaming