Does an always-on agent's risk of overstepping grow with its task chain?

Yes: in OpenAI’s own testing of its dots agents, doubling a chained task sequence from five to ten roughly doubled the share of runs flagged for a boundary problem, from 8.6% to 19.7% of samples, reported in the Dots appendix of the GPT-6 Astra system card.

Nobody restates the rules at step six. A dots agent has to infer where its authority ends from business records, earlier decisions, context, and a confirmation policy, not a fresh grant for each new task, so a small slip has more chances to happen as the chain gets longer. The card counts this as a moderate severity scope violation: an action that goes past the intended task with no severe outcome, such as carrying information between unrelated tasks or making an edit to a shared document. It found no severe breach or data exfiltration in this evaluation.

A five-task chain staying in bounds is weak evidence a twenty-task chain will too. What it actually did belongs in the trace, not in the agent’s own account of the run.

sources

keep reading

More on this.

Try Tessary on Cloud.

free · 10,000 traces a month · 1 GB · 30-day retention · $10 one-time credit for triage and RCA · no credit card