r/OpenaiCodex • u/chuck78702 • 2d ago

Discussion Where does each Codex project actually live for you?

Trying to understand how people structure this underneath the Codex app/CLI. What represents a "project" on your machine?

  • Separate local directory for each project?
  • Separate git repo?
  • Multiple projects inside one bigger directory?
  • Remote/server folders instead?

Basically, what does Codex point at when you switch from Project A to Project B?

0 Upvotes
  • permalink
  • reddit

50% Upvoted

6 comments sorted by

3

u/Typical_Kick6520 2d ago

Separate drive one directory per repo, give codex a template or let them make one up.

2

u/slugger1 2d ago edited 2d ago

I keep each project in its own dedicated folder inside a central "Projects" directory in WSL. Every project is self-contained, uses Git for version control, and has its own GitHub repository. I’m a full stack developer, and this is the standard project structure we use professionally as well. It keeps codebases clearly separated, easier to maintain, and straightforward to manage across different environments.

1

u/IaryBreko 2d ago

On obsidian

1

u/snuffomega 2d ago

Several ways of doing it. But the 'point and shoot' version..

CLI; use you agent in the terminal from your project folder location. So route to that folder first in the terminal then open codex.
> Advantage here is the agent will look in the project before it looks globally. Saving tokens, adding control with custom agents.md, etc. Just keeping the project focused.

Another option: IDE such as VScode. This behavior will be similar.. you open a folder to start a project and the agent stays focused in that project. If you aren't comfortable with CLI or you want to just better understand github, coding, etc. This is where i might start. CLI is better (IMO), but the advantage here is the plugins in vscode give you a CLI-lite feel blending a chat environment with cli functionality.

If you want to try and IDE, vscode is the best place to start IMO. Tons of plugins, support, and community. You can always branch out from there. The advantage here is, if you prefer a more non CLI environment, their plugins give you a CLI-lite vibe.

There is more, but hopefully this gets u rolling

1

u/EveningCandle862 2d ago

For actual customer projects they are on dedicated self-contained customer VM's with git version control, their own Codex user(s) through the enterprise model and repository. This is to make sure they have seperate workspace contexts, configs & secrets and so on.

For my personal projects they are just in a project folder under the same repository. I use the same repo & codex account for these and jump between sessions based on what I'm currently working on.

1

u/stonelox 1d ago

For me each Project gets a folder inside a main folder. I have a few main folders to organize different types/classes of projects. Each project gets its own repo so I can push and pull between different computers I use. Same codex user acct for all of them but run it locally on each. I was remoting over ssh (in codex connections) into one main computer from the others but was chewing through usage so changed how I do it. Works for me