Non-Git projects
Superconductor opens plain folders that are not Git repositories. Plain folders hold notes, prototypes, generated project folders, or codebases not yet tracked with Git.
Non-Git project support is experimental. Plain folders support local navigation, file browsing, terminals, and agent sessions. Command-palette file search, Git-backed review, and branching features stay unavailable until the folder becomes a Git repository.
Enable non-Git projects
Section titled “Enable non-Git projects”Open Settings, go to Experimental, and enable Non-Git projects.
You can also enable the setting when adding a plain folder. Superconductor asks whether to enable experimental non-Git projects before continuing.
Existing plain-folder projects stay visible if you later disable the setting.
Add a plain folder
Section titled “Add a plain folder”Add the folder the same way you add a repository. Superconductor checks the selected path before registering it:
- Folders above your home folder are blocked.
- Large plain folders may show a warning because they produce noisy file events.
- System folders and your home folder may show warnings.
- Folders with unreadable or corrupt Git metadata are handled separately from plain folders.
What works
Section titled “What works”In a non-Git project, you can:
- Browse files in the project file tree.
- Open terminals in the project folder.
- Start terminal or chat agent sessions.
- Keep session history attached to the project.
- Use the project folder for exploration or editing.
Agent tools still run locally with their own provider credentials. Superconductor does not add Git history around a plain folder automatically.
What requires Git
Section titled “What requires Git”Plain folders do not support git worktrees. Features that depend on Git history, branches, diffs, pull requests, or merge requests require a Git repository.
Git is required for:
- Isolated task directories backed by git worktrees.
- Branch creation and target-branch comparisons.
- Built-in diff review against a base branch.
- Commit, PR, MR, checks, and forge-aware status.
- Cleanup flows that remove a worktree after a branch is merged or abandoned.
If you try to create a git worktree from a plain folder, Superconductor shows an Initialize Git first message.
Initialize Git later
Section titled “Initialize Git later”To turn a plain folder into a repository, use the project menu’s Initialize Git action. Superconductor creates Git metadata in the selected folder so branch tracking and worktree creation become available.
Superconductor will not initialize Git in reserved system folders or in your home folder. Large folders may require confirmation before Superconductor creates Git metadata.
After initializing Git, create an initial commit before you rely on standard branch and review workflows.