GDP is not a coding model or an unrestricted remote shell. It is the control layer that binds AI requests to exact targets, local policy, authorized execution, and fresh evidence.
Understand the control-plane role
Git Diff Patcher (GDP) is the local-first control plane around AI-assisted software work. An AI can inspect bounded context and propose patches, checks, or other actions; GDP keeps target identity, policy, execution routing, evidence, and recovery separate from the model's reasoning.
That separation is what lets GDP support more automation without treating a capable model as automatically authorized to change the machine.
A request is not permission.
A technical capability is not the same as authority to use it for the current task.
A model saying that something worked is not execution evidence.
Know the connected product surfaces
GDP is a connected product family rather than one patch dialog or one MCP endpoint.
GDP Desktop owns local repository targeting, patch and terminal policy, rollback protection, and local execution evidence.
GDP Browser is GDP's owned Chromium workspace for normal web use and governed AI/browser workflows.
Browser Companion connects supported conversations in an external browser to bounded GDP relay, export, and continuation workflows.
GDP Cloud and the hosted gateway coordinate account identity, transport, sessions, queueing, and bounded hosted services without becoming the local repository execution authority.
GDP Ops is the mobile mission-control surface for observing work and using bounded operations; it is not a general mobile IDE or shell.
Follow the normal GDP loop
Confirm the exact repository, task, or other target before material work.
Read the current bounded context instead of relying on an old conversation summary.
Let the AI propose a patch, check, or other bounded action.
GDP validates the target and preconditions and applies the relevant local policy.
The work waits for review or continues only when the selected local permission envelope allows it.
Read fresh repository, diff, check-run, or other GDP evidence for what actually happened.
Continue from the first step that is not already proven.
Know what GDP is not
GDP is not a foundation model, an unrestricted remote shell, or a general-purpose filesystem browser. AI-facing repository tools remain bounded to repositories intentionally exposed through GDP, and hosted transport does not silently become local apply, terminal, commit, push, reset, or clean authority.
Local-first describes GDP's execution and privacy architecture. It does not make billing, license state, source-license choices, or a future packaging model into execution authority, and it does not freeze every future customer-distribution decision.
A queued request, an entitlement, a lineage record, and a confident model answer can all be useful facts without proving that a material local effect occurred.
