Create a disposable boundary
Start from a known commit in a temporary worktree or isolated container. Mount only the repository and tools required, remove production credentials, block unnecessary network access and set CPU, time and file-change limits.
Give the agent one explicit issue with a finish condition. A controller should record every command, stop after a maximum number of attempts and preserve the original commit so the run can be discarded without manual cleanup.
Separate editing from validation
Allow writes only to files the task reasonably touches. Keep security policies, CI configuration, protected tests and the validator read-only or outside the sandbox. Run formatting, type checks, unit tests and targeted regression tests after the patch.
Add a behavioral test that fails before the repair and passes afterward. Compilation belongs in the suite but cannot replace correctness, security and integration checks. Flag deleted tests and unrelated changes automatically.
Review, merge and learn
Present the reviewer with the issue, proposed diff, commands run, test results, uncertainty and rollback instructions. The agent must not approve its own patch or bypass branch protection.
Follow the AINewsInu homepage and Coding coverage for agent engineering guides. After deployment, monitor the repaired behavior and feed verified failures into the held-out test set.
Sources & further reading
Social-media activity is treated as a signal of attention, not proof. Product claims are attributed to the linked publisher or announcement.