Overview
When an AI agent finishes its work, you’ll typically want to open a pull request from the task branch. Whim automatically detects PRs created from task branches and links them back to the corresponding task, giving you real-time status tracking in the dashboard.Creating a pull request
There are two ways to create a PR from a task branch:From the AI agent
The most common approach is to ask the AI agent to create a PR as part of its task. Include instructions like “open a PR when done” in your prompt, and the agent will usegh pr create to open a pull request from the task branch.
From GitHub
You can also create a PR manually in GitHub. Navigate to your repository, select the task branch (e.g.,whim-ww-42), and open a pull request as usual. Whim detects the PR automatically via webhook.
Whim links PRs to tasks by matching the branch name. Any PR opened from a
whim-* branch is automatically associated with the corresponding task.PR status tracking
Once a PR is linked to a task, Whim tracks its state in real time:| Status | Meaning |
|---|---|
| Draft | PR is open but marked as a draft |
| Open | PR is open and ready for review |
| Merged | PR has been merged into the target branch |
| Closed | PR was closed without merging |
PR display in the UI
Linked PRs appear directly on the task in both the task list and detail views:- A status badge shows the current PR state with a color-coded indicator
- Clicking the badge opens the PR on GitHub in a new tab
- The PR number is displayed alongside the status for quick reference
Review workflow
Whim fits into your existing code review process:- Task completes — the AI agent finishes work and optionally opens a PR
- Review in GitHub — your team reviews the PR using GitHub’s standard review tools (comments, approvals, requested changes)
- Track in Whim — PR status updates flow back to Whim automatically, so you can monitor progress from the dashboard
- Merge — merge the PR in GitHub; Whim updates the task’s PR status to “merged”
Multiple PRs per task
A task can have more than one linked PR. This can happen when:- The agent opens PRs to multiple repositories in a monorepo
- A PR is closed and a new one is opened from the same branch
Branch Isolation
How every task gets its own isolated Git branch.
Task Lifecycle
Understand task states from creation to completion.

