Skip to main content

Projects

A project is a scoped workspace inside Genesis: its own files, its own knowledge, and its own settings. Sessions run inside a project, so work on different efforts stays separated.

What a project scopes​

  • Files — uploads and generated files live in the project.
  • Knowledge — documents you add are retrievable inside the project.
  • Settings — model preferences and tool configuration can be set per project instead of globally.
  • History — a project's sessions belong to it; switching projects switches context.

Projects keep unrelated work apart: a client engagement, a personal research line, and a coding effort can each hold their own files and knowledge without leaking into each other.

Locally vs Mother One​

Project behavior is the same on every Mother machine — on a Mac client and on Mother One alike, projects live on the Mother machine itself. Nothing is kept only in the client app.

Git support​

For coding work, a project can track a Git repository: clone or point a project at a repository and Genesis works with it — reading files, committing to branches, and reviewing diffs as part of sessions.

  • Commits are attributed to the account you configured for the project.
  • The repository history stays in the project; switching projects switches repositories.
  • Standard remotes (including private ones) work — credentials are held in the project's settings, Owner-managed.