Tag: automation

A practical setup for Cursor Projects: prepare the repo so every worker starts warm, seed the Project's shared Context with a plan, conventions and a slice ledger, cut the work into disjoint PR-sized slices, and let subscriptions keep it moving. Covers Cursor 3.24, plan and admin gates, and the gotchas of a Context that lives outside git.

Request a GitHub Copilot code review from a script with the REST requested_reviewers endpoint, the GraphQL requestReviewsByLogin mutation, or gh pr edit, then control whether it runs at Lite or Balanced effort. Covers the bot login, the effort precedence chain, why the per-request effort field announced on October 2, 2026 is not in the published schemas yet, and how to read the effort that actually ran.

GitHub Agentic Workflows (gh-aw v0.91.5) compiles a Markdown file into a hardened GitHub Actions .lock.yml that runs Copilot, Claude Code, Codex, Gemini or Pi in a read-only, firewalled job and applies writes through safe-outputs. What it adds on top of Actions, the jobs it generates, and when a plain workflow with claude-code-action is still the better tool.

Use Cursor's /goal command to keep a cloud agent working toward one finish line across many turns. Covers writing a verifiable objective, pinning a Custom Mode playbook, pairing it with /loop and subscriptions, the CLI's durable goals, and how to stop a goal that ignores Stop.

GitHub's August 3, 2026 changelog adds a comment trigger to Copilot cloud agent automations, replacing the issue_comment workflow plus PAT plus REST dispatch that teams have been hand-rolling since June.

Two ways to make a coding agent land its own work: Claude Code 2.1.198+ background sessions commit, push, and open a draft PR from their worktree with no config, or wrap any agent CLI in a git worktree plus gh pr create --draft. Covers the worktree guardrails, the subagent-vs-session distinction, the GITHUB_TOKEN trigger trap, and why there is still no off switch.

Pick Copilot coding agent when the work starts and ends on GitHub and you want issue-to-PR with native branch protection. Pick Cursor cloud agents when you want a live, editor-attached VM, multi-repo tasks, and to take over the run by hand. Full feature matrix, the 59-minute cap, the Actions-approval gotcha, and June 2026 billing for both.

Use Cursor 3.8's /automate skill to spin up a cloud agent that fires on GitHub events. Covers the five GitHub triggers added June 18, 2026, tool config, repo scope, and the Max Mode billing gotcha.

When a GitHub Actions job goes red, the Fix with Copilot button hands the failure to the Copilot cloud agent: it reads the logs, pushes a fix to your branch, and tags you for review. Here is where the button lives, the May 18 / June 4 2026 rollout, the Approve and run workflows gotcha that stalls re-runs, how billing works per session, and when to reach for the REST API instead.

POST a prompt to /agents/repos/{owner}/{repo}/tasks and Copilot's cloud agent spins up, writes code, and opens a PR. Here is the exact request, the X-GitHub-Api-Version: 2026-03-10 header, the user-to-server token gotcha that breaks GitHub App installs, a polling loop over the eight task states, and a fan-out script that dispatches the same migration across many repos.