I need the first working login path
Start with API key setup if your current blocker is basic authentication or getting the first provider response.
Go to API key setupConfig Hub
DeepSeek TUI config questions usually start with API keys and end with workflow details
Configuration pages exist because successful install does not mean useful setup. Most new users still need provider setup, auth, and the first runtime decisions explained clearly.
Choose the config path by question type
Use this hub as the config list first. Pick the exact setup problem you need to solve, then open the detail page.
I need the right provider and endpoint route
Start with provider setup if the key exists but the runtime still does not match the endpoint or vendor path you expect.
Go to provider setupI need to untangle a messy config state
Start with file location, environment variables, or reset if the tool keeps reading the wrong state.
Go to file location guideConfig article list
Open the exact config detail page you need instead of mixing auth, provider, and file-level problems in one session.
DeepSeek TUI API key setup
Start here if your current blocker is authentication, provider selection, or first-run config.
Open API key pageProvider setup
Use this page if you already understand API keys but still need to decide which provider path fits your runtime and endpoint setup.
Open provider setupConfig file location
Open this page when the real problem is not what to write, but which config file DeepSeek TUI is actually reading.
Open file location guideEnvironment variables
Use this when runtime behavior still ignores your file edits and you suspect shell-level overrides.
Open environment variables guideReset DeepSeek TUI config
Use this page when the current config state is so tangled that a clean reset is more efficient than more patching.
Open config reset guideProvider cost
Use this page when your pricing question is really about which provider meters the usage behind DeepSeek TUI.
Open provider cost guideMCP and skills build on config
Do not jump into advanced workflows before the core auth and runtime path is stable.
Open MCP guide