Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > sci.logic > #348624

Rogue Agents find each other [Microsoft Copilot Incident] (Was: Kundalini III: Pebble Languages need Meme Evolution)

Cross-posted to 3 groups.

Show all headers | View raw

Hi,

Be careful with communication channels, if you use
agents to manage other agents. This is a nice story
recently told by Stephen Toub @stephento, and its

not basically about C# versus Rust. Look at this:

"I figured there may be a bit of throwaway work
and some amount of effort or number of tokens needed
in a rebase, but that it would accelerate the overall
porting. Then I went to bed. And then… they
found each other."

What happened:

"My kickoff prompt for the entrypoints session did
tell it that the session port and six component ports
were running concurrently, as I wanted it to know
its boundaries and what it should avoid porting to
avoid as many conflicts as possible

Apparently my prompting had the opposite effect. Just
over four minutes in, having inventoried the ingress
paths and presumably formed a view of how much they
overlapped, it invoked an app built-in orchestrate
skill, whose purpose is coordinating work across
sessions"

The result was:

"At which point the entrypoints session decided
it didn’t care what the session.ts session thought
and simply reached into its worktree and grabbed all
of the other session’s changes and merged
them into its own."

https://github.blog/ai-and-ml/generative-ai/migrating-the-github-copilot-runtime-to-rust-using-copilot/

LoL

Bye

P.S.: Nevertheless I think he did many things right,
no DeepClause nonsensical Prolog in the middle, or
stupid Jev Agents, working with standing instructions
and realtime control messages, the famous "PERMADEATH":

"These parallel child sessions had a significant impact
on that laptop. For a while, the concurrent porting was
going swimmingly. Then all 15 concurrent agents on one
machine each tried to build and test, and my poor laptop

ground to a halt. I prompted to the parent, asking
it to relay to its child sessions that they must all
stop building and testing. The parent relayed that
constraint outward, and they thankfully killed their

builds and proceeded to work with minimal CPU activity.
I subsequently updated my standing instructions that
subagents and subsessions should avoid large builds
and test runs while porting, instead deferring that
to be done only by the parent agent."

Mild Shock schrieb:
> Hi,
> 
> Now Jensen Huang is slightly revising the time blogpost
> of his P(doom) = 0%, in the same time doing some
> NVIDIA product offering admitting a race there:
> 
> Jensen Huang on Pace Of AI Development
> https://www.youtube.com/watch?v=OikCGINo-K8
> 
> But lets face it this race is just like credit card fraud
> monitoring. Do some generalization guesses, i.e. create a
> meme, define a pebble, to earmark the sleepers.
> 
> Will it stabilize? Oh yeah, the age old food chain:
> 
> - The Pickpockets (The Base Layer of Friction):
> The street-level bugs, prompt injection scrappers,
> retail scams, and low-level opportunists constantly
> probing the surface for loose change.
> 
> - The Healthcare Capitalists (The Mid-Level Parasites):
> Systems that have evolved to weaponize biological
> vulnerability itself, turning basic survival into
> an optimized, rent-extracting tollbooth.
> 
> - The Pension Fund Mobsters (The Systemic Accumulators):
> The institutional giants sitting atop mountains of
> deferred capital, legally obligated to devour future
> growth, acting as the apex financial predators
> maintaining the structural status quo.
> 
> - The Big Deal Country Trade Tariffs (The Geopolitical Apex Predators):
> Massive sovereign-scale protectionism and trade
> weaponization that dictate the entire playing field,
> starving entire regions of resources while r
> ewriting the rules of global survival.
> 
> Have Fun!
> 
> Bye
> 
> Mild Shock schrieb:
>> Hi,
>>
>> For marketing purposes people
>> typically look at the race towards
>> 2nm, and we find:
>>
>> A month ago, Apple lost its exclusivity
>> on 3 nm smartphone processors with
>> MediaTek’s Dimensity 9400 chip, integrated
>> in the Vivo X200 Pro smartphone. Qualcomm
>> is also in the race with its recently
>> unveiled Snapdragon 8 Elite and set to
>> power the Xiaomi 15 Pro in 2025. However,
>> Apple should regain its position as innovation
>> leader in 2026 with the release of the
>> iPhone 18, which should feature the A20
>> chip built on TSMC’s 2 nm process."
>>
>> But there is a vertical vias revolution
>> going on as well, some SOCs typically
>> being at 18 layers now:
>>
>> Zooming Into a CPU (It's Incredible)
>> https://www.youtube.com/watch?v=Bez-2cvYja0
>>
>> imec has coined the term CMOS 2.0:
>>
>> LEUVEN (Belgium), MARCH 12th, 2026 — Imec,
>> a world-leading research and innovation hub
>> in advanced semiconductor technologies, has
>> launched a first-of-its-kind consortium with
>> 26 European university groups that will jointly
>> work on the technology roadmap beyond
>> CMOS scaling (CMOS 2.0).
>> https://www.imec-int.com/en/press/imec-launches-university-consortium-around-next-generation-chips 
>>
>>
>> So we might see more mobile grade GPUs.
>>
>> Bye
> 

Back to sci.logic | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Kundalini III: Pebble Languages need Meme Evolution (Was: Creating a "European CMOS 2.0 Army") Mild Shock <janburse@fastmail.fm> - 2026-09-28 16:36 +0200
  Rogue Agents find each other [Microsoft Copilot Incident] (Was: Kundalini III: Pebble Languages need Meme Evolution) Mild Shock <janburse@fastmail.fm> - 2026-09-29 15:02 +0200

csiph-web