entropyconquers claims the released MIT-licensed simfleet CLI attributes simulator devices and ports to specific Claude Code and Codex sessions via session-ID-tagged claims, ending device collisions, Metro port clashes, and memory thrash when running parallel coding agents on one Mac; adoption by multi-agent developers would establish session-scoped device-claim coordination as standard parallel-agent infrastructure.
state: seedheat: lowuncertainty: mediumnovelscott: mediumparallel-coding-agents agent-orchestration developer-toolingentropyconquers
What is this?
entropyconquers has released simfleet, an MIT-licensed CLI that lets multiple AI coding-agent sessions (Claude Code, Codex) share one Mac's simulators without collisions: each session registers session-ID-tagged claims on specific simulator devices and ports, ending device grabs, Metro bundler port clashes, and the memory thrash of duplicate simulators. The supplied snippets never mention simfleet or entropyconquers directly — they ground the surrounding space: a crowded 2026 ecosystem of parallel-agent orchestrators (Claude Squad, dmux, kmux, Agent of Empires, ccmanager, Superset) that coordinate almost entirely via git-worktree and file-level isolation, with one project explicitly marking file-claim coordination 'advisory/experimental, not yet reliable under concurrency,' and Anthropic now shipping native multi-session oversight in Claude Code 2.1.139. Against that backdrop, device/port-level attribution would be a genuinely distinct coordination layer from the worktree mainstream — but the tool's existence, license, and mechanics rest on the case's own claim, not on anything the supplied snippets establish.
Why it matters to Scott
Novel to his canon rather than convergent: nothing in his wikis argues session-scoped device/port claims, and the case actually bounds his goal-world-isolation thesis — where duplicating a simulator world per agent thrashes the host, agents share one fleet behind an external session-ID-tagged claims registry, i.e. his shared-blackboard/durable-external-coordination-state pattern applied to hardware, structurally kin to his singleton GPU job queue (one arbiter over contended local hardware so parallel clients don't collide). Medium not high: simfleet is a small, unverified macOS/iOS-simulator CLI — the supplied snippets never confirm it exists — on a platform his demonstrated Linux/WSL2 stack doesn't evidence, in a niche the radar already tracks via the Manzanas cases; it's a liftable lease pattern for contended parallel Claude Code/Codex sessions, not an argument-changer.
ip:concept.goal-world-isolationdev:concept.singleton-gpu-job-queueip:concept.shared-blackboardradar:manzanas-parallel-ios-agent-testingradar:manzanas-ios-agent-simulator-fleetradar:concept.multi-agent-orchestration
queries asked of Scott's wikis
- parallel coding agents one Mac resource contention
- agent coordination claims leases locks protocol
- git worktree isolation limits shared resources
- iOS simulator Metro port conflicts automation
- session identity first-class in agent harnesses
- multi-agent memory footprint local dev
Measured heat
now 0 pts/hpeak 1 pts/hcomments 0/hpeers p0momentum: steady2 platformsage 410h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p48 vs 1032 stories at the 336h mark (now 410h old) — ahead of acs-local-skill-risk-catalog (1.1x), behind agentgit-accountless-agent-handoffs (0.9x)
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-09-28T12:23:34Z
origin walked (opencode/cheap-glm, conf 0.85): anchor reddit.post.1wsb1l7 -> echo.github.77ca3d9fdc by entropyconquers
2026-09-28T12:10:01Z
grounded: novel/medium — Novel to his canon rather than convergent: nothing in his wikis argues session-scoped device/port claims, and the case actually bounds his goal-world-isolation
2026-09-28T12:01:32Z
case created — Released first-party artifact solving a concrete parallel-agent contention problem (device/port attribution) not covered by the existing file- and workspace-coordination cases.
Decision trace
- 09-29 22:31review_screenNew comments are only third-party design discussion and opinions (single-flight builds, fail-closed lanes, cancellation/stale-claim questions) plus anecdotal restatement of the already-known device/Me
- 09-29 22:31review_screenjev screen borderline (noul=0.35) — luna review
- 09-28 23:21sensor_dirtycomment_update
- 09-28 22:23promote_anchororigin walk conf 0.85
- 09-28 22:10groundNovel to his canon rather than convergent: nothing in his wikis argues session-scoped device/port claims, and the case actually bounds his goal-world-isolation thesis — where duplicating a simulator w
- 09-28 22:01createReleased first-party artifact solving a concrete parallel-agent contention problem (device/port attribution) not covered by the existing file- and workspace-coordination cases.