Prepare a project for Aegis
Use this after Aegis is installed and the dashboard can start. If you still need to install dependencies, launch the app, or configure server environment variables, start with Installation.
This guide covers the project, Git, account, and tool setup Aegis needs before agents inspect repositories, prepare patches, or call external tooling.
Check Git Identity
Confirm Git is installed and configured:
git --version
git config --global user.name
git config --global user.email
Set identity if needed:
git config --global user.name "Your Name"
git config --global user.email "you@example.com"
Prepare Repository Access
Clone projects into local paths Aegis can read:
git clone git@github.com:your-org/your-repo.git
Before running coding workflows, confirm:
- the repository opens locally;
- the default branch is current;
- dependencies can install;
- tests or verifiers can run from the terminal;
- uncommitted work is understood before the agent starts.
Configure GitHub Access
For GitHub-backed workflows, install and authenticate GitHub CLI if you plan to create branches, inspect PRs, or use GitHub automation:
gh auth status
If not authenticated:
gh auth login
Confirm the repo remote:
git remote -v
Configure GitLab Access
For GitLab-backed workflows, configure SSH access or a credential manager for Git operations. If you use the GitLab CLI, confirm it can reach your instance:
glab auth status
If glab is not used, make sure normal git fetch, git pull, and git push work from the terminal.
Install Project Tooling
Install the tools your workflows expect, such as:
- package managers;
- test runners;
- linters;
- browser automation dependencies;
- cloud or API CLIs;
- local model runtimes;
- image, document, or media tools used by specific workflows.
Run the same verifier command you plan to give Aegis:
npm test
or:
npm run build
Safe Defaults For Agent Work
Before giving an agent a repository:
- start with read-only analysis;
- use a small target scope for coding;
- keep approval gates enabled for repo writes;
- review existing uncommitted changes;
- choose a verifier command that catches real mistakes;
- avoid giving connector write access until the workflow is proven.