Use Copilot for a tightly managed coding day
A commenter had GitHub Copilot produce all the code they pushed in one day, with close supervision throughout.
- What they did
- A commenter said they let GitHub Copilot generate every line they committed that day, but only while they kept directing it step by step. In the same discussion, other people described a careful routine: give the agent a very narrow goal, say what must stay unchanged, check the code before accepting it, and fall back to backups if it starts breaking things.
- How it went
- The setup was good enough for that day’s work, but it depended on constant human oversight. The thread’s wider conclusion was that agents can struggle on larger tasks and may force a full revert or restart when they go off course; one person said a game change needed 2 days of trial, error, and rollbacks before it finally worked.
- Tips
- Keep each request small, and make the no-touch areas explicit. Review and test every step, and have a backup ready in case the agent edits the wrong parts.
Try it yourself with GitHub Copilot
Help me use GitHub Copilot on [repo/project] to implement [feature or fix] in small pieces. For each piece, make the smallest safe edit, then report the files changed and what you altered so I can review it before you continue. Leave [areas to avoid] alone, and if a change would affect existing behavior, flag that clearly before proceeding. Pause for my approval before any irreversible step such as applying, submitting, deleting, or sending anything. Stop when [done condition] is met and the relevant tests pass.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Update a codebase with Copilot in chat and agent mode
A developer used GitHub Copilot to make code changes and preferred the CLI’s autopilot workflow and todo list.
Use Copilot CLI subagents for parallel terminal work
A commenter used GitHub Copilot CLI to split repo work across multiple subagents, run commands in parallel, and review the results live.
Split development work into phases before using Copilot
A developer plans features in stages first, then feeds the approved steps to GitHub Copilot instead of asking it to make all architecture decisions at once.
Break a runtime migration into tiny reviewable PRs
GitHub engineers had Copilot agents carry out most of a large TypeScript-to-Rust runtime rewrite.
Use Copilot agent mode to finish a web app
Jonas used GitHub Copilot with Claude Sonnet to turn a game-score idea into a working app.
Use Copilot agent mode for multi-step coding work
Hand Copilot agent mode larger coding jobs that need file selection, command runs, and repeated fixes, not just quick text edits.