Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

ai-sandbox-daytona: spawn().stdin.end() is a no-op while writableStdin: true, so stdin-fed harnesses (Claude Code, Codex) hang forever

未关闭
  • 哪里不对？
#1,926 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
64/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
backend, devtools

调研方向

Start by reading the Daytona spawn handle used by spawnNdjson and startJournaledAgent in ai-sandbox, then check how the Daytona API handles closing stdin and what tests cover stdin writes. Confirm that ending stdin delivers EOF and lets stdin-fed processes finish; the issue is resolved when the reproduction no longer hangs.

由索引模型根据 Issue 内容生成。

描述

TanStack AI version

1.0.0

Framework/Library version

React 19

Describe the bug and the steps to reproduce it

What happens

On a Daytona sandbox, a Claude Code run never starts working. claude -p starts, writes its config, and then waits with no output until the run is aborted. The claude process stays alive in the sandbox afterwards, because killableProcesses is false. Codex takes the same stdin path, so it hangs the same way.

Cause

DAYTONA_CAPS.writableStdin is true, so the harnesses send the prompt through stdin. spawnNdjson and startJournaledAgent in ai-sandbox call proc.stdin.write(input) and then proc.stdin.end(). Daytona's spawn handle implements end as a no-op:

stdin: {
  write: (data) =>
    this.sandbox.process.sendSessionCommandInput(sessionId, cmdId, data),
  end: () => Promise.resolve(),
},

sendSessionCommandInput delivers the bytes, but EOF never arrives. claude -p and codex exec read stdin to EOF before they begin, so they wait forever.

Minimal reproduction

import { daytonaSandbox } from "@tanstack/ai-sandbox-daytona";

const provider = daytonaSandbox({ apiKey: process.env.DAYTONA_API_KEY });

const h = await provider.create({} as never);

const read = node -e "let s='';process.stdin.on('data',d=>s+=d).on('end',()=>console.log(s))";


// 1. Through stdin: never exits.

const p = await h.process.spawn(read, {});

await p.stdin.write("hello");

await p.stdin.end();

console.log(await Promise.race([

p.wait().then((c) => exit ${c}),

new Promise((r) => setTimeout(() => r("still waiting after 20s"), 20_000)),

])); // -> "still waiting after 20s"


// 2. Through a file redirect: exits at once.

await h.fs.write("/tmp/prompt", "hello\n");

const q = await h.process.spawn(${read} < /tmp/prompt, {});

console.log(await q.wait()); // -> 0, prints "hello"

Measured on a real Daytona sandbox (daytonaio/sandbox:0.8.0): case 1 was still waiting after 20 s, and case 2 exited 0 in about 2.4 s.

Affected harnesses

Harness How the prompt is passed On Daytona
ai-claude-code stdin (claude -p) hangs
ai-codex stdin hangs
ai-grok-build (NDJSON) argv (-p "") not affected
ai-opencode HTTP to opencode serve via ports.connect not affected

Suggested fix

Either of these would fix it:

  1. Set writableStdin: false for Daytona until EOF can be delivered. The harnesses already have this path: they write the prompt to a file and run … < file, and it works on Daytona today. This is the smallest change.
  2. Implement end() for real, if the Daytona session API can close a command's stdin (for example, a PTY session, which #1085 mentions). If it cannot, writableStdin: true should not be advertised.

A test for whichever fix is chosen: spawn a process that reads stdin to EOF, then write and end, and assert that it exits.

Workaround

We wrap the provider so that it and its handles report writableStdin: false:

const handleWithoutStdin = (h: SandboxHandle) =>
  Object.defineProperty(h, "capabilities", {
    value: { ...h.capabilities, writableStdin: false },
  });
// applied to provider.capabilities(), create(), resume(), restoreSnapshot()

After this, ai-claude-code takes the prompt-file path, and the prompt reaches the CLI.

Related: #1085 (session stdin, PTY kill).

Your Minimal, Reproducible Example - (Sandbox Highly Recommended)

Code Sanbox

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

None

Terms & Code of Conduct
  • I agree to follow this project's Code of Conduct
  • I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
主要语言
TypeScript
星标
3.2k
派生
372
平均合并
1 天 14 小时
30 天内合并 PR
241

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

TanStack/ai 的其他 Issue

查看 TanStack/ai 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。