Coding agents are good at long, well-defined jobs. The trouble is what happens around them: the run stops on a question, you are not there, and an hour is gone. These habits make long runs smoother, whether or not you use Brocoded.

1. Pick a task with a clear finish line

“Improve the codebase” never ends. “Add rate limiting to /login and cover it with tests” does. A task with a checkable result, such as tests that pass or a command that exits cleanly, lets you glance at the output and know if it worked.

2. Decide what it may do without asking

Every approval is a place the run can stall. Before you leave, decide which actions you are happy to allow ahead of time, such as reading files and running the test command, and which you want to see first, such as deleting files, changing config or touching anything shared.

  • Allow the cheap, reversible things ahead of time.
  • Keep a human in the loop for anything destructive or outside the repository.
  • If you cannot say yes to a command from your phone, it should not be on the allow list.

3. Work on a branch

Start the run on its own branch, or in a clean working tree. Then the diff is the whole story: you can read it, keep it or throw it away without untangling it from your other work.

4. Make sure you hear when it asks

A run that needs you and cannot reach you just waits. Turn on alerts so your phone buzzes when the agent asks a question or needs approval. With Brocoded, the alert is a fixed message such as “A session needs you”, and you open the app to see the full command.

5. Keep the computer awake

The session runs on your computer, so it has to stay on, awake and online. Plug in a laptop and change its sleep settings before you walk away. If the machine sleeps, the session cannot be reached until it wakes.

6. Review before you ship

When the agent says it is done, read the diff file by file before you commit. Look at what changed outside the files you expected. A passing test run is a good sign, not a review.

Brocoded gives you the pieces for steps 4 and 6 from your phone: alerts, approval cards with the full command, a read-only git diff, and commit and push. See the use cases page for how each one looks.

A short checklist

  • The task has a finish line you can check.
  • You decided what it can do alone.
  • It is on a branch.
  • Alerts are on and the computer will stay awake.
  • You will read the diff before committing.