Configuration Docs
Configuration documentation is useful because many practical failures come from provider, path, and runtime assumptions rather than the install step itself.
Open docs pageDocs Hub
DeepSeek TUI docs deserve their own hub because repo docs and search intent are not the same thing
This hub turns the upstream docs directory into a browsable structure for install, config, MCP, runtime, architecture, and maintainer-oriented reading paths.
Core Docs
Docs topics grouped by search and reading intent.
Install Docs
Install documentation belongs in docs because many users search for a more official explanation than short package-manager snippets.
Open docs pageMCP Docs
MCP documentation is worth listing separately because many advanced DeepSeek TUI searches now revolve around MCP concepts, setup, and extension strategy.
Open docs pageModes Docs
Modes documentation matters because mode choice is one of the clearest workflow decisions users make after basic setup.
Open docs pageKeybindings
Keybindings become important after first-run success, especially for users who want faster terminal navigation instead of reading mode pages repeatedly.
Open docs pageRuntime API
Runtime API documentation matters when search intent shifts from usage to integration and programmatic control.
Open docs pageSubagents
Subagents deserve a dedicated docs page because they are one of the clearest advanced concepts people search once terminal-agent workflows become more complex.
Open docs pageTool Surface
Tool surface docs help users who want to understand which actions DeepSeek TUI can actually take, not just what the homepage promises.
Open docs pageWorkflow and Ops
Docs topics grouped by search and reading intent.
Docker
Docker docs matter when users want DeepSeek TUI in a more controlled runtime instead of depending entirely on the host machine setup.
Open docs pageMemory
Memory docs help when users want to understand how context persistence, recall, or session continuity fits into DeepSeek TUI workflows.
Open docs pageOperations Runbook
Operations runbooks matter more to maintainers than casual users, but they still capture how DeepSeek TUI is expected to behave in repeatable operational scenarios.
Open docs pageRelease Runbook
Release runbooks help readers who care about how the project ships, what release discipline looks like, and how updates are expected to flow.
Open docs pageCapacity Controller
Capacity controller docs matter when users want to understand throttling, coordination, or workload balancing inside more advanced agent behavior.
Open docs pagev0.8.8 Coordinator Prompt
Coordinator prompt docs are highly specific, but they help readers who want insight into orchestration behavior rather than end-user setup alone.
Open docs pageArchitecture and History
Docs topics grouped by search and reading intent.
Architecture
Architecture pages matter when users want to understand how DeepSeek TUI is structured beyond install and first-run usage.
Open docs pageLocalization
Localization docs matter because multilingual support quickly becomes relevant once a CLI project grows beyond one language community.
Open docs pageLegacy Rust Audit 0.7.6
Legacy audit notes are more niche, but they still help users who track DeepSeek TUI stability, technical debt, or historical implementation context.
Open docs pagev0.7.5 Implementation Plan
Implementation plan docs are historical, but they still help readers who want to track how DeepSeek TUI decisions turned into actual shipped structure.
Open docs pageCompetitive Analysis
Competitive analysis is useful when the real search intent is not setup, but product positioning and how DeepSeek TUI compares with adjacent agent tools.
Open docs pageAccessibility
Accessibility notes explain how DeepSeek TUI should stay usable in keyboard-first terminal workflows and where interface choices can create friction.
Open docs page