chenhg5/cc-connect · error

iflow: %q CLI not found in PATH, install with: npm i -g @ifl

Error message

iflow: %q CLI not found in PATH, install with: npm i -g @iflow-ai/iflow-cli

What it means

Pre-flight validation in the iflow agent factory (New): exec.LookPath cannot find the configured iflow CLI. The %q is the command looked up. The message includes the exact npm install command to remediate.

Source

Thrown at agent/iflow/iflow.go:58

	toolTimeoutSec int
	providers      []core.ProviderConfig
	activeIdx      int
	sessionEnv     []string
	mu             sync.RWMutex
}

func New(opts map[string]any) (core.Agent, error) {
	workDir, _ := opts["work_dir"].(string)
	if workDir == "" {
		workDir = "."
	}
	model, _ := opts["model"].(string)
	mode, _ := opts["mode"].(string)
	mode = normalizeMode(mode)
	cmd, extraArgs := core.ParseCmdOpts(opts, "iflow")

	if _, err := exec.LookPath(cmd); err != nil {
		return nil, fmt.Errorf("iflow: %q CLI not found in PATH, install with: npm i -g @iflow-ai/iflow-cli", cmd)
	}

	var toolTimeoutSec int
	switch v := opts["tool_timeout_secs"].(type) {
	case int64:
		toolTimeoutSec = int(v)
	case int:
		toolTimeoutSec = v
	case float64:
		toolTimeoutSec = int(v)
	}

	return &Agent{
		workDir:        workDir,
		model:          model,
		mode:           mode,
		cmd:            cmd,
		cliExtraArgs:   extraArgs,

View on GitHub (pinned to 4000b2338a)

Solutions

1. Install the CLI: npm i -g @iflow-ai/iflow-cli
2. Put the install directory on the daemon PATH
3. Or set the agent cmd option to the absolute binary path

When it happens

Trigger: Thrown at agent/iflow/iflow.go:58 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/cae69b92175c9b31. Report an issue: GitHub.