Skip to content
CC Switch WikiUnofficial Community Wiki

bash: cannot set terminal process group - cc-switch

Quick fix

A known 3.18.0 bug when checking the local proxy environment on Linux. Downgrade below 3.18.0 and configure the proxy in the terminal by hand.

Symptom

Section titled “Symptom”
Error output
bash: 无法设定终端进程组 (1492): 对设备不适当的 ioctl 操作 bash: 此 shell 中无任务控制
English translation

bash: cannot set terminal process group (1492): Inappropriate ioctl for device. bash: no job control in this shell

Cause

Section titled “Cause”

The cc-switch local proxy environment check and configuration features have several defects. On Linux in 3.18.0, invoking bash to check the proxy triggers the ioctl job control error. At the same time, the standalone GUI proxy configuration feature was removed by the author for being incomplete, and proxying is not supported at all in IDE plugins such as VSCode. Forcing a proxy in an external terminal also makes Codex reconnect continuously, or breaks the stream during Claude Code tool calls.

Fix

Section titled “Fix”

  1. Downgrade cc-switch below 3.18.0 to avoid the ioctl error from the local environment check on Linux.

  2. Give up on the GUI proxy configuration and set the proxy environment variables directly in a system terminal ($env:http_proxy= on Windows, export http_proxy= on macOS/Linux).

  3. If the stream breaks during Claude Code tool calls, launch the CLI from the terminal built into the cc-switch console, or use claude-code-router instead.

Affected Versions

Section titled “Affected Versions”
Toolcc-switch
Version3.13.0 - 3.18.0
PlatformsWindowsmacOSLinux

Source Issues

Section titled “Source Issues”

This page is distilled from 5 real issues

FAQ

Section titled “FAQ”
Why does configuring a proxy in the VSCode Claude Code plugin have no effect?
The author stated plainly that the plugin cannot be proxied and cannot hot-switch; proxying and hot switching only work in the CLI.
After configuring the local proxy, the Claude CLI works without tool calls but breaks the stream as soon as one runs. What now?
That is a problem with proxy forwarding in an external terminal. Launch claude from the terminal inside the cc-switch console, or switch to claude-code-router.
Section titled “Related problems”
unexpected status 502 Bad Gateway CodexSet 127.0.0.1 to direct in your proxy software, or configure NO_PROXY in the Codex environment, so the local proxy is not intercepted.7 issues mergedCodex API key automatically modified leading to model xxx not foundUpgrade to v3.19.2+ to fix incorrect API Key convergence caused by reading auth.json when multiple suppliers share the same address.24 issues mergedIt says 1.6 billion used — usage statistics spiking - CodexUpgrade cc-switch to v3.18.0 to fix the sub-agent history replay double-count bug; it rebuilds the polluted Codex usage data automatically.5 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.