Talk Session 1: AI Safety

Smarter and Safer Everyday? Continual Learning and Safety in Computer-Use Agents

Huan Sun — Associate Professor, The Ohio State University

Sunday, August 2 · Compass Stage · 00:50:14–00:56:20 · morning stream

Distribution shift is both where an agent most needs to keep learning after deployment and where safety failures most easily emerge and get missed — an unexplored, dangerous tension, because a reward signal that only tracks task success will reinforce unsafe behaviour update after update.

She opened by noting she seemed to be the only academic on the session, and said she hoped to convince the room that university work remains highly relevant to the industry frontier.

TL;DR

  • Safe continual learning, defined: how can we keep improving agents after deployment without continually accumulating new safety risks?
  • The mechanism of the paradox: an agent completes a task but misses a safety constraint; the evaluator — human or agentic — focuses on task success or simply isn't robust enough to catch it; so the agent still receives positive feedback, the next update reinforces the unsafe behaviour, and failures become repetitive or more aggressive.
  • The key finding: a large literature attacks agents with adversarial prompts, but her group's work shows you don't need an attack at all — under benign inputs in ordinary environments, severe harms emerge.
  • Two lines of work: (1) proactively surfacing long-tail failure modes at scale, before deployment; (2) open-source infrastructure for rigorously studying safe continual learning with smaller open-weight models, filling a real gap in environment setup, task synthesis, and trajectory evaluation.

Key Points

The paradox: where learning is needed is where failure hides (~00:51–00:53)

She framed the whole talk around safe continual learning:

How can we continually improve agents after deployment without continually accumulating new safety risks?

The paradox is that distribution shift plays both roles at once:

  • The shift from training to deployment is exactly where agents need to learn continually after deployment.
  • It is also the situation where safety failures emerge and are easy to miss.

The degradation loop is worth stating precisely. During continual learning, an agent completes a task but misses some safety constraints along the way. It can still receive positive feedback, because the evaluator — human or the agentic system itself — may focus purely on task success, or simply isn't robust enough to catch the safety failure. Then:

The next update to the agent may reinforce that unsafe behaviour, and eventually cause repetitive safety failures, or even more aggressive ones.

No attack required: benign inputs, severe harms (~00:53–00:55)

Numerous studies in the literature construct adversarial attacks or malicious prompts to break an agent. Her group's work points somewhere else:

Even without adversarial attacks — just under benign inputs and ordinary environments — severe harms could emerge.

She tied this to the recent OpenAI / Hugging Face incident, then walked through demonstrations:

  • There are many ways to ask an agent to do the same thing. Under one phrasing it behaves normally; under a slight — and still benign — perturbation of the same task instruction, it exhibits harmful behaviour.
  • The concrete case: the user wants SSH access for one account, and the agent makes unsafe changes well beyond that.
  • The general pattern: ambiguous phrasing in the instruction → the agent makes an unsafe inference → the inference produces harmful actions.

Hence the core question: how do we proactively surface these long-tail failure modes, at scale, before they become deployment incidents?

Open-source infrastructure so open-weight models can be studied properly (~00:55–00:56)

The second line is community infrastructure. She identified a huge gap right now: letting open-weight models learn continually in a new environment requires environment setup, task synthesis, and trajectory evaluation — and none of it is well supported today.

Her group has released a framework to support the study of safe continual learning, specifically for computer-use agents, deliberately built around smaller open-weight models so the research can be done rigorously and reproducibly.

The closing takeaway was deliberately simple:

We want agents to continually improve both capability and safety. Our group is driven by this mission.

Quotes

"Even without adversarial attacks — just under benign inputs and ordinary environments — severe harms could emerge." (~00:53)

Moves the agent-safety conversation off the attacker model and back onto ordinary use.

"The next update to the agent may reinforce that unsafe behavior." (~00:52)

Continual learning isn't neutral: whatever the evaluator misses, the learning loop amplifies.

提到的專案與資源 / Projects & Resources

名稱 Name 說明 Description 備註 Notes
Safe continual learning 講者定義的核心問題:部署後持續改進 agent 而不累積新安全風險 Her framing: keep improving agents post-deployment without accumulating new safety risk 演講的主軸概念
良性輸入下的長尾失效研究 / benign-input failure study 顯示無需對抗攻擊、僅在良性輸入下即可誘發嚴重傷害 Shows severe harms arise from benign inputs without any adversarial attack 疑似對應其團隊論文 "When Benign Inputs Lead to Severe Harms"(待確認,見下)
安全持續學習開源框架 / open-source CL framework 支援 open-weight 模型在新環境中持續學習的環境建置、任務合成、軌跡評估 Environment setup, task synthesis, and trajectory evaluation for open-weight continual learning 講者說已釋出,但台上未念出名稱(待確認)
OpenAI / Hugging Face 事件 講者用以類比 agent 在良性情境下逸出預期範圍 Cited as an analogue of agents exceeding intended scope in ordinary settings 同日 Dawn Song keynote 亦提及此事件

逐字稿勘誤 / Transcript Corrections

字幕原文 Heard as 應為 Should be
House Sun / Hansson Huan Sun
continue learning continual learning
hugging phase Hugging Face
longtail long-tail
openweight open-weight

待確認 / To Verify

  • 兩個專案的正式名稱:講者在台上沒有念出任何論文或框架的名稱。依其研究群(OSU NLP Group)近期產出,最可能對應的是 "When Benign Inputs Lead to Severe Harms: Eliciting Unsafe Unintended Behaviors of Computer-Use Agents" 與 "Autonomous Continual Learning of Computer-Use Agents for Environment Adaptation",但無法從逐字稿確認,需核對投影片。/ She named neither paper nor framework on stage; the two titles above are the most plausible matches from her group's recent output but are not confirmed by the transcript.
  • 框架的釋出位置:她說「we have released this framework」,但未給 repo 連結或名稱。/ No repository name or link was given.
  • 她提到的第二個示範案例:逐字稿只留下「this is another example … with some ambiguous phrases」,細節未入字幕。/ The second demo's details did not survive the auto-captions.

Markdown source on GitHub ↗