Read your agent's pull or merge request in the session
Your agent says it opened a PR and CI passed. To check that, you switch to GitHub, GitLab, or Azure DevOps, read the diff and checks, then return to the conversation.
Omnigent's Pull Requests panel puts the request description, CI results, comments, and file diffs beside the conversation. You can compare the agent's explanation with the changes before asking it to continue.
Opening the Pull Requests panel from a session: Summary, CI checks, then Changes and file navigation.
Start with a coding-agent session whose workspace is a git checkout on a
supported provider and whose files you can browse. The execution host needs
provider access: GitHub uses the GitHub CLI (gh); GitLab uses glab; Azure
DevOps uses Azure CLI sign-in (az login) or AZURE_DEVOPS_EXT_PAT. For GitHub
in a managed sandbox, have the session owner connect GitHub in Omnigent.
- Open Pull Requests in the workspace rail, or click the PR indicator in the composer's workspace bar when one is available.
- Read Summary for the request description and CI checks. Open Comments for conversation comments.
- Switch to Changes and use the folder tree to jump between file diffs.
If the session has multiple associated requests, use the request selector to choose one.
PR information refreshes when an agent turn ends. While the panel is open and the app is in the foreground, it also polls for PR and CI updates rather than streaming them in real time. For branch-based lookup, polling normally stops once checks settle or the PR closes or merges; tracked PRs continue polling while the panel is focused.
For request tracking and selection, see the Web UI guide.
The panel shows whether the request is open, closed, or merged. It is read-only: it does not post comments, submit approvals, or merge requests.