Agent and pull request

Symptom

The inbox status is Failed, the client never gets a preview, or a new request is refused before the agent starts.

Causes

The agent run failed

Confirm. The status is Failed. Home is red. The line is the project name, then "Agent run failed", unless the kind is Build failed, Pull request conflict, or Repository access. The request can also be labeled Agent found nothing to change, Agent error, Timed out, or Unknown error.

The client sees a short line, not the log. Build failed uses "The preview couldn't be prepared." and the team name "has been notified." Nothing to change: "We couldn't find that element on the site. Which page is it on?" Other failures: "A team member will look at this." After a second failure: "A team member is looking at this."

Fix. Open the request and press Retry. The dialog says "Start the agent again. Extra context is added to this attempt only." A conflict or a timeout is retried once automatically. Retry is disabled on any other status with "Only failed requests can be retried." See Quotes and merges.

No pull request, because GitHub cannot write to the repo

Confirm. The failure label is Repository access, or the project checklist says "The GitHub App is installed, but it cannot open pull requests yet." The reason is "Grant contents:write and pull_requests:write on the GitHub App." Installing the widget from the dashboard can also say "Missing GitHub permissions. Re-authorize the GitHub App with contents:write and pull_requests:write." If the repository was removed from the GitHub App installation, GitHub answers that the repository is not found or not accessible, and Modifee classifies that as Repository access. Home may also say "GitHub disconnected" when the workspace has no installation.

Fix. Open the GitHub App installation and grant this repository, including contents and pull requests. Then press Retry. If the checklist says "Install the GitHub App and link this project to a repository.", start from Install GitHub App on Projects.

The pull request conflicts with the default branch

Confirm. The label is Pull request conflict. The detail mentions a merge conflict, a rebase, or a push that was not a fast-forward. Modifee retries that kind once.

Fix. If it is still Failed, press Retry. If it stays in conflict, merge or rebase the pull request on GitHub. Approve & merge says "Review required — merge on GitHub." when the diff touches a protected path or deletes a file. See Guardrails. A merge that loses a race with another update returns "That conflicted with the current state." Reload and repeat the action. MDF-REQ-003.

A request limit or the AI allowance was reached

Confirm. Which sentence the client sees:

• "You've reached this month's request limit. Your team can raise it." French: "Vous avez atteint la limite de demandes de ce mois. Votre équipe peut l'augmenter." Monthly request cap on this project is set, and that many non-test requests were already sent this UTC month. The widget shows the sentence, then the link MDF-PLAN-004. Raise or clear the field. See Autopilot and limits and Billing and plan.
• "Request received — your team has been notified and will process it shortly." The workspace is out of credits, or the spend cap is reached. The request stays queued and the agent does not start. Home says "No credits left this period" or "Spend cap reached". MDF-QUOTA-001.
• "Too many messages. Try again in a few minutes." That client sent too many messages in a short window, or they already have two requests in Triage. MDF-QUOTA-002.

Fix. For the monthly cap, edit Monthly request cap or wait until the next UTC month. For credits, open Settings → Plan & usage and upgrade, raise Monthly spend cap (USD), or wait for the period to reset. For the short window, wait and send again.

Further adjustments on one change stop with "For further adjustments," the team name "will get back to you." MDF-REQ-004.