trungbui888/chatgpt_coding — explained in plain English
Analysis updated 2026-05-18
Let ChatGPT Web read and edit code in a local project folder through a secure tunnel.
Run commands, tests, and git operations on your machine at ChatGPT's request with approval controls.
Configure safety modes so risky actions like file deletion require local approval before running.
Point ChatGPT at one project folder while keeping the agent's launcher in a separate directory.
| trungbui888/chatgpt_coding | 100/tab-organizer | addyosmani/devtools-snippets | |
|---|---|---|---|
| Stars | 11 | 11 | 11 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | — | 2021-03-01 | 2013-09-22 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | hard | easy | easy |
| Complexity | 4/5 | 1/5 | 1/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Node.js 18+, a separately downloaded OpenAI tunnel client, and an OpenAI runtime API key with tunnel access.
Local Coding Agent turns a folder on your own computer into a workspace that ChatGPT Web, or any other tool that speaks the MCP protocol, can work inside of directly. Once set up, ChatGPT can read your files, edit code, run commands, check git status and diffs, and report back on the health of the local setup, acting like a coding assistant that operates on your real machine rather than a sandbox. The project ships with a setup control panel you open in a browser to configure everything: which folder to work in, which network ports to use, and how cautious the agent should be. Two safety modes are offered, a safe mode that blocks many risky command patterns, and a balanced mode that allows normal editing and testing but asks for local approval before doing something risky like deleting files or making network installs. The README is explicit that this tool is not an operating system sandbox: it can genuinely read, write, and run commands on your computer, so it should only be pointed at folders you trust. Getting connected involves several pieces: Node.js 18 or newer, a separately downloaded tunnel client from OpenAI that creates a secure connection between your machine and ChatGPT, a runtime API key with permission to use tunnels, and a tunnel ID. After running an install script and placing the tunnel client in the right folder, you start the setup UI, fill in the workspace path and connection details, and save and start the service. From there, you create a custom app inside ChatGPT's settings pointed at your tunnel, after which new chats can call tools exposed by the local agent, such as asking it for information about the connected workspace. The README also documents a command-line path for people who prefer not to use the browser UI, a table of common error messages and how to fix them, and a test suite for checking the agent's behavior, with a warning not to run the security tests against a real project folder since some of them intentionally test deletion and blocking behavior.
A local server that lets ChatGPT Web or other MCP clients read, edit, and run commands on a folder on your own computer.
Mainly JavaScript. The stack also includes JavaScript, Node.js, MCP.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.