Editorial: Two threads tie today's stories together — powerful new AI tools are collapsing old technical barriers (turning compiled games into browser playables), and ordinary people are using the same models to ask hard questions about what automation means for their lives. Both show capability running ahead of policy, and both demand clearer thinking about risk, incentives, and preservation.

In Brief

I've been extra nice to my agent recently

Why this matters now: Personal AI agents are moving from novelty to daily tools, so how people treat agents now shapes future UX, trust, and social expectations around automation.

A short Reddit post titled "I've been extra nice to my agent recently" on r/openclaw caught attention as a human vignette about how people relate to increasingly autonomous tools. The original post could not be retrieved, but the idea sits against a broader pattern: as agents gain autonomy, users often anthropomorphize and adjust behavior — sometimes out of gratitude, sometimes out of habit.

"Being able to make my computer do things – anything – by just talking to an agent running inside it is incredibly fun, addictive, and educational."

That quote, reported in community summaries, captures the emotional side. The practical takeaway: designers need to account for both social cues and task flows when building agents — politeness rituals can shape expectations and, in turn, the kinds of labor people will assign to these systems. (Source: Reddit post.)

Advice for writing instructions/agents.md for Opus 5.5 please

Why this matters now: Clear instruction files for Opus 5.5 can materially reduce errors and unpredictability when teams deploy Claude-family models as autonomous agents.

A developer thread requested help drafting an instructions/agents.md tailored to Opus 5.5. Commenters emphasized practical structure: a short role statement, explicit do/don't rules, concise examples, and a testing checklist. The stakes are mundane but real — better instructions mean fewer hallucinations and fewer surprises when the model takes action in production.

Anthropic says Opus 5.5 "puts the most important information up front" and testers say "it writes the way I do," so the community is trying to match that behavior with tight, example-driven rules. (Source: Reddit thread.)

Deep Dive

GTA 5, Modern Warfare 2, Halo, and many other games have been ported to browser thanks to the power of AI reverse-engineering

Why this matters now: AI-assisted reverse‑engineering is allowing hobbyists to decompile and recompile classic games to WebAssembly, putting major titles like Halo and GTA playable in a browser tab and raising urgent legal and preservation questions.

Reporters have noted a wave of fan projects that have made heavyweight console and PC titles playable in a browser — a feat that, until recently, required painstaking manual decompilation and months of reverse engineering. According to Destructoid's report, modders are now using generative models (reportedly variants of the Claude Opus family) to accelerate converting binary game code back into human‑readable source-like form, then recompiling portions into WebAssembly.

At the heart of the change is decompilation — the process of turning compiled binaries back into source-like code. Historically this was slow and error-prone; generative models are automating pattern recognition and filling in gaps, sometimes running dozens of agent instances in parallel. As one modder boasted, the community is scaling work with "currently 17 agents working in parallel," which speaks to a shift from single‑expert efforts to distributed, AI-augmented teams.

"With currently 17 agents working in parallel, we’re making progress at an incredible pace."

That capability has two obvious effects. First, preservationists and players celebrate — abandoned or flaky ports of beloved games become playable again without waiting for a publisher-backed remaster. Second, it creates a legal flashpoint. Publishers have responded with DMCA takedowns and threats, and the law doesn’t have tidy categories for AI-reconstituted code or community‑assembled playables. There are also technical caveats: these ports often lack original assets (textures, voice acting), can contain hallucinated or unsafe code sections generated by models, and may be expensive to produce because of heavy compute needs during decompilation and recompilation.

Beyond copyright, there are security risks. Turning binary formats into new executables and serving them in browsers creates attack surfaces — both in the tooling chain and in the distributed agents running on unvetted code. Researchers warn that hallucinated code inserted by models could open vulnerabilities or misbehave in subtle ways. Preservationists counter that community projects can be the only practical way to keep software playable as platforms age and original source is lost.

What to watch next:

  • Publisher responses: expect more DMCA takedowns and possibly broader legal tests over who owns the "playable code" once it has been reconstructed by AI agents.
  • Tooling safeguards: vendors may add provenance tracing, reproducibility checks, and automated security scans to decompilation pipelines.
  • Preservation coalitions: libraries, archives, and game studios might create sanctioned ways to surface old titles without requiring risky fan reverse-engineering.

The net result is a collision between a clearly useful preservation impulse and an unsettled legal/ethical environment. How the industry, archivists, and courts resolve that will determine whether these "vibe‑coded" browser ports survive beyond the news cycle.

Ask AI how likely AI is to take your job

Why this matters now: Public experiments like the Reddit "Ask AI how likely AI is to take your job" thread illustrate how model choice and framing produce wildly different automation-risk numbers — and why a single percentage is rarely the right answer for career decisions.

A Reddit thread on r/singularity encouraged people to feed resumes and job descriptions into large language models and automation-exposure tools to get percent‑chance estimates that their jobs will be automated. The results were messy: different models and tools produced widely varying probabilities because they measure different things — whole roles vs. tasks, historical trends vs. forward-looking scenario modeling, and different definitions of "automation."

Two well‑cited but superficially contradictory numbers often surface in these discussions. The U.S. Bureau of Labor Statistics has noted that "only 9% of workers in the U.S., and in the average OECD country, face a high risk of losing their job to automation" under their more conservative measures. On the other hand, McKinsey and other analysts estimate generative AI could automate "60% to 70% of current work activities before 2030." Those figures both hold truth when you remember they measure different things: the BLS isolates jobs with high probability of full displacement, while McKinsey counts tasks across jobs that could be automated or augmented.

This distinction matters for everyday workers. Jobs are bundles of tasks — many contain routine, automatable pieces (data entry, drafting boilerplate) alongside human‑centric work (negotiation, complex judgment, craft). Automation commonly changes job content rather than eliminating roles overnight. So when a model spits out "40% likely," what it's really saying depends on the algorithm, training data, and whether the analysis treats granular tasks or whole jobs.

Two practical takeaways:

  • Focus on task-level risk. Identify routine, repetitive tasks in your role that are easiest to automate, and then look for ways to upskill into the higher‑value parts of the job.
  • Treat AI risk estimates as signals, not verdicts. They can prompt planning — retraining, diversifying responsibilities, or adopting AI tools to augment productivity — but shouldn't replace nuanced career decisions.

The subreddit experiment also highlights a broader behavioral trend: people want a single number to reduce anxiety. But ambiguity is real here, and public policy (education, retraining, safety nets) will ultimately shape whether those numbers translate into hardship or opportunity.

Closing Thought

AI is lowering technical barriers and raising social and legal ones at the same time. Whether it's hobbyists reconstituting games in a browser or workers crowd-sourcing automation risk estimates, the new tools amplify human choices — about preservation, about careers, and about how we regulate capability. The clearest short-term defense is simple: be deliberate about incentives, require provenance and safety checks in toolchains, and use task-level analysis when thinking about automation risk.

Sources