- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper studies privacy risks in developer-agent interaction logs. The authors argue that conventional anonymization does not remove behavioral fingerprints, and propose SteerSim, an agentic user simulator that replaces the original human developer in a live coding session. The simulator is conditioned on a persona extracted from real developer traces, and the persona can be transformed to reduce behavioral re-identification. The paper further proposes SteerRL, a post-training method for a smaller open-weight simulator using SFT and agentic RL with rubric-based rewards.
Critical strengths
- The paper identifies an important and timely privacy problem: developer-agent traces can leak identity through behavioral patterns even after standard anonymization.
- The proposed simulator is more ambitious than next-utterance user simulation, since it acts inside a live coding environment, can inspect the repository, and decides when to intervene or stay silent.
Critical weaknesses
-
The central assumption behind the paper is not fully validated: replacing a real human developer with a simulator may remove exactly the interaction signals that make the original logs valuable. The downstream utility experiment only shows comparable performance in limited settings, and the gains appear mainly on FeatureBench, while SWE-bench Verified and SWE-Skills-Bench do not show clear improvement.
-
The persona is extracted by an LLM from a single session and evaluated largely by LLM-based rubric judgments. The paper does not provide enough evidence that the induced persona accurately represents the real developer.
-
The comparability between the simulator and human developers remains unclear. Human-likeness and protocol validity are useful metrics, but they do not directly test whether the simulator has comparable software-engineering judgment, debugging ability, or intervention quality. A simulator may look human-like while still steering the agent in ways that are less informative for training future agents.
Questions for authors
How do the authors verify that an induced persona is an accurate representation of the original developer, beyond LLM rubric scores? Were any human developers or independent annotators asked to validate the extracted personas?
Since the goal is to release useful training traces, can the authors evaluate whether models trained on synthetic traces learn the same intervention patterns as models trained on real human traces, rather than only reporting benchmark pass@1?
3 comments
W2/Q1: Does a persona induced from one session accurately represent the developer? Was it validated by humans?
Thank you for asking us to clarify the intended meaning of a persona. Our personas are session-specific behavioral summaries, not estimates of a developer's complete or stable personality. Section 4.2 explicitly attaches personas to sessions: the same developer can have different personas across sessions. The axes are motivated by prior studies of developer interaction styles, including [2], and the induction prompt summarizes observable steering habits from the session. Prior work motivates this representation but does not independently validate each extracted profile.
The paper provides several checks beyond the persona-alignment rubric. In the re-identification evaluation, the attacker's profile comes from a different session by the same developer; its 0.309 accuracy on real user turns, against 0.100 chance (Table 8), shows that the profiles capture some cross-session identifying information. Appendix I.5 further removes task, repository, product, and technology specifics from the conditioning personas. On the same 100-session subset, this changes Turing score from 4.295 to 4.240, persona alignment from 0.862 to 0.870, and profile re-identification from 0.240 to 0.220 (Table 14). These results support the role of transferable behavioral descriptions rather than dependence solely on task-specific details. Appendix G also traces how a generated session reflects the original developer's corrections and plan-gating behavior.
We have not asked the original developers or independent human annotators to validate the extracted personas. We will state this explicitly and distinguish evidence that a profile captures useful behavioral information from validation of every inferred trait.
W3: Human-likeness does not establish comparable engineering judgment, debugging ability, or intervention quality.
Thank you for making this distinction. We agree that a human-likeness score is not a measure of engineering competence. SteerSim is designed to model developer steering, including when to inspect, interrupt, question, or approve the agent, rather than to claim expert-level debugging from a Turing score. Its live access to the repository makes such decisions possible, but does not by itself establish that their quality matches a human developer's.
We therefore evaluate behavior and downstream usefulness separately. Table 11 directly measures protocol actions and reveals remaining differences: real developers average 0.35 interrupts and 0.44 plan approvals/rejections per session, while SteerRL averages 0.17 and 0.07. SteerRL is also more talkative (7.47 versus 5.44 messages). The new feedback-training experiment above adds evidence that interactions generated by SteerSim (Opus-5) contain usable supervision, evaluated through downstream tests. We will distinguish this demonstrated utility from the stronger, untested claim of matching human engineering judgment.
Q2: Do models trained on synthetic traces learn the same intervention patterns as models trained on real traces?
Thank you for this question. There are two different learned roles in the paper. SteerRL learns to produce user interventions; the downstream coding agent learns to respond to them. In downstream SFT, user messages remain in the context, but the loss covers only the coding agent's assistant turns; user turns and tool results are masked (Appendix H). We also understand the question as asking whether agents trained on synthetic and real traces respond similarly to human corrections and feedback. We have not directly compared their responses to matched interventions; user turns still condition the agent's responses even though they are masked from the loss.
For simulator behavior, Tables 2 and 11 report persona alignment and directly counted interaction patterns. Relative to simulator SFT, SteerRL increases own-persona alignment from 0.790 to 0.867, validity from 0.770 to 0.921, and interrupts from 0.04 to 0.17 per session, although the human distribution is not fully matched. For downstream agents, the new Span-KTO experiment uses feedback extracted from SteerSim (Opus-5) interactions to train the coding agent and evaluates its task performance. This provides related evidence that simulated feedback is useful for learning, but does not establish that agents trained on synthetic and real traces respond equivalently to human interventions. We will make this distinction explicit.
[1] The verification horizon: No silver bullet for coding agent rewards. arXiv 2026.
[2] No two developers think alike: How problem-solving styles and experience shape needs in conversational interaction with Copilot. ICSME 2026.
We thank the reviewer for the thoughtful feedback and for recognizing both the importance of behavioral privacy and the value of simulation inside a live coding environment. We address the preservation of useful interaction signals with additional downstream experiments, and clarify what our persona and behavioral evaluations establish.
Thank you for identifying the central utility question. Our aim is to reduce behavioral identification while retaining the usefulness of the sessions for training coding agents. Figure 5 tests this through agent-side SFT and skill distillation: synthetic and real sessions provide comparable downstream performance in the evaluated settings, and both improve FeatureBench. We do not interpret the absence of clear gains on the other benchmarks as evidence that the sessions improve every kind of software-engineering task.
We added two experiments to examine the value of the generated interactions more directly. First, we regenerated 350 persona-swap sessions with Qwen3.5-4B as the coding agent and SteerSim (Opus-5) as the user simulator, then trained Qwen3.5-4B on its own coding trajectories. Second, following the feedback-annotation approach in The verification horizon [1], we labeled the simulated-user turns and used their feedback in Span-KTO training. All results below use Qwen3.5-4B with opencode on the first 100 SWE-bench Verified tasks, three evaluation runs, and the same environment.
Tables R2–R3: Downstream utility of self-generated sessions and simulated user feedback.[^hardware-UbNE]
Self-generated trajectory SFT improves mean pass@1 from 0.393 to 0.410 without stronger coding-agent outputs as targets. With standard Span-KTO, simulated feedback reaches 0.410, compared with 0.402 using real feedback. Class balancing further increases pass@1 on simulated feedback to 0.417. This tests a use of the simulated interventions themselves: their feedback is converted into supervision for the coding agent. It extends the utility evaluation beyond imitation and skill distillation, although it does not show that every useful human interaction signal is preserved.
The 350 sessions provide 1,130 judged verdicts without requiring live human participation during rollout or feedback annotation. The pipeline still starts from real session tasks and personas. We also observe a substantial feedback-distribution difference: 87% of simulated feedback is negative, versus 32% for real feedback. Class-balanced Span-KTO yields the highest pass@1 in this comparison, while SFT and standard Span-KTO retain the highest pass@3. We will report this distinction rather than treating simulated and real feedback as interchangeable distributions.