Repository Workflows
Repository mode keeps GitHub and GitLab work in one place. Use it when you want to start from a repository, issue, merge request, or inbox item instead of a free-form chat.
Connect a Git Provider
Open Repos from the sidebar. If the selected Git server requires OAuth and your account is not connected, the app prompts you to connect the provider. After connecting, refresh the repository list.
Supported repository sources depend on your deployment configuration. Hosted Agentrix commonly includes GitHub, and private deployments can add GitLab servers.
Repository List
The repository panel lets you:
- Switch between configured Git servers.
- Sync repositories from the selected server.
- Search across repositories.
- Filter the current server by owner or organization.
- See inbox badges for repositories that need your attention.
Select a repository to open its workspace.
Repository Workspace
Each repository has these tabs:
| Tab | What it shows |
|---|---|
| Inbox | Issues, merge requests, or repository events that need user attention |
| Tasks | Agent tasks associated with the repository workspace |
| Issues | Open issues from the Git provider |
| MRs | Open pull requests or merge requests |
Use the refresh action when you need the latest provider state.
Inbox
Inbox items come from repository integrations and webhooks. They give you a queue of issues or merge requests that need review, follow-up, or agent work.
Open an inbox item to jump to the matching issue or merge request view. If the inbox is empty, no repository item currently needs attention.
Issues
The Issues tab lets you list and open issues. Depending on provider support and permissions, you can also create issues from Agentrix.
An issue view can show:
- Title, description, labels, and assignees.
- Comments from the Git provider.
- Comment creation from Agentrix.
- GitLab thread replies where the provider exposes thread IDs.
- A link back to the issue on the Git provider.
Work on an Issue
Issue work uses a root issue workspace with subtasks. This keeps the issue overview separate from the implementation attempts.
- Open a repository issue.
- Review the description, labels, assignees, and comments.
- Create a task from the issue workspace.
- Choose the execution environment if the root issue does not already define one.
- Let the agent implement, debug, or verify the issue.
- Open each subtask to review history, artifacts, diffs, and previews.
- Close the issue from Agentrix when the work is complete and your provider permissions allow it.
The app attaches issue context to the task so the agent sees the issue body and selected comments. When you reference issues from the task composer, the app can add citations to the initial message.
Merge Requests
The MRs tab lists open pull requests or merge requests. Open one to review provider metadata and code review context. Agentrix can show merge request status and review discussion data where the provider API supports it.
For GitLab merge requests, review threads can include resolved state. If a thread or comment opens in the provider, use the provider link when you need native controls that are not exposed in Agentrix.
Repository Tasks
The Tasks tab shows tasks bound to the repository workspace. Create repository tasks here when the work is not tied to one issue or merge request.
Use repository tasks for:
- Implementing a feature across several files.
- Running a broad refactor.
- Asking an agent to inspect the repository and produce a plan.
- Verifying a change before opening or updating a pull request.
Repository tasks keep their artifacts under the same review surfaces as chat tasks: history, artifacts, diffs, commits, and previews.
Private GitLab Webhooks
Private GitLab deployments can use the daemon webhook bridge. Configure the GitLab server with the CLI, then add the daemon webhook URL and secret to the GitLab project. See CLI Commands for the full setup.
If your GitLab server is not on the same machine as the daemon, enable daemonControl.allowLanAccess in ~/.agentrix/settings.json, restart the daemon, and restrict network access to trusted sources.