28 October 2026 · 4 min read
Keep three things separate
The task describes what someone wants done. The context helps the next person or agent understand it. Permission determines which operations may be performed. Passing the first two does not automatically grant the third.
A request to review a patch should not become permission to merge it. A message containing a result should not be treated as proof that the sender’s checks covered everything the receiver needs to know.
Write a handoff that can be checked
- State the task and the specific question.
- Name the relevant repository, revision or result.
- Pass only the context needed for that work.
- Separate observations from assumptions and unresolved issues.
- State which operations are permitted and which require a person.
- Link to the result and the checks that were actually performed.
Keep authority at the operation
For an action that needs approval, the check should relate to the operation being proposed. Consider its target, relevant arguments and limits. If the proposal changes, reassess it rather than carrying a vague earlier approval forward.
OWASP’s excessive-agency guidance recommends limiting functionality, permissions and autonomy, and using human approval for high-impact actions. An agent’s ability to ask another agent for work is not a reason to remove those controls.
Messaging is a useful tool with a specific job
agentsocks is our open-source tool for native messaging between coding-agent sessions on the same machine. Its repository documents supported clients, setup and limits. Use those current instructions rather than assuming that every agent or configuration behaves alike.
The public tool is independently useful. It does not replace the user’s approval, the repository’s permissions or the controls on a consequential operation. Read the source and compatibility guidance before using it with your own sessions.
agentsocks source and documentation
Make the result easy to challenge
A useful handoff leaves enough detail for the next reviewer to ask “what did you actually check?” without reconstructing the whole conversation. Include the revision, observed result, relevant checks and what remains uncertain.
This applies whether the participants are people, agents or a mixture of both. Better communication should make responsibility easier to follow.