[haroldship]

Chore Pull Request

Related Issue

Closes #211

Description

cuga-agent is adding the setting execution.enforce_code_security (default true). It controls the checks on agent-generated code: import allowlist, AST checks, restricted builtins and globals. Once that change lands, DYNACONF_ADVANCED_FEATURES__BENCHMARK=appworld no longer turns those checks off on its own. This PR sets the flag to false for AppWorld, so AppWorld keeps running in relaxed mode.

Type of Changes

• Dependency updates
• Build system changes
• CI/CD improvements
• Code cleanup/refactoring
• Configuration changes
• Development tooling
• Other maintenance tasks

Changes Made

• benchmarks/appworld/config/appworld.env: add DYNACONF_EXECUTION__ENFORCE_CODE_SECURITY=false, with a one-line comment
• Only AppWorld changes. Other benchmarks keep the cuga-agent default (true)
• Safe to merge before the cuga-agent change: until then, Dynaconf keeps the key but nothing reads it

Impact

• No functional changes to the codebase
• Build/deployment process changes
• Development workflow improvements
• Performance improvements (non-functional)

Testing

• I have verified that existing functionality still works
• Build process works correctly
• All tests still pass

Checked that source benchmarks/helpers/load_env.sh appworld (under bash) exports DYNACONF_EXECUTION__ENFORCE_CODE_SECURITY=false. just lint passes. I did not run just ci or an AppWorld run, since this changes only one env line.

Checklist

• My changes follow the project's standards
• I have performed a self-review of my changes
• I have updated relevant documentation if needed

Summary by CodeRabbit

• Chores
  • AppWorld benchmark runs with code security enforcement disabled.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Source mode: Auto
• Repository: cuga-project/cuga-eval
• Branch: chore/appworld-enforce-code-security-off
• File: .coderabbit.yaml
• Commit: acf0b9b
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 95683f23-020e-4a25-b307-e6b1914d71e7

📥 Commits

Reviewing files that changed from the base of the PR and between 3ef04c3 and acf0b9b.

📒 Files selected for processing: 1

• benchmarks/appworld/config/appworld.env

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The AppWorld environment configuration sets DYNACONF_EXECUTION__ENFORCE_CODE_SECURITY to false.

Changes: AppWorld configuration

Layer / File(s)	Summary
Set AppWorld execution mode benchmarks/appworld/config/appworld.env	The configuration sets DYNACONF_EXECUTION__ENFORCE_CODE_SECURITY to false.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Suggested reviewers: sami-marreed

Merge Risk: ⚪ Minimal · up to acf0b

The AppWorld setting is appropriately scoped and does not introduce a merge-blocking concern.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: configuring AppWorld to run with code security enforcement disabled.
Linked Issues check		Issue #211 requires AppWorld to set DYNACONF_EXECUTION__ENFORCE_CODE_SECURITY=false and keep other benchmarks unchanged. The whole-PR diff adds this exact setting to `benchmarks/appworld/config/appw…
Out of Scope Changes check		The whole-PR diff contains only two added lines in benchmarks/appworld/config/appworld.env. The setting and comment directly support issue #211. No unrelated change is present.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…

Full details: Linked Issues check

Explanation

Issue #211 requires AppWorld to set DYNACONF_EXECUTION__ENFORCE_CODE_SECURITY=false and keep other benchmarks unchanged. The whole-PR diff adds this exact setting to benchmarks/appworld/config/appworld.env with a clear comment. No additional coding or automated-test requirement is stated in issue #211.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files.

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}