Your pull requests, on the tasks they belong to
Connect GitHub and every PR shows up on its PerspecTask task: open or merged, CI passing or failing, approved or not, with a one-click link to the preview deploy. Link a PR by putting the task's code in its branch name or title. It updates live, so your task list tells you where the code is.
Add dark mode to the app
Created the task “Add dark mode” in PerspecTask and started on it.
Finished. I moved it to Waiting so you can review it.
Opened pull request #42.
The preview build is on its way.
Checked the preview, looks good. Merge it.
Merged #42. The task is done.
In Progress
Weekly digest email
Export invoices as CSV
Waiting
Pricing page copy
Completed
Add dark mode
Stripe webhooks
What the GitHub integration shows
Each linked PR appears as a small chip on the task card, in GitHub's own colors, with a dot for the combined CI result of its latest commit. The task window lists the PR title, repository, review decision and preview deploy, and lets you link another PR or unlink one. A task can have several PRs, and a PR can belong to several tasks.
Week 44
Oct 26 – Nov 1
Fix the login redirect
#42Preview
Acme app
Weekly digest email
#41
Acme app
Pricing page copy
#40Preview
Acme app
Export invoices as CSV
#38
Acme app
Stripe webhooks
#39
Acme app
- Open
- Draft
- Merged
- Closed
- Checks passed
- Checks failed
How to link pull requests to tasks
Install the GitHub app
In PerspecTask, open Account, then GitHub, and click Connect. You pick the account or organization and exactly which repositories PerspecTask can read. The app only asks for read access.
Name the PR after the task
Every task has a code like pt-a3f91c2. Put it in the branch name or the PR title, or paste the PR link into the task. The PR shows up on the task as soon as it is opened.
Watch it from your task list
The PR chip on the task card shows open, draft, merged or closed, with a dot for CI. Click it to jump to GitHub, or click Preview to open the deploy without opening the task.
AI agents link their own PRs
A coding agent that works from your PerspecTask tasks reads the task with the CLI or the MCP server, gets its pr_token, and names the branch or PR with it. You hand out tasks, the agent opens PRs, and the results line up on your board without anyone copying links around. For the rare manual case, the API can list, link and unlink a task's pull requests.
pt tasks a3f
# { "id": "a3f", "pr_token": "pt-a3f91c2", ... }
git switch -c feat-fix-login-pt-a3f91c2
gh pr create --title "Fix login [pt-a3f91c2]"
pt tasks prs a3f
# [{ "number": 42, "state": "open", ... }]Frequently asked questions
- How do I link a GitHub pull request to a task?
- Connect GitHub under Account in the PerspecTask app, then put the task's code (for example pt-a3f91c2) in the branch name, the PR title or the PR description. The PR links itself when it is opened. You can also paste the PR URL into the task, or use Pull requests in the task menu.
- What does PerspecTask show about a pull request?
- The PR title, repository and number, whether it is open, a draft, merged or closed, the combined CI result of its latest commit (GitHub Actions check runs and commit statuses), the review decision (approved or changes requested), and the latest preview deployment from providers like Vercel, Netlify or Cloudflare Pages.
- Why doesn't my pull request show a preview link?
- PerspecTask reads the preview link from the deployments your host reports to GitHub. Vercel only reports them when the project's deployment_status events are on: in Vercel, open the project, then Settings, Git, and turn on deployment_status Events. The link shows up from the next push. Other hosts work the same way, as long as they create GitHub deployments for your pull requests.
- Does it update by itself?
- Yes. GitHub sends PerspecTask a webhook whenever the PR, its checks, its reviews or its deployments change, and every open PerspecTask tab and device updates within a second or two. There is nothing to refresh.
- What access does the GitHub app need?
- Read-only access to pull requests, checks, commit statuses, deployments and repository metadata, only on the repositories you select. It cannot push code, comment, merge or change settings. You can change the repository list or uninstall it on GitHub at any time.
- Can someone else link their pull request to my tasks?
- Automatic linking only happens for pull requests you opened, or for PRs on your own repositories written by people with write access to them. A stranger's fork PR with your task code in it does not link. Linking by URL also checks that your GitHub account can read that repository.
- Can an AI agent link its pull requests?
- Yes. An agent using the PerspecTask CLI or MCP server reads the task, gets its pr_token, and puts it in the branch name or PR title when it opens the PR. The PR then shows up on the task with no extra step. The API also has endpoints to list, link and unlink pull requests.
- Are pull request details end-to-end encrypted?
- No. Your tasks can stay end-to-end encrypted, but the link between a task and a PR (repository, number, title, state) is stored in plaintext, because the server has to match incoming GitHub webhooks to it. Nothing from an encrypted task is sent to GitHub.
See your code where your goals are
Connect GitHub from your account page, choose the repositories, and the next PR with a task code lands on its task.
