[Plugin / 插件] dsh-codex — ChatGPT OAuth, Codex search, and image input / ChatGPT 登录、搜索与图片输入 #518
Yan-Zero
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
中文
大家好,我做了一个独立的 dsh 插件
dsh-codex,可以通过 ChatGPT OAuth 登录,在 DeepSeek Harness 里使用账号可用的 Codex 模型。我平时主要在 Web profile 里用 dsh,所以把登录、额度和图片都接进了现有界面。目前包里有这些功能:
$DSH_HOME/.openai-codex-auth.json;web_search工具访问 Codex 独立搜索,并保留普通文本与引用历史;view_image也能读取本地路径和 HTTP(S) 图片;安装:
启动后打开 设置 → OpenAI Codex → 使用 ChatGPT 登录。无界面环境可以运行:
dsh plugin --profile web exec dsh-openai-codex login --device-code插件使用 ChatGPT Codex 后端。模型权限、额度和可用性由 OpenAI 账号与套餐决定;它不会生成通用 OpenAI API Key。dsh 的 shell、文件系统、skills、MCP、subagents 和权限系统仍由当前 profile 提供。
0.2.1,依赖与测试环境对齐 dsh0.1.0-rc.6如果你愿意试一下,我很想了解浏览器回调、headless 登录、图片附件和搜索记录在不同环境里的表现。协议和凭据生命周期也写在仓库的 design 文档里,欢迎直接提 issue。
English
Hi! I’ve been working on an independent dsh plugin called
dsh-codex. It signs in through ChatGPT OAuth and makes the Codex models available to a DeepSeek Harness profile.I use dsh mostly through the Web profile, so the package covers the account flow and a few everyday Codex features in the existing UI:
$DSH_HOME/.openai-codex-auth.json;web_searchtool, with regular text and citation history;view_imagetool for local paths and HTTP(S) URLs;Install it into a Web profile:
Then open Settings → OpenAI Codex → Sign in with ChatGPT. For a headless machine:
dsh plugin --profile web exec dsh-openai-codex login --device-codeThe plugin talks to the ChatGPT Codex backend. Model access, quotas, and eligibility follow the OpenAI account and plan; this does not create a general OpenAI API key. Shell, filesystem, skills, MCP, subagents, and permissions continue to come from the active dsh profile.
0.2.1, aligned and tested with dsh0.1.0-rc.6I’d especially appreciate field reports on the browser callback, headless login, image attachments, and search history across compaction. Protocol and credential-lifecycle notes are in the repository’s design document; issues are welcome.
All reactions