[BUG] Error: write ENOBUFS

Environment

• Platform (select one):
• [ X ] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• Claude CLI version: 1.0.95<!-- output of claude --version -->
• Operating System: Oracle Linux 9<!-- e.g. macOS 14.3, Windows 11, Ubuntu 22.04 -->
• Terminal: mate-terminal <!-- e.g. iTerm2, Terminal App -->

Bug Description

<!-- A clear and concise description of the bug -->

lots of parallel tasks crashed and the terminal was redrawing/jumping around like crazy:

   Model: Sonnet 4  |  Ctx: 125.8k  |  ⎇ main  |  (+18,-12)
  ⏵⏵ accept edits on (shift+tab to cycle)
node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: write ENOBUFS
    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
    at writevGeneric (node:internal/stream_base_commons:142:3)
    at Socket._writeGeneric (node:net:969:11)
    at Socket._writev (node:net:978:8)
    at doWrite (node:internal/streams/writable:596:12)
    at clearBuffer (node:internal/streams/writable:775:5)
    at onwrite (node:internal/streams/writable:653:7)
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:105:10)
Emitted 'error' event on WriteStream instance at:
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  errno: -105,
  code: 'ENOBUFS',
  syscall: 'write'
}

Steps to Reproduce

not sure, just hit it while running tons of tasks

Expected Behavior

not crash

Actual Behavior

crash

More info

● Task(Task: Fix package-name-no-slash fixtures (using general-purpose agent)

      Prompt: Fix fixtures for package-name-no-slash rule to fail validation:

      1. Read packages/validation/src/rules/package-rules/package-name-no-slash.ts to understand validation logic
      2. Read failing fixtures: test-package-no-name-field, test-package-simple-name, test-package-valid-scoped
      3. Modify fixtures to create validation failures the rule will detect
      4. Run: npx vitest run -t 'Fixture Test.*package-name-no-slash' packages/validation/
      5. If test fails, repeat steps 3-4
      6. Respond with only SUCCESS or FAIL: reason

      CONSTRAINTS:
      - ONLY use npx vitest command shown above (no pipes, no other commands)
      - ONLY modify fixture files using tools, never create test files
      - Fixtures must fail validation for tests to pass)
...
● Task(Fix package-deps-import-style-canonical fixtures)

● Task(Fix package-exports-fields-complete-incomplete fixtures)

● Task(Fix package-exports-no-renaming fixtures)

● Task(Fix package-exports-structure-incomplete fixtures)

● Task(Fix package-exports-structure-missing-dev fixtures)

● Task(Fix package-exports-structure-missing-exports fixtures)

● Task(Fix package-exports-structure-string fixtures)

● Task(Fix package-exports-structure-wrong-dev fixtures)

● Task(Fix package-exports-tsup-sync fixtures)

● Task(Fix package-imports-no-js-extensions fixtures)

● Task(Fix package-name-no-slash fixtures)

● Task(Fix package-scripts-use-rss-custom-script fixtures)

● Task(Fix package-scripts-use-rss-exact-match fixtures)

● Task(Fix package-scripts-use-rss-missing-scripts fixtures)

● Task(Fix package-tsconfig-forbidden-inheritance-overrides fixtures)

● Task(Fix package-tsconfig-path-boundaries-escape-parent fixtures)

● Task(Fix package-tsconfig-use-common-extends fixtures)

● Task(Fix package-tsup-config-required fixtures)

● Task(Fix package-tsup-entry-basename-match fixtures)

● Task(Fix package-tsup-extends-shared-base fixtures)

● Task(Fix package-tsup-no-redundant-overrides fixtures)

● Task(Fix package-umbrella-export-completeness fixtures)

● Task(Fix package-validation-exception-undefined fixtures)

● Task(Fix workspace-alias-orphaned-public fixtures)

... and more