chenhg5/cc-connect · error

opencodeSession: stdout pipe: %w

Error message

opencodeSession: stdout pipe: %w

What it means

Wraps a failed exec.Cmd.StdoutPipe() in opencodeSession.Send while preparing the opencode CLI subprocess. Pre-spawn pipe allocation failure — practically always OS fd exhaustion, not an opencode issue.

Source

Thrown at agent/opencode/session.go:101

	chatID := s.CurrentSessionID()
	isResume := chatID != ""

	args := s.buildRunArgs(prompt, imagePaths, chatID)

	slog.Debug("opencodeSession: launching", "resume", isResume, "args", core.RedactArgs(args))

	cmd := exec.CommandContext(s.ctx, s.cmd, args...)
	cmd.Dir = s.workDir
	env := os.Environ()
	if len(s.extraEnv) > 0 {
		env = core.MergeEnv(env, s.extraEnv)
	}
	cmd.Env = env

	stdout, err := cmd.StdoutPipe()
	if err != nil {
		return fmt.Errorf("opencodeSession: stdout pipe: %w", err)
	}

	var stderrBuf bytes.Buffer
	cmd.Stderr = &stderrBuf
	cmd.Stdin = strings.NewReader(prompt)

	if err := cmd.Start(); err != nil {
		return fmt.Errorf("opencodeSession: start: %w", err)
	}

	s.wg.Add(1)
	go s.readLoop(cmd, stdout, &stderrBuf)

	return nil
}

func (s *opencodeSession) stageImages(prompt string, images []core.ImageAttachment) (string, []string, error) {
	if len(images) == 0 {

View on GitHub (pinned to 4000b2338a)

Solutions

1. Raise the file-descriptor limit
2. Run fewer concurrent opencode sessions
3. Look for fd leaks in the daemon

When it happens

Trigger: Thrown at agent/opencode/session.go:101 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of chenhg5/cc-connect@4000b2338a (2026-09-06). Data as JSON: /api/errors/4913bdfe881ca582. Report an issue: GitHub.