Cairn

Daytona sandbox naming and recreation conflicts

NousResearch/hermes-agent · cluster 28299 · environments

Data as of

4 open items. Fix attempted, not merged.

The short answer

2open issues
2open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 2 PRs.

These issues and fixes address two related Daytona backend problems: non-unique sandbox names causing conflicts during concurrent use, and persistent sandboxes resuming without checking for image changes or supporting forced recreation.

Open issues2

  • Issue#28299Daytona terminal backend: all sandboxes named "hermes-default" → DaytonaConflictError on concurrent use
  • Issue#63361Daytona persistent sandbox resumes by name without image comparison; cleanup() lacks force_remove so callers cannot force recreation

Open PRs2

  • PR#28777fix(daytona): use unique sandbox names
  • PR#63368fix(daytona): recreate persistent sandboxes after image changes

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #28391 fix(daytona): make sandbox names unique per instance to unblock concurrent multi-agent · stale or abandoned
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
environments
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/28299.json
cluster/28299.md