Configuring dsh-codex-connect
DeepSeek Harness loads dsh-codex-connect into a selected profile. Open Settings → Plugins → Plugin configuration → Codex Connect to start the separate ChatGPT OAuth login and manage optional capabilities. The README does not document named configuration keys or environment variables. A new installation displays Not signed in; after browser approval it displays Signed in.
The bundle is additive. DeepSeek Harness keeps the current default model and global search route. Standalone search, view_image and image generation are disabled until explicitly enabled. When an eligible GPT Codex model is selected, the Composer exposes a conversation-scoped Fast Mode toggle and a weekly-quota indicator.
Commands
dsh web starts the web UI for the selected profile. The documented manual update command is dsh plugin --profile web update dsh-codex-connect; web can be replaced with the profile name in use. The plugin does not execute upgrade commands automatically. After an update, restart the profile's DeepSeek Harness Web process if the running process still reports the old version.
Compatibility and updates
The DeepSeek Harness Web server periodically checks public package metadata and verified-compatibility.json from the repository. That file records exact plugin and DeepSeek Harness version pairs. The status can be green for a verified pair, yellow when the latest plugin should be installed first, red when no matching record exists, or gray when the version is unrecorded or the public check fails. A newer-version notice shows user-facing changes and technical release notes, but updating remains manual.
Requirements and limits
A working dsh installation, a ChatGPT account with the required subscription access, and a browser capable of completing OAuth approval are required. If an embedded WebView blocks the sign-in window, the displayed Open ChatGPT sign-in page link opens the flow in the system browser. The plugin does not convert a ChatGPT subscription into an OpenAI Platform API credential.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub