Clarify terminology: Project vs Workspace vs Group

[shpoont]

Hi! First off: Codex Monitor is great — thanks for building it.

I’m confused about terminology: the UI/docs seem to use Project and Workspace interchangeably, and Group sometimes appears as a “project group” / “workspace group”.

Could you clarify the intended meaning / hierarchy of these terms?

Specifically:

• Is a “Project” a distinct concept from a “Workspace”, or just a UI label for the same saved working directory?
• Does “Open Project” behave differently than “Add Workspace” in terms of persistence and app-server lifecycle?
• Are “Groups” purely organizational metadata for workspaces/projects, or do they affect behavior in any way?

Concrete example:

• I have a tree under ~/Work with multiple repos (and some non-repo folders). I can add ~/Work as a Project and ~/Work/some-repo as a Workspace, but it’s unclear what the intended organization model is.

If there’s an existing doc/section that defines these terms, a link would be appreciated.

[Dimillian]

Project/Workspace are the same thing, it's just a folder you add to Codex Monitor so that it can work in. I suggest adding each independent working project folder, and if you add a subfolder, there is a UI to point it at your desired related git repo if needed.

I'll try to improve the copy.

[Dimillian]

And groups are an extra UI layer, so you can group workspaces in the sidebar.