01 - Repository#
A repository is the foundational object in Helmor. It represents the source project — the file tree, Git history, branches, and context that agents use to perform coding tasks.
What a repository provides#
When you add a repository, Helmor gains access to:
- File tree — browse, search, and open any file in the project.
- Git history — view commits, branches, and tags.
- Branch context — workspaces branch from the repository's default or target branch.
- Diff baseline — agent changes are compared against the repository state.
Local vs. GitHub-connected#
| Mode | What you get |
|---|---|
| Local only | File browsing, workspace creation, agent sessions, local commits. |
| GitHub-connected | Everything above, plus remote branch tracking, account identity, and pull request workflows. |
A local repository is sufficient for isolated agent work and review. Connect GitHub when you need remote collaboration, branch protection context, or PR-based shipping.
Adding a repository#
Open Helmor, click Add Repository, and choose either a local folder or a GitHub import. Helmor detects the default branch and indexes the project. See Add a Repository for the step-by-step guide.
Best practices#
- One repo, many workspaces. Add the repository once, then create separate workspaces for separate tasks.
- Avoid catch-all workspaces. Long-lived workspaces with unrelated changes make review harder and diffs noisier.
- Keep credentials fresh. If your GitHub token expires, reconnect under Settings so remote context stays available.
Related#
- Workspace — the isolated working copy created from a repository.
- GitHub Integration — remote features enabled by connecting your account.