Guard quickstart for your own agent
Use Dengel Guard when a coding agent you already use makes a change in your checkout. This quickstart uses standard Git for the agent and the Dengel panel for proposal, verification, and human review.
Access required. Ask your early-access contact to confirm Guard proposal review and independent verification for your Dengel Git repository. You need a project Git access token, a teammate who can propose changes, and an owner or maintainer who can authorize verification. The proposal identifies who can approve landing. A Git-only workspace can follow the Git quickstart through the candidate push. Guard uses a separate verification quote. An authorized person reviews the limits and covers any charge. See pricing and limits.
1. Give the agent a task and a Git checkout
Clone the repository over HTTPS using the URL and Git credentials from Code, as shown in the Git quickstart. In a clean clone where origin is the intended Dengel repository, start from the current main:
git fetch origin main && git switch -c guard/first-change FETCH_HEAD
Give the agent one small change, its allowed scope, and how to check it. Ask it to review the diff, run the project's local checks, and commit only that change. Use a project Git credential through an approved credential helper. Keep human approval and billing credentials out of the agent's environment.
If the repository has no approved checks, an owner or maintainer can open Code, then Checks and Edit checks. Choose commands that can run in the verifier environment and select Approve these checks before asking Guard to verify.
2. Push the candidate and open a proposal
After reviewing the local commit, push it to a unique candidate branch:
git push origin HEAD:refs/heads/candidate/guard-first-change &&
git rev-parse HEAD &&
git ls-remote --exit-code origin refs/heads/candidate/guard-first-change
Compare the local commit ID to the first field returned by git ls-remote. Hand off the repository, full candidate ref, commit ID, purpose of the change, and local check results. In the panel, a teammate opens Code, finds that branch, enters what the change is for, and selects Propose for review. In Changes, open the resulting proposal and confirm its head commit matches the handoff. Pushing stores the branch. Creating the proposal opens the review.
3. Verify the exact proposal
On the proposal page, review What changed, the risk summary, and Checks. An owner or maintainer reviews the displayed price and time limits and selects Run checks. If funding is refused or the quote changes, review the current price and available credits before retrying. Local checks are useful context. Guard uses the independent results for the exact proposal.
Wait for Ready for approval. If the verdict is failed or inconclusive, open the check results and follow the suggested remediation. If the base has moved, update the change against the new base, push it under a fresh candidate ref, and open a new proposal so Guard can verify it again.
4. Land and record the result
The human listed under Who must approve reviews the proposed change and checks. When ready, they select Approve and merge, then Confirm and merge. On the landed proposal, find the signed Receipt and its ID in Technical record. Read main again from the remote to confirm where the branch landed:
git ls-remote --exit-code origin refs/heads/main
If main has advanced since, check that the landed commit is in its history.
The agent's handoff ends with the candidate and evidence. The human opens the proposal, approves any verification spend, and confirms the merge.
The CLI reference also covers submitting with a project submit token in an enabled workspace. See the API reference for proposal endpoints and token scopes.
