Add user_id Data Isolation for Reasonix System

[zeroro88]

Overview

Reasonix currently shares all user sessions, memory, task and API request resources globally without user_id isolation. When serving multiple end-users under one DeepSeek account, it will cause cross-user KV cache interference, scheduling conflicts and inaccurate rate limiting. We need to support configurable user_id to implement DeepSeek official multi-user isolation capabilities.

Why We Need This

• DeepSeek API supports user_id isolation, including KV Cache isolation, scheduling isolation and content safety isolation
• Without user_id isolation, different end-users’ reasoning contexts may conflict or leak with each other
• Lack of user-level independent concurrency rate limit, causing 429 inaccurate triggering in multi-user scenarios

Expected Features

• Configurable user_id (core)
• Support configuring static/dynamic user_id via Reasonix local config, no hardcode
  https://api-docs.deepseek.com/quick_start/rate_limit

[richardchen874-sys]

This is an important feature for production multi-user systems.

If multiple end-users share one DeepSeek API account or provider key, user_id isolation can help with:

• KV cache / reasoning context isolation
• accurate rate-limit attribution
• safer multi-tenant request tracking
• easier debugging when one user triggers 429s
• cleaner cost attribution per user or workspace

For small AI SaaS teams, this becomes important very quickly once usage grows beyond personal testing.

I’m working around DeepSeek / OpenAI-compatible API access for small AI builders, and multi-user isolation, rate limits, and cost attribution are exactly the kinds of issues that matter in production.