DeepSeek-TUI
The project previously cataloged as DeepSeek-TUI is now Codewhale. Its README says it preserves earlier configuration and session compatibility while becoming provider-neutral and independently maintained, without affiliation to a model provider. It can read a repository, edit files, run commands and inspect results using a hosted or local model you connect.
Connect a model before evaluating the agent
Codewhale's terminal interface and headless command are clients of the same runtime, with a local browser client also described. The repository lists hosted providers and local-model routes through Ollama, vLLM and SGLang. A downloaded program does not include unlimited inference: hosted providers require access and incur their own charges, while local models need suitable running infrastructure.
The current README describes a launch state with no model connected and a provider picker. The installation guide records older version-specific behavior where a missing key could leave the interface unresponsive. Check the installed version against the documentation before troubleshooting a model connection. A screenshot of a development build or a changelog entry is not proof that the feature exists in the latest published download.
Distinguish planning from permission posture
The README describes Plan mode as exploration without file changes or shell execution, while Work mode permits changes. Approval posture is a separate control. The installation guide says default Ask posture applies workspace edits and shows a diff, but asks before shell commands. Do not read the word Ask as a guarantee that files remain unchanged. Reasonix also separates planning from tool permissions and describes approval for reads, writes and commands. Comparing those boundaries is more useful than assuming similarly named modes grant the same access.
Review proposed actions and inspect the resulting diff and tests. Keep important existing work recoverable before a tool can edit it. The project describes optional operating-system sandboxing where supported, but permissions and platform support vary. Computer Use has additional access requirements; an included plugin is not evidence that those permissions are enabled or appropriate for every machine.
Match the installation and update path
The repository recommends published release binaries, with package-manager routes also documented. The installation guide distinguishes direct-install updates from npm, Cargo and Homebrew installations, which their package managers continue to own. Confirm which executable your terminal resolves when more than one installation is present.
The guide also identifies aggregate telemetry enabled by default and an opt-out, and describes plaintext file-backed keys on its tested Linux setup. Those details matter when deciding what repository material and credentials the agent may access. A diagnostic command completing successfully does not necessarily establish that a provider key works. Use the documented authentication status and connection checks for the installed version, without exposing credentials in shared command logs.