Git detection
On startup, Codeg locates your Git executable using the systemwhich (macOS/Linux) or where (Windows) command. The detected path and version are shown in Settings → Version Control.
If Codeg cannot find Git, or if you need to use a specific Git binary (e.g., a version installed in a non-standard location), enter the full path in the Custom Git Path field and click Save. Codeg validates the path by running git --version before saving.
Remote accounts
Codeg stores remote Git credentials so agents and built-in Git operations can authenticate when pushing to or pulling from remote repositories. Credentials are stored in your OS keyring — never in config files or logs. Codeg separates accounts into two categories:- GitHub accounts
- Other Git servers
GitHub accounts authenticate using a personal access token (PAT). Codeg validates the token against the GitHub API and displays your username, avatar, and granted OAuth scopes.To test whether a stored token is still valid, click Test Connection on the account row. Codeg re-validates the token against the GitHub API in real time.
Enter the server URL
For github.com, leave the server URL as
https://github.com. For GitHub Enterprise, enter your enterprise URL, e.g., https://github.example.com. Codeg automatically routes to api.github.com for github.com and {url}/api/v3 for enterprise.Enter your personal access token
Paste your GitHub personal access token. Codeg calls the GitHub API to verify the token and retrieve your username and scopes.
Set as default (optional)
If this is your primary account for push/pull operations, enable Set as default. The default account is used when no other account is specified for a remote operation.
Managing accounts
| Action | How |
|---|---|
| Set default | Click Set Default on any non-default account |
| Remove | Click the trash icon; the token is deleted from the keyring and the account is removed |
| Test connection | Click Test Connection to re-validate against the remote API |
Git operations
The Version Control panel in the workspace sidebar exposes all standard Git operations for the open project folder:Basic operations
Basic operations
- Status — view modified, staged, and untracked files
- Diff — inspect line-level changes per file
- Log — browse commit history
- Stage files — add specific files or all changes to the index
- Commit — create a commit with a message
- Push / Pull / Fetch — synchronize with the remote
Branch management
Branch management
- List branches — view local and remote branches
- Create branch — start a new branch from the current HEAD or a specified ref
- Checkout — switch to a branch or commit
- Delete branch — remove a local branch
- Merge — merge a branch into the current branch
- Rebase — rebase the current branch onto another
Stash
Stash
- Stash push — save uncommitted changes to the stash
- Stash list — view all stash entries
- Stash pop — apply the most recent stash entry and remove it
- Stash apply — apply a stash entry without removing it
- Stash drop — delete a specific stash entry
Conflict resolution
Conflict resolution
- View conflicting files — list files with merge conflicts
- Resolve — mark a file as resolved after editing
- Continue — continue a merge or rebase after resolving conflicts
- Abort — cancel the current merge or rebase operation
Remote management
Remote management
- List remotes — view configured remote URLs
- Add remote — register a new remote by name and URL
- Remove remote — unregister a remote
- Set remote URL — update the URL of an existing remote
- Clone — clone a repository into a local directory
Git worktrees
Git worktrees
Codeg includes first-class support for
git worktree, enabling parallel development across multiple branches without switching. You can list, add, and remove worktrees from the workspace UI. Each worktree opens as a separate project folder in Codeg, with its own agent sessions and terminal.