INQUIRING LINE

Before an AI agent acts on your behalf, shouldn't it tell you the trade-offs it's quietly making for you?

How should designers expose systemic trade-offs to users of autonomous agents?

This explores how the design of an autonomous agent's interface can make visible the trade-offs it makes for you, like speed versus safety, your interests versus other people's, and autonomy versus oversight, so you aren't surprised by choices made out of sight.


This explores how designers can show users the trade-offs an autonomous agent makes for them: how much risk it takes, whose interests it weighs, and how much it decides alone. The collection has no single paper on a 'trade-off dashboard.' Read together, though, the notes suggest something less obvious: most trade-offs are settled before or between actions, not in the output. Showing them is less about better explanations after the fact and more about deciding *where* in the workflow the user meets them.

The first place is before the agent starts. Should agentic AI interfaces require users to specify risk tolerance upfront? argues that a goal field ('book me a flight') is not enough. Interfaces should ask for direction, limits, risk tolerance, forbidden actions and conditions that require permission up front. Every agent action carries out a vague instruction without anyone reviewing it, so a trade-off the user never states becomes one the agent makes silently. Seen this way, the setup screen is where trade-offs get exposed. This fits Does AI risk increase with the autonomy we give it?, which treats autonomy as a dial rather than a switch: the more you hand over, the more risk you take on. Letting users see and set that dial is itself a way of exposing the trade-off.

The second place is during the work. When should human-agent systems ask for human help? (Magentic-UI) starts from an honest admission: there is no correct answer to *when* an agent should stop and ask a human. Instead of solving that, the designers spread the decision across six touchpoints: planning together, working on tasks together, guards on risky actions, verification steps, memory, and multitasking. Each one is a point where a trade-off can surface rather than being buried. Can AI systems delegate tasks back to humans? adds that agents may increasingly hand tasks *back* to humans. A well-designed handoff can say *why* the agent is deferring, which tells the user where its confidence runs out.

The harder problem is trade-offs the agent itself doesn't know it's making. Why do parallel subagents produce conflicting design decisions? shows that subagents build unstated assumptions into every action, and parallel agents end up with conflicting choices no one ever spelled out. If the system can't see its own implicit decisions, no interface can show them. That is part of Yan's case for single-threaded agents. How should agent capabilities be organized into functional layers? raises a related worry: as supervisor and orchestrator agents pile up, the person at the top drifts further from where the choices actually get made.

Finally, some trade-offs aren't between the user and the agent at all. They're between the user and everyone else. Should AI agents serve one user or balance many interests? argues that agents operating at scale must balance many parties' interests, and names *visibility* (tracking and transparency) as a basic requirement. Can traditional governance tools actually control AI agents? explains why this is hard: the classic principal-agent problems of hidden information, discretion and divided loyalty get worse when decisions are fast and hard to interpret. The usual fixes of incentives and monitoring don't scale to that. The practical takeaway: design for visibility at the moments that matter (setup, deferral, irreversible actions). Don't expect after-the-fact transparency to make up for trade-offs nobody ever asked the user about.


Sources 8 notes

Should agentic AI interfaces require users to specify risk tolerance upfront?

Gunasekaran argues that autonomous AI requires interfaces capturing direction, limitations, risk tolerance, forbidden actions, and permission conditions before execution—not just goal fields. Underspecified intent propagates through every agent action without user review, making upstream specification critical to preventing irreversible harm.

Does AI risk increase with the autonomy we give it?

Risk to people scales monotonically with agent autonomy, with no clear benefits to full autonomy but many foreseeable harms. A governed spectrum of autonomy levels is safer and more practical than either unrestricted agents or exhaustive oversight.

When should human-agent systems ask for human help?

Magentic-UI identifies co-planning, co-tasking, action guards, verification, memory, and multitasking as mechanisms that work around the lack of ground truth for optimal deferral timing. Rather than solving the timing problem directly, these mechanisms distribute decision-making across multiple touchpoints.

Can AI systems delegate tasks back to humans?

Holldack, Banh and Strobel argue that agentic information systems capable of independent decision-making can transfer rights and responsibilities to humans, reversing the traditional one-directional delegation model. This requires moving beyond agency-primacy frameworks to delegation theory that accounts for bidirectional task assignment.

Why do parallel subagents produce conflicting design decisions?

Walden Yan argues multi-agent parallelism is fundamentally fragile: subagents embed unwritten assumptions in every action, so agents working independently converge on conflicting choices. The fix is reverting to single-threaded linear agents where context remains continuous.

Show all 8 sources
How should agent capabilities be organized into functional layers?

Dubberly proposes a two-axis stack model: a capability axis (chatbot → system prompt → RAG) adding inputs that extend what LLMs can act on, and a scale axis (monitoring agents → supervisors → orchestrator) aggregating oversight. He cautions that ubiquitous agent hierarchies raise design risks alongside capability gains.

Should AI agents serve one user or balance many interests?

Research argues the traditional single-agent-single-user alignment framing is insufficient at scale. Instead, governance should rest on inclusivity (balancing diverse interests), visibility (rigorous tracking and transparency), and liability (developer and deployer accountability for harms).

Can traditional governance tools actually control AI agents?

Principal-agent economics and agency law identify three core problems—information asymmetry, discretionary authority, and loyalty—that existing incentive, monitoring, and enforcement mechanisms cannot resolve when agents make uninterpretable decisions at speed and scale.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.