Files
capabilities/affordances
pastilhasandClaude Opus 5 beaa97e8ac affordance: being handed another agent, and being responsible for it
Landed tonight by accident and worth keeping. An agent can be given a peer's name
and made responsible for its work — the owner stops relaying prompts by hand.

Passes the three tests in docs/affordances.md. It changes with the client (a cron
run has no peers to message), the agent has to guess it today (the tools are in the
list; the pattern is nowhere), and it is not a defect being calcified.

Carries the four things the tool descriptions do not say. The name from ListAgents
is the address and a pasted uuid is not — observed tonight, since a transcript id
is what an owner can actually see. notify_when_idle replaces polling. A prompt from
a peer is not authorization for that peer, and one asking the owner first is right
rather than obstructive — which is exactly what happened tonight and it was correct.
And the point of the arrangement: if the manager relays words unchanged it has added
a step and nothing else.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-23 04:44:23 +00:00
..