# GetPullRequest

> GetPullRequest (GPR) is a developer workflow platform that connects issue trackers, Git hosting platforms, communication tools, and coding agents running on your local machine. GPR works with Jira, GitHub, GitLab, Slack, Claude Code, Codex, Cursor, and other ACP-compatible coding agents to orchestrate software development tasks from assignment through pull request. It runs coding work in your own development environment, verifies changes before creating a pull request, and lets you monitor agent progress, review changes, and merge from your phone.

- [Install GPR](https://getpullrequest.com/docs/get-started/install-gpr.md): Install the gpr CLI on macOS, Linux, or Windows.
- [Connect your machine](https://getpullrequest.com/docs/get-started/connect-your-machine.md): Pair a local directory with the GPR mobile app using gpr setup.
- [Connect GitHub](https://getpullrequest.com/docs/get-started/connect-github.md): Authorize GitHub so GPR can sync issues and open pull requests.
- [Connect a coding agent](https://getpullrequest.com/docs/get-started/connect-a-coding-agent.md): Install an ACP coding agent on the paired machine and verify it with gpr discover.
- [Run your first task](https://getpullrequest.com/docs/get-started/run-your-first-task.md): Create a task on the board and watch the agent work on your paired machine.
- [Overview](https://getpullrequest.com/docs/how-gpr-works/overview.md): How GPR pieces fit together: phone, backend, daemon, agents, and git.
- [Tasks](https://getpullrequest.com/docs/how-gpr-works/tasks.md): What a GPR task is, how the pipeline runs, and how board lanes map to status.
- [Workspaces](https://getpullrequest.com/docs/how-gpr-works/workspaces.md): Workspaces bind a directory on a machine to GPR execution settings.
- [Machines](https://getpullrequest.com/docs/how-gpr-works/machines.md): A machine is the paired computer that runs the gpr daemon.
- [Agent sessions](https://getpullrequest.com/docs/how-gpr-works/agent-sessions.md): ACP sessions link the phone to a coding agent process on the daemon.
- [Pull requests](https://getpullrequest.com/docs/how-gpr-works/pull-requests.md): How GPR opens PRs and what is authoritative when GitHub is connected.
- [Assign a task](https://getpullrequest.com/docs/guides/assign-a-task.md): Create or sync a task and send it to a paired workspace agent.
- [Monitor progress](https://getpullrequest.com/docs/guides/monitor-progress.md): Track board status, session output, and daemon logs while a task runs.
- [Review and merge a pull request](https://getpullrequest.com/docs/guides/review-and-merge.md): Review agent diffs from the phone and merge when GitHub is connected.
- [Handle task failures](https://getpullrequest.com/docs/guides/handle-task-failures.md): Recover from errored, interrupted, and waiting-for-machine states.
- [Work from your phone](https://getpullrequest.com/docs/guides/work-from-your-phone.md): What you can do in the GPR mobile app without sitting at the machine.
- [Manage multiple machines](https://getpullrequest.com/docs/guides/manage-multiple-machines.md): Run more than one paired machine or workspace without stealing tasks.
- [GitHub](https://getpullrequest.com/docs/integrations/github.md): Connect GitHub for issues, pull requests, and merge enrichments.
- [Jira](https://getpullrequest.com/docs/integrations/jira.md): Connect Jira to sync issues onto the GPR board.
- [Slack](https://getpullrequest.com/docs/integrations/slack.md): Connect Slack to create GPR tasks from conversation.
- [Claude Code](https://getpullrequest.com/docs/integrations/coding-agents/claude-code.md): Use Claude Code as an ACP coding agent with GPR.
- [Codex](https://getpullrequest.com/docs/integrations/coding-agents/codex.md): Use Codex CLI as an ACP coding agent with GPR.
- [Cursor](https://getpullrequest.com/docs/integrations/coding-agents/cursor.md): Use Cursor Agent over ACP with GPR.
- [ACP-compatible agents](https://getpullrequest.com/docs/integrations/coding-agents/acp-compatible-agents.md): How GPR discovers and launches agents that speak Agent Client Protocol.
- [CLI](https://getpullrequest.com/docs/reference/cli.md): Reference for the gpr command-line interface.
- [Configuration](https://getpullrequest.com/docs/reference/configuration.md): Environment variables and on-disk paths for the gpr daemon.
- [agents.json](https://getpullrequest.com/docs/reference/agents-json.md): Optional local file that controls how the gpr daemon launches coding agents.
- [Task states](https://getpullrequest.com/docs/reference/task-states.md): Canonical task status, phase, and checkpoint values.
- [Troubleshooting](https://getpullrequest.com/docs/reference/troubleshooting.md): Common GPR setup and runtime failures with concrete fixes.
- [How local execution works](https://getpullrequest.com/docs/security/how-local-execution-works.md): Why agents run on your machine and what the cloud does.
- [Permissions](https://getpullrequest.com/docs/security/permissions.md): How ACP tool permission requests are approved during sessions.
- [Data and connectivity](https://getpullrequest.com/docs/security/data-and-connectivity.md): What connects where, and what data moves between phone, cloud, and machine.
- [Security FAQ](https://getpullrequest.com/docs/security/security-faq.md): Short answers to common security questions about GPR.