Cairn
NousResearch/hermes-agent

Daytona sandbox not receiving terminal env_passthrough variables

Cluster 5995 · environments. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

Most members concern the Daytona backend not forwarding allowlisted terminal.env_passthrough variables into sandbox command execution, with several fix PRs and a bug report. One feature request broadens the topic to other remote backends (SSH, Singularity, Modal).

Open issues1

  • Issue#59286[Bug]: terminal env_passthrough not honored by Daytona backend — allowlisted env never reaches the sandbox

Open PRs1

  • PR#59296fix(tools): forward allowlisted env vars to Daytona sandbox exec

4 PRs closed without merging

From the close comments: stale or abandoned 2 · duplicate 1 · superseded by another PR 1

  • #59424 fix: Daytona backend now honors env_passthrough · superseded by another PR
  • #59620 fix(daytona): forward env_passthrough variables to sandbox process.exec() (#59286) · duplicate → #59296
  • #59687 fix(daytona): honor terminal.env_passthrough in sandbox commands · stale or abandoned
  • #60701 fix(daytona): forward env_passthrough variables to sandbox processes (#59286) · stale or abandoned
Closed issues · 1
  • Closed#5995[Feature]: preserve env passthrough in remote terminal backends (Daytona, SSH, Singularity, Modal)
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.26: 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
1
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/5995.json
cluster/5995.md