DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to open ChatGPT with terminal access to a project with Web GPT

Open ChatGPT in the browser with terminal access to the current project or a folder you name.

Remote script. The local Worker is exposed through accountless HTTPS forwarding, so ChatGPT can run terminal commands on your machine through that link.

Who it is forA developer who wants to talk through a codebase directly with ChatGPT, with it able to run commands in that project.

The problemExplaining a project to ChatGPT by hand and copying output back and forth is slow.

The outcomeA ChatGPT session opens with terminal access to the chosen project folder.

What you need first

  • Codex with the WebGPT skill installed from https://github.com/Nhahan/WebGPT/tree/main/skills/webgpt
  • A ChatGPT account you can sign in to on the web
  • Permission for the local Worker, accountless HTTPS forwarding, and full terminal access as your OS user for the assigned project
  • A terminal on the machine where Codex runs

Steps

  1. Install the skill by pasting the install prompt from the README into Codex, then let Codex follow references/setup.md.
  2. In Codex, tell it: webgpt open to open ChatGPT for the current project.
  3. To use another project, tell Codex: webgpt open /path/to/project with your project path.
  4. Confirm the project is the one you intended before asking ChatGPT to run anything.

Prompt for your agent

Using the WebGPT repo (Nhahan/WebGPT), run `webgpt open /path/to/project` with the project path <project path>. Expect ChatGPT to open with terminal access to that folder. Verify the session is pointed at the correct project before giving it any task.

Caveat. The README says the project folder is not a sandbox, so ChatGPT has the same terminal access as your OS user in that folder.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page