acceptodds
Desk rejected at ICLR 2027

SafeSym: Generating a Safety-Constrained Symbolic World Model for GUI Agents

Desk rejected at ICLR 2027, so left out of the paper lists and the map.

Abstract

GUI agents can execute complex multi-step tasks in real-world digital environments, but ensuring their safety remains a key challenge. Existing approaches rely on post-hoc guardrails, which fail to enforce safety during decision-making. Symbolic world models provide a structured representation of environment dynamics and enable planning with explicit reasoning, making them a promising foundation for controllable and interpretable agent behavior. However, existing symbolic approaches do not explicitly model safety, leading to potential risks during planning and execution. To address this, we propose SafeSym, a novel multi-agent framework that constructs safety-constrained symbolic world models and embeds safety constraints directly into planning. SafeSym builds and verifies symbolic models represented in the Planning Domain Definition Language (PDDL), dynamically instantiates task-specific constraints via rule matching, and performs planning over the constrained model to ensure safety by construction. Extensive experiments on GUI-based tasks show that SafeSym achieves the highest overall safety compliance and success-with-obligation rate, outperforming existing SOTA methods while maintaining competitive task success and requiring zero runtime safety guard calls. These results demonstrate that integrating safety into symbolic planning provides an effective and interpretable solution for safe GUI agents. The source code is available at https://anonymous.4open.science/r/SafeSym.

Primary area:
alignment, fairness, safety, privacy, and societal considerations
Keywords:
Safety, AI Agents, Neuro-Symbolic

Reviews

Among:
Shape:
1234this paper, Top 49%
Figure 1. Mean review rating of the reviewed papers at ICLR 2027. This paper averages 2.33 over 3 reviews, above 51% of the others.
Reviewer_YLr6OpenReview ↗
Rating
3
Confidence
3
Informativeness
3
Presentation
3
Soundness
3
Read review
Paper summary

SafeSym builds a PDDL world model from a GUI finite-state machine, checks syntax and goal reachability, matches actions against a fixed safety-rule library, and injects the resulting obligations as preconditions or auxiliary check actions. A planner then returns a plan that meets the goal only on paths satisfying the injected constraints. The plan is given to a GUI agent as decision-time guidance. On web tasks drawn from AutoWebWorld, across several backbone models, SafeSym reports higher obligation compliance than two external guard methods while keeping task success comparable and making no extra runtime guard calls. A progressive ablation attributes most of the gain to static constraint injection, with a further gain from dynamic matching.

Critical strengths

1.Safety is placed in the model, and its cost is measured. Injecting obligations as preconditions or check actions before planning is a concrete alternative to a second model vetting each chosen action. Table 2 makes the benefit operational: zero external guard calls and roughly half the online model calls per task of the two guard baselines. This matters because runtime guard cost is a real barrier to deploying agent safety mechanisms, and the paper reports it directly.

  1. The ablation and the uncertainty reporting are informative and honest. Unconstrained planning barely changes obligation metrics, static constraint injection produces the large jump, and dynamic instantiation adds a further gain on the obligation types that need parameter binding. The appendix reports paired bootstrap intervals, including one that spans zero for obligation coverage against SafePred. Appendix F states that the guarantee is relative to the supplied symbolic model and rule library, and that it does not certify external sanitizers or approval workflows. This lets a reader see which parts of the gain are solid.
Critical weaknesses

The setting is narrow, and the safety notion is procedural. The method assumes an accurate FSM of the target site, a fixed library covering five obligation types, and tasks where the obligation check can be expressed as a typed support action. Robustness to incomplete or noisy transition models is not tested, and the paper lists this itself. The metric rewards emitting the right check in the right order and does not verify that the check had its intended effect. Together these limit how far the results transfer to open-web GUI agents.

Questions for authors

On episodes where the planner returns a constraint-satisfying plan, how often does the low-level agent omit or reorder a required check, and is that the main source of the 57.9% OSR?

2 comments
AuthorsOpenReview ↗

Response to Reviewer YLr6

Thank you for recognizing SafeSym's runtime efficiency, informative ablations, and transparent uncertainty and scope reporting. We address the two aspects of the stated weakness and then answer the execution-gap question with an additional log analysis.

W1: Symbolic-model and rule scope

SafeSym targets known or model-accessible GUIs, with guarantees defined relative to the supplied symbolic model and encoded policy. PDDL represents the combinatorial state space implicitly through predicates and action schemas rather than enumerating every GUI state. Workflow specifications, application instrumentation, developer interfaces, or upstream exploration can provide the model; when transitions are updated, SafeSym reruns obligation grounding, compilation, validation, and planning.

AutoWebWorld's executable sites and reference FSMs let us isolate this policy-to-model transformation across 24 websites, 345 multi-step tasks, five application domains, and four actor backbones. Within the supplied model, every constrained plan must establish the required obligation predicates before governed actions. The five obligation types are reusable safety-procedure interfaces rather than a closed list of risks: new policies can add triggers, state predicates, templates, or typed procedures while retaining the same planner. We will make this applicability and update path more explicit in the revision.

W2: Procedural compliance and external effects

The current evaluation measures typed-obligation orchestration during GUI execution; deployment-specific handler correctness is enforced at a separate interface. In the symbolic model, a check is a stateful support action: its predicate is initially false, the governed action requires it, the support action establishes it, and the governed action consumes or resets it. OSR (Succ.) and OCov (Succ.) are computed from recorded actor trajectories, measuring required-type coverage, prescribed ordering, and invalid types rather than copying compliance from the plan.

A deployment can bind the same typed interface to an authorization service, validator, sanitizer, content moderator, or human-approval workflow, and establish the predicate only after that procedure reports success. SafeSym therefore determines which procedure is required, binds it to the governed action, and enforces its planning-time lifecycle; the deployment handler verifies its external effect. We will state this division directly when defining the guarantee and metrics.

Q1: What explains the 57.9% OSR (Succ.)?

The 57.9% OSR (Succ.) is explained by actors omitting required check types, not by additional order-only failures. Across 1,370 completed SafeSym episodes with nonempty reference safe plans, 762 are successful. Every OSR (Succ.) failure among these successful episodes coincides with a missing required obligation type, with no additional order-only failures when all required types are present:

Actor modelSuccessful episodesEpisodes missing a required typeMissing-type rate
GPT-5.4 mini17714481.4%
Gemini 3.1 Flash-Lite1962211.2%
Gemma 4 26B A4B IT172169.3%
Qwen3.6-35B-A3B21714466.4%
Overall (unweighted model macro-average)----42.1%

The 42.1% macro-average missing-type rate is the complement of the reported 57.9% OSR (Succ.). Across all 1,370 completed episodes, including unsuccessful executions, 845 (61.7% pooled) miss at least one required type. Only one episode (0.073%) exhibits a first-occurrence ordering inversion among observed required types, and it also misses a required type. No invalid check types occur in the recorded and successfully parsed execution trajectories. Thus, ordering contributes no additional OSR (Succ.) failures beyond those already failing coverage.

This localizes the measured gap to actor-level realization: constrained plans satisfy the compiled obligations, while GUI actors sometimes omit required check types during execution. The variation across backbones further shows that execution-level realization depends on actor capability. We will add this breakdown to the revision and explicitly distinguish planning-level constraint satisfaction from actor-level compliance.

AuthorsOpenReview ↗

Follow-up on Rebuttal Discussion

Dear Reviewer YLr6,

Thank you again for your thoughtful feedback and positive assessment. We have carefully addressed the concerns raised in your review and provided additional analysis of execution trajectories to clarify the omission and ordering of safety checks in our rebuttal. We have also uploaded an updated manuscript PDF incorporating these revisions.

As the discussion period is approaching its deadline, we would greatly appreciate it if you could review our responses and share any remaining concerns or feedback. We would be happy to provide further clarification if needed. If our responses have satisfactorily addressed your concerns, we would also appreciate your consideration of an updated assessment.

Thank you for your valuable time and consideration.

Reviewer_vPNROpenReview ↗
Rating
2
Confidence
3
Informativeness
2
Presentation
2
Soundness
2
Read review
Paper summary

This paper proposes SafeSym, a multi-agent framework for building symbolic world models with integrated safety constraints for GUI agents. It embeds safety requirements directly into the planning process by dynamically generating and injecting task-specific constraints into PDDL-based models. Experiments on diverse GUI tasks show that it achieves higher safety compliance and constrained success rates than existing approaches, while maintaining competitive task completion rates and eliminating the need for runtime safety guards.

Critical strengths

The writing is well-organized, the theoretical analysis is sound, and the experimental results support the authors' claims.

Critical weaknesses

a) The problem addressed in this paper is important, but the proposed method is relatively trivial. Ensuring the safety of GUI agents is a significant and timely challenge, however, injecting safety constraints into symbolic world models and planning— can be seen as a straightforward extension of existing symbolic planning frameworks. The approach mainly relies on matching predefined safety rules to actions and incorporating them as additional preconditions. b) Experimental evaluation mainly contrasts SafeSym with two external guard-based baselines, SafePred and WebGuard. But these baselines may not be fully optimized for the symbolic planning setting. The comparison is weak.

Questions for authors

a) how to handle situations where the predefined safety rule set is incomplete or fails to capture emerging risks in dynamic GUI environments. b) are there any additional benchmark results beyond AutoWebWorld.

4 comments
AuthorsOpenReview ↗

Response to Reviewer vPNR

Thank you for recognizing the paper's organization, sound analysis, and supporting experiments. We clarify the technical contribution and evidence below.

W1: Technical contribution beyond standard symbolic planning

SafeSym's technical contribution is automatically deriving and compiling task-specific safety constraints, rather than planning with manually specified preconditions. It retrieves rule-action candidates, contextually refines and validates them, binds typed obligations to concrete actions and parameters, and emits the coupled predicates, preconditions, support actions, and reset effects. The planner remains unchanged.

The ablation makes this distinction visible: Planning obtains 11.9% OSR (Succ.) and 23.9% OCov (Succ.); static compilation raises them to 43.3% and 62.9%; dynamic refinement reaches 57.9%, 73.8%, and 31.9% SOR. In Table 11, a matched control receives identical action-bound obligations but no constrained PDDL or plan; SafeSym still improves SR, CIR, OSR (Succ.), OCov (Succ.), and SOR by 7.0, 6.0, 4.1, 5.3, and 1.6 points.

W2: Strength and fairness of the baseline comparison

SafePred and WebGuard remain runtime action-level supervisors. All methods share actor backbones, observations, actions, step budget, and the frozen obligation reference. SafePred uses single-step world-model risk assessment; WebGuard-style supervision uses its SAFE/LOW/HIGH protocol. The comparison therefore measures realization of the same typed-obligation policy.

On the common completed-task intersection, paired bootstrap gives SafeSym gains over SafePred of +13.0 OSR (Succ.) (95% CI [8.0, 17.7]) and +8.2 SOR ([5.2, 11.2]); over WebGuard, gains are +41.2 OSR (Succ.) ([37.2, 45.3]), +39.8 OCov (Succ.) ([36.8, 43.1]), and +22.3 SOR ([19.5, 25.2]).

The within-framework ablation and matched-information control provide complementary evidence independent of external adapters.

Q1: Incomplete policies and emerging risks

The five obligation types are reusable safety-procedure interfaces, not five rules or a closed risk taxonomy. Keyword/regex matching retrieves candidates, which then undergo task-aware refinement, validation, consolidation, and recompilation.

New policies can add state conditions, triggers, templates, or typed procedures without changing the planner. Multi-action risks can use predicates for workflow stage, prior information, or authorization state. Explicit provenance keeps these extensions inspectable.

Appendix E.2 audits 408 contexts across 48 tasks and 24 applications: annotators achieve Cohen's kappa of 0.892, while SafeSym reaches 95.0% precision and 80.0% recall. For every obligation represented in the policy and model, constrained plans cannot bypass its support action; newly encoded risks use the same grounding and compilation pipeline.

Q2: Evaluation beyond AutoWebWorld

We also evaluate WebArena tasks from Shopping, Reddit, and Shopping Admin using task-family symbolic abstractions. WebArena's evaluator measures success, while the typed-obligation reference measures compliance; results average four actor backbones.

MethodSRCIROSR (Succ.)SOR
Reactive64.30.00.00.0
Planning85.70.00.00.0
SafeSym78.671.481.864.3
SafePred78.657.154.542.9
WebGuard85.728.616.714.3

On WebArena, SafeSym achieves the highest OSR (Succ.) of 81.8% and SOR of 64.3%, while maintaining a competitive SR of 78.6%. It outperforms SafePred (54.5% OSR (Succ.), 42.9% SOR) and WebGuard (16.7%, 14.3%) on both obligation metrics, providing direct evidence beyond AutoWebWorld.

We will revise the manuscript to sharpen the distinction from standard symbolic planning and add the common-protocol comparison, policy-extension explanation, and WebArena results.

AuthorsOpenReview ↗

Follow-up on Rebuttal Discussion

Dear Reviewer vPNR,

Thank you again for your thoughtful feedback. We have carefully addressed your concerns regarding technical novelty, baseline comparisons, and policy extensibility, and provided additional experimental results on WebArena in our rebuttal. We have also uploaded an updated manuscript PDF incorporating these revisions.

As the discussion period is approaching its deadline, we would greatly appreciate it if you could review our responses and share any remaining concerns or feedback. We would be happy to provide further clarification if needed. If our responses have satisfactorily addressed your concerns, we would also appreciate your consideration of an updated assessment.

Thank you for your valuable time and consideration.

Appreciate your response. I prefer to maintain my rating.

Thank you for reviewing our response. Could you please let us know whether any specific concern remains unresolved? We would be glad to address it during the remaining discussion and hope that the added clarifications, controlled comparisons, and WebArena results may support reconsideration of the rating.

Reviewer_rZ5nOpenReview ↗
Rating
2
Confidence
3
Informativeness
2
Presentation
2
Soundness
2
Read review
Paper summary

This paper introduces SafeSym, a multi-agent framework designed for GUI-based intelligent agents. Its core concept involves formally embedding safety constraints into the construction and planning processes of a symbolic world model. This ensures safety by construction during the planning phase, rather than relying on post-hoc guardrails or reflection mechanisms. The framework consists of four stages: symbolic world model construction, model verification, dynamic safety constraint generation, and safety injection with constrained planning. Experiments were conducted using GUI tasks based on AutoWebWorld, with the framework compared against two external guardrail methods: SafePred and WebGuard.

Critical strengths
  1. SafeSym compiles safety constraints into PDDL preconditions and auxiliary predicates, effectively constraining the planner’s search space such that all feasible plans are structurally guaranteed to satisfy safety requirements. This approach represents the first systematic proposal of its kind within the domain of GUI-based agents.
  2. Rather than applying uniform, static rules to all actions, SafeSym performs context-aware matching by analyzing action semantics against a predefined library of rules. It then instantiates abstract safety templates into concrete constraint expressions tailored to the current model. Ablation studies confirm the effectiveness of this mechanism.
  3. The approach offers advantages in terms of runtime efficiency. Experiments presented in the paper demonstrate that incorporating safety constraints directly into the planning phase not only enhances compliance but also reduces inference overhead.
Critical weaknesses
  1. SafeSym requires the GUI environment to be provided a priori as a FSM. In reality, however, GUI environments are typically dynamic, only partially observable, and possess a state space far too vast to be enumerated by an FSM.
  2. There is a fundamental distinction between issuing a check action and the actual completion of a safety check. While the paper acknowledges this in the Limitations section, its evaluation metrics are built entirely upon the former. Consequently, the reported metrics measure non-substantive safety, which may lead to an overestimation of the method's actual safety efficacy.
  3. The comparisons with baseline methods, SafePred and WebGuard, suffer from fairness issues; since these baselines were not originally designed for symbolic planning scenarios, the adaptations made in the paper may have undermined their inherent strengths.
  4. Although the paper emphasizes that safety is maintained without compromising task completion, the main experiments indicate that the injection of constraints can alter planned paths, potentially preventing the agent from triggering necessary safety checks in certain situations. The paper lacks an in-depth analysis of these occurrences.
  5. The current rule base includes only five types of obligations, and the matching mechanism relies on keyword inclusion/exclusion and regular expressions. This pattern-matching approach to constraint generation is ill-equipped to handle combinatorial risks or complex safety policies that require contextual reasoning.
  6. The paper does not address how SafeSym behaves when injected safety constraints conflict with task objectives, or when a combination of constraints renders the planning problem unsolvable—a common scenario in practical deployments where constraints may lead to planning failures.
Questions for authors
  1. How does the symbolic world model construction phase of SafeSym adapt when the target GUI environment cannot be fully pre-acquired as a complete FSM, and do the safety guarantees still hold in such cases?
  2. In the current evaluation, the check action verifies only whether a command was issued, not whether it was actually executed. How do the authors justify that this form of formal compliance assessment accurately reflects real-world safety outcomes, rather than merely measuring the agent’s adherence to a specified prompt format?
  3. The paper’s safety rule base consists of five types of obligations and relies on pattern matching for rule activation. How do the authors address the limitations of this rule base, such as the potential for missing rules, rule conflicts, or the emergence of previously unseen risk types, and are there any principled approaches for extending the framework?
3 comments
AuthorsOpenReview ↗

Response to Reviewer rZ5n

Thank you for recognizing SafeSym's planning-level constraint enforcement, context-aware obligation instantiation, and runtime-efficiency advantages. We address your questions about the mechanism, evaluation protocol, and guarantee scope below.

W1/Q1: Model acquisition and guarantee scope

SafeSym requires a symbolic action model, not an enumeration of all GUI states: PDDL represents states implicitly through predicates and action schemas. We target known or model-accessible GUIs, including enterprise workflows, instrumented applications, and systems with developer-accessible interfaces. Models may come from workflow specifications, instrumentation, developer interfaces, or upstream model learning; after an update, the same grounding, compilation, validation, and planning pipeline is rerun. AutoWebWorld's executable sites and reference FSMs isolate this policy-to-model transformation, with 345 of 349 sampled tasks passing validation.

Within the supplied symbolic model and encoded policy, no feasible plan can bypass a required typed obligation or schedule it after its governed action.

W2/Q2: Typed obligation execution and safety meaning

The check is a typed, stateful support action. Its action-specific predicate is initially false; the support action establishes it; and the governed action requires and then consumes or resets it. This excludes arbitrary mentions and invalid ordering.

OSR (Succ.), OCov (Succ.), and SOR are computed from the agent's actual GUI trajectory rather than copied from the symbolic plan. They assess required check-type coverage, prescribed check-type ordering, invalid check types, and task outcome. SafeSym obtains 57.9% OSR (Succ.) rather than 100%, reflecting that a GUI actor can realize only part of, or deviate from, a symbolically compliant plan.

The evaluation measures typed-obligation orchestration: obligations are action-bound in the model, while trajectory metrics assess their coverage and ordering. A deployment can bind the same interface to an authorization service, validator, sanitizer, or human-approval workflow and establish the predicate only after success. The planning guarantee remains distinct from external-handler correctness.

W3: Fairness of the SafePred and WebGuard comparison

We compare planning-time enforcement with runtime action supervision while holding actor backbones, observations, actions, step budget, and the frozen obligation reference fixed. The baselines retain their action-level roles: SafePred uses single-step world-model risk assessment, and WebGuard-style supervision uses SAFE/LOW/HIGH classification. The comparison measures realization of the shared typed-obligation policy, not all native safety objectives.

The evidence for SafeSym's contribution does not rest solely on external-method adapters. The progressive ablation compares unconstrained Planning, Static Constraints, and Dynamic Constraints within the same execution framework, directly testing the incremental value of constraint injection and contextual refinement.

On the per-model intersection of completed records for all three methods, paired bootstrap shows gains over SafePred of +13.0 OSR (Succ.) (95% CI [8.0, 17.7]) and +8.2 SOR ([5.2, 11.2]); gains over WebGuard are +41.2 OSR (Succ.) ([37.2, 45.3]), +39.8 OCov (Succ.) ([36.8, 43.1]), and +22.3 SOR ([19.5, 25.2]). Table 11 further gives both conditions identical action-bound obligations; without constrained PDDL or planner output, the matched control trails SafeSym by 7.0, 6.0, 4.1, 5.3, and 1.6 points in SR, CIR, OSR (Succ.), OCov (Succ.), and SOR.

W4: Task completion, path changes, and missed checks

Constraint injection intentionally changes the path by searching within the obligation-constrained transition system; every governed action still requires its obligation precondition. The changes from unconstrained Planning to SafeSym are:

Actor backboneDelta SRDelta OSR (Succ.)Delta SOR
GPT-5.4 mini-4.6+18.6+9.6
Gemini 3.1 Flash-Lite-1.2+44.3+24.6
Gemma 4 26B A4B IT-1.5+90.1+46.3
Qwen3.6-35B-A3B+2.9+31.2+19.8
Overall-1.1+46.0+25.0

Overall SR decreases by only 1.1 points, while OSR (Succ.) and SOR increase by 46.0 and 25.0 points. CIR rises from 38.9% to 86.2%. Every OSR (Succ.) failure in successful trajectories includes a missing required type, with no additional order-only failure when all types are present. Backbone differences show that realized compliance still depends on actor capability.

W5/Q3: Rule library, contextual matching, and extensibility

Keyword/regex matching is only SafeSym's candidate-retrieval stage, not the complete constraint-generation pipeline. Task-aware LLM refinement then applies structured add, remove, change_type, and change_reason operations, validates targets, consolidates obligations, and recompiles them into PDDL. This dynamic stage raises OSR (Succ.) from 43.3% to 57.9% and OCov (Succ.) from 62.9% to 73.8%.

The five types are reusable safety-procedure interfaces, not a closed risk taxonomy. New policies can add state conditions, rules, templates, or obligation types without changing the planner; multi-step risks can use predicates for workflow stage, authorization, or accumulated risk. The explicit representation preserves provenance and auditability.

Appendix E.2 audits all five types across 48 tasks and 24 applications: annotators achieve Cohen's kappa of 0.892, while SafeSym reaches 95.0% precision and 80.0% recall against the adjudicated reference.

W6: Constraint conflicts and planning infeasibility

Current rules encode preparatory obligations rather than prohibitions. The support action inherits the governed action's preconditions and establishes the required predicate without changing task state. Thus, an originally feasible plan has a constructive constrained counterpart: insert the support action before the governed action. Multiple obligations use separate predicates, duplicates are consolidated, and Fast Downward checks feasibility.

If the model or policy makes the goal infeasible, SafeSym fails closed and surfaces the planning failure for policy review or human intervention instead of relaxing constraints.

SafeSym's contribution is the automatic policy-to-model transformation that selects task-relevant obligations, grounds them to concrete actions, compiles their stateful lifecycle, and jointly plans for task completion and compliance.

We will revise the manuscript to make the guarantee scope, baseline protocol, execution-level analysis, extensibility mechanism, and infeasibility behavior explicit.

AuthorsOpenReview ↗

Follow-up on Rebuttal Discussion

Dear Reviewer rZ5n,

Thank you again for your thoughtful feedback. We have carefully addressed the concerns raised in your review, including the safety guarantee, baseline fairness, and constraint handling, with additional clarifications and experimental analyses in our rebuttal. We have also uploaded an updated manuscript PDF incorporating these revisions.

As the discussion period is approaching its deadline, we would greatly appreciate it if you could review our responses and share any remaining concerns or feedback. We would be happy to provide further clarification if needed. If our responses have satisfactorily addressed your concerns, we would also appreciate your consideration of an updated assessment.

Thank you for your valuable time and consideration.

Comments on the paper

1 comment
AuthorsOpenReview ↗

Rebuttal Summary

Dear Area Chair and Reviewers,

We sincerely thank all reviewers for their valuable feedback. As the discussion period draws to a close, we would like to briefly summarize our contributions and the additional work completed during the discussion.

Paper Summary

We appreciate the reviewers' recognition of SafeSym's planning-level safety enforcement and context-aware obligation generation (Reviewer rZ5n), interpretability and runtime efficiency (Reviewers rZ5n and YLr6), and sound theoretical analysis, informative ablations, and transparent uncertainty reporting (Reviewers vPNR and YLr6). SafeSym automatically grounds abstract GUI safety policies into task-specific, action-bound obligations and compiles them into stateful symbolic constraints, enabling safety-constrained planning without additional runtime guard calls.

Discussion Period Summary

During the discussion period, we responded to all questions raised by the three reviewers, provided additional experiments and analyses, and uploaded an updated manuscript incorporating these revisions.

  • Technical novelty and policy extensibility (Reviewers rZ5n, vPNR, YLr6). We clarified SafeSym's core contribution in automatic policy-to-model transformation, including context-aware obligation grounding, stateful constraint compilation, and extensibility to new safety policies.

  • Baseline fairness and effectiveness (Reviewers rZ5n, vPNR). We provided common-task paired bootstrap analyses and highlighted the matched-checklist control. With identical obligations, SafeSym improves all five metrics over checklist prompting, including a 7.0-point gain in task success.

  • Safety guarantees and execution analysis (Reviewers rZ5n, YLr6). We clarified the distinction between planning-level guarantees and GUI execution. Additional analysis of 1,370 execution episodes identifies missing obligation types as the primary source of the OSR shortfall, with no additional order-only failures.

  • Obligation validation and constraint handling (Reviewers rZ5n, vPNR). We highlighted the independent obligation audit (Cohen's κ = 0.892, precision = 95.0%) and clarified the mechanisms for constraint feasibility, rule matching, and policy extension.

  • Evaluation beyond AutoWebWorld (Reviewer vPNR). We conducted supplementary experiments on WebArena, where SafeSym achieves the highest OSR (81.8%) and SOR (64.3%) among the evaluated methods, providing additional cross-benchmark evidence.

Detailed results and explanations are available in the corresponding review threads and updated manuscript. We sincerely appreciate your time and consideration.

Sincerely,

The Authors

From OpenReview, CC BY 4.0. Authors as signed there; shown unedited.

Related papers

Discussion (0)

Sign in to comment.