- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper test whether a statement on "value" (function) in the instruction file of a self-improving coding agent changes what it builds and how will it performs. Specifically, the value statements come from Schwart’s high-order value types, openness, conservation, enhancement and transcendence. Evaluated on six coding tasks, this paper finds that 1) openness is better than none while conservation and transcendence is worse; 2) value statements do change what the agent builds, e.g., openness makes larger and more complex solvers; 3) when the agent can revise its own values, the difference between different value statements shrinks.
Critical strengths
- I like the direction that looking at coding agent’s actual code beyond simple metrics from some benchmarks. Also the idea of starting from an existing theory of human values (Schwartz) is also interesting.
- The experiment settings are rigorious and comprehensive---6 tasks, 2 controls and full reports.
Critical weaknesses
- My main concern is that the paper calls a short prompt a "value", but the results do not fully support this framing. The openness and conservation statements are mainly codind/search strategies, e.g., prefer the bold transformation a rewrite, a new representation, a different algorithm vs.take the smallest, most-verified step, so the gap between them is largely expected and relatively intuitive. Moreover, section 4.8 shows that rewording openness while "retaining their original dispositions" significantly lowers its score, and the off-task placebo also has a significant effect on Game 2048. Does this mean that the results reflect prompt wording, not human values which are supposed to be more fundemantal, stable and long-term?
- Related to point 1, the link to Schwartz’s theory is mainly in the names. The statements were drafted with an LLM, and the paper does not check that agent behavior matches the intended value. How to define these values mathematically and formally and embed to LLM agent’s value function like classic RL does?
- The none control is itself an instruction (You do not have any inherent values). It is not the same as leaving the values section out.
Questions for authors
See weaknesses.
Response to Reviewer MPqa
Hi, thank you for the review. We appreciate the feedback.
Regarding paper weaknesses:
We define “values” to mean guiding principles designed for AI coding agents, drawing on Schwartz's theory. We do not claim that the agents possess human values. The search guidance is intentional and allows us to evaluate what algorithms the agents develop and how well they perform on held-out data across six tasks.
Our experiments do show that wording matters moderately. In Section 4.8, the rewrites were designed to express openness as rules, outcomes, or character traits. The wording do not change the gap in performance between different ends of the value spectrum such as openness vs conservation. However, we admit that we cannot fully separate the influence of the guiding principles from the wording for each value. We will clarity the details of the prompt wording comparison in the Introduction and Section 4.8.
Schwartz's theory is used not only as names but to guide the content of the instructions: openness favors trying new approaches, conservation favors preserving proven ones, enhancement emphasizes achievement, and transcendence emphasizes others' welfare (Appendix B). An LLM drafted the statements from Schwartz's accounts, and we edited them (Section 3.1). We will make this mapping clearer in Section 3.1.
We examine behavior in Appendix F. Its LLM-based analysis finds more exploration and method adoption under openness than conservation on ALE-Bench and Circle Packing. This is consistent with the intended openness–conservation distinction, but is not an independent validation of the value categories. We will state this limitation explicitly in Appendix F.
In Algorithm 1, V is the instruction text supplied at each iteration. We do not define the four values mathematically or embed them in an RL value function. The model weights and benchmark objective stay fixed. We will make this distinction explicit in Section 3.1 and Algorithm 1. An RL formulation remains future work.
You are correct that “no values” is an explicit instruction: “You do not have any inherent values” (Appendix B). In preliminary experiments, we observed negligible performance difference between this instruction and omitting the values section. We included it to keep the instruction file structure consistent across all values and controls. We will clarify the control wording and rationale in Section 3.1.