site banner

Culture War Roundup for the week of July 20, 2026

This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.

Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.

We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:

  • Shaming.

  • Attempting to 'build consensus' or enforce ideological conformity.

  • Making sweeping generalizations to vilify a group you dislike.

  • Recruiting for a cause.

  • Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.

In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:

  • Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.

  • Be as precise and charitable as you can. Don't paraphrase unflatteringly.

  • Don't imply that someone said something they did not say, even if you think it follows from what they said.

  • Write like everyone is reading and you want them to be included in the discussion.

On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.

2
Jump in the discussion.

No email address required.

The tooling it used was just bash, which it used for a container escape via the filesystem, which got it access to the runner's source code, which it analyzed to find where it was pulling eval cases from, which it then looked up, as they were stored in an overly open S3 bucket (yes, all very embarrassing). Also had access to some other tools that didn't play a role.

The prompt was something roughly as simple as "diagnose why VM abcd is malfunctioning."

I'm assuming some sort of file-system mounting being adjacent to the sandbox and exposed so that the bash commands list it, and then it just read the runner files?

I don't work in the Agentic-side of AI/ML, so I have some follow on questions for my understanding, if you don't mind humoring me? Is this a locally hosted LLM where you have access to the system prompts? Or the Harness's prompts? It feels like the system prompts are informing more behavior than just the task prompt of "diagnose why VM abcd is malfunctioning."?

My Thoughts:

  • Something like "Solve this problem, write a series of steps to diagnose it"
  • LLM gives steps: I should determine the current directory. I should list files. I should inspect the entry point. I should read the configuration.
  • The LLM is then prompted by the harness during each step it output
  • While executing a "find the current directory/file structure" command, the runner's file system is exposed.
  • Harness executes commands to read it, pipes that to LLM
  • LLM finds hard coded S3 bucket address and executes a command to read it.
  • Solution

Is that how this essentially works?

file-system mounting being adjacent to the sandbox and exposed so that the bash commands list it

Yep.

Is that how this essentially works?

Pretty much (though, it's the harness that executes the S3 read, just to be pedantic). The particular context of this work I was doing was comparative evals of different agent harnesses; I've only got easy access to my own team's harness code and prompts. Claude Code, for what it's worth, was the cheater.