leeguooooo

ChatGPT Use — Development skill for Claude Code

Development community

Turn your ChatGPT web subscription into a coding-agent backend — no API key, no Codex billing.

How to install ChatGPT Use

This entry records only its repository, not the path inside it, so there is no exact command to give. Open leeguooooo/chatgpt-use and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What ChatGPT Use does

Turn your ChatGPT web subscription into a coding-agent backend — no API key, no Codex billing. Built on chrome-use.

Alternatives in Development

Ccusage — CLI for analyzing Claude Code/Codex usage from local JSONL files 11.8k ★
Ds Harness Remote — 基于 DeepSeek Harness 插件机制构建的远程访问方案，通过低延迟、端到端加密的 P2P 网络，支持使用 PC、移动端和 Web 随时访问本地设备上的DSH 、CodeX、Cursor、Claude Cod 860 ★
Mem0 Chrome Extension — OpenMemory Chrome Extension: Long-term memory for ChatGPT, Claude, Perplexity, Grok etc 671 ★

README

chatgpt-use

Turn your **ChatGPT web subscription** into a coding-agent backend — **no API key, no Codex billing.** Built on [`chrome-use`](https://github.com/leeguooooo/chrome-use), same lineage as [`chatgpt-imagegen`](https://github.com/leeguooooo/chatgpt-imagegen) and [`cookie-use`](https://github.com/leeguooooo/cookie-use).

🧪 Experimental · v0.0.2 released. Browser main line (ask · structured delegation · --model pro · handoff) is live-verified; install with the one-liner below.

![chatgpt-use](assets/hero.png)

Your Plus / Pro plan already includes a chat surface you've paid for. `chatgpt-use` drives that **logged-in web conversation** through `chrome-use` — exactly the way `chatgpt-imagegen` drives image generation — and wires it into your local machine. The result: a coding agent (Claude Code, Codex, anything) can hand work to ChatGPT, and ChatGPT can read and edit your project files.

The web chat surface is **not the API** and **not the Codex-usage bucket**. So the work runs on quota you've *already bought* — that's the whole point.

Why this exists

	API / `codex exec`	chatgpt-use (web)
Auth	`OPENAI_API_KEY` or Codex login	your normal browser login
Billing	per-token API spend / Codex-usage limit	your flat monthly subscription
File access	you build context plumbing	`read_file` tool — no tunnel
Setup	keys, env, gateways	`chrome-use` + a logged-in tab

If you're already paying for ChatGPT Plus/Pro and *also* burning API credits or Codex-usage limits from your coding agent, this closes the gap: route the cheap-and-already-paid work to the browser.

Three modes

`chatgpt-use` is one engine — a `chrome-use`-driven **channel** to the ChatGPT web conversation (send a message, wait for the reply, parse it) — exposed three ways depending on **who's the brain**.