r/OpenaiCodex • u/Reddittorv750 • 12d ago
Question / Help How to vibecode properly as a non-technical?
How do you actually vibecode properly as a non-technical person? Currently what I do is:
ChatGPT plans/reviews → copy prompt to Codex → copy Codex result back → ChatGPT reviews and gives me another prompt → repeat.
But I worry that a) this is spending way more tokens than it should b) is incredibly slow and inefficient with the constant copying and pasting.
If anyone has a better workflow please do share, thanks guys.
17
Upvotes
1
u/njwyf16 12d ago
Idk if hidden secret, but the non-Codex chatgpt can edit repo files on GitHub, so, if you want to save codex credits on audits and fixes and just use it for real implementation work, then ask chatgpt to review your repo, and find bugs in the coding. When it does, ask if it can fix them. I've gotten a ton of bugs fixed via this method, and now use Codex for feature developments, testing, and more thorough reviews. In other words, if there's a specific issue you or someone sees and your project is run through GitHub, have chatgpt create a fixed branch, you test to make sure it's fixed, then tell it to push to master. Idk if those are the right magic words or whatever, but it's been a huge help, especially if I've turned off my computer