CLI Feedback

[bdougie]

🚀 We just launched Continue CLI - async AI agents in your terminal!
We'd love your feedback on the new CLI tool for building async coding agents. What workflows would you automate? Any feature requests or use cases we should consider?

Try it: npm i -g @continuedev/cli

Docs: https://docs.continue.dev/guides/cli
Announcement: https://x.com/continuedev/status/1958591429804269906

[Igorgro]

I have a negative experience with getting started on Linux. When I first launched a cli it caused excessive disk load while showing nothing. After a 5 minutes of empty console it showed a prompt asking for either logging in to Continue or to use Anthropic key. I wanted to use local models and nothing of that options was suitable for me, so I tried to exit the cli, but it does not react to Ctrl-C, neither Ctrl-d. The only way to exit is to send SIGKILL. I hope the next updates will make it at least runnable

[Igorgro]

I used lsof and noticed that during that long startup it scans the whole home directory. What the hell is going on here? Is that freaking malware?

[Igorgro]

I found the code resposible for that

continue/extensions/cli/src/systemMessage.ts

Line 93 in 3543454

${getDirectoryStructure()}

. While it is not a malware, I think it's totally incorrect to send such data as current working directory, OS name and the whole directory tree to external services without explicit user consent. Also, I noticed that this project uses sentry to catch error, then me as a user cannot be sure that that info won't be sent to third-parties without my agreement

[bdougie]

Thanks for the feedback @Igorgro

[bdougie]

Looks like a related question came up in the discord. Cross linking here https://discord.com/channels/1108621136150929458/1156679146932535376/1412737814768128001

Points to #7528

[chrisbratlien]

Trying out @continuedev/cli v1.4.35 (beta) on Windows PowerShell and also WSL.

I use the VS Code extension all the time. When trying out CLI, I noticed a few things which could improve:

1. The default config.yaml is not detected on WSL or on Windows without supplying --config path parameter

2. CLI can't find Ollama AUTODETECT models in the config below whether using CLI in PowerShell or WSL bash. Continue VS Code extension has no problem finding them in either PowerShell or WSL bash.

  - name: Ollama Autodetect
    provider: ollama
    model: AUTODETECT
    apiBase: http://ollama.local:11434
    capabilities:
      - tool_use
    roles:
      - apply
      - edit
      - chat
      - summarize
      - autocomplete

It shows up as one entry in the Select Model list:

[aaronpliu]

experiencing the issue as @Igorgro , it often stuck and no response, and hard to exit even if press cmd+C/ctrl+C, and wait for a long time after input /exit.
I have a proxy setting in my machine, and add the apiBase IP in bypass list since it no need proxy to access. But in CLI (v1.5.7), cannot access remote API, in spite of running command cn --config ~/.continue/config.yaml, using same config as continue.

[lagosr-github]

Trying the continue.dev cli on debian. - some feedback.

1 - The cn cli ignores the stream: false directive from the config.yaml file (it always uses streaming, would be nice to support non-streaming too if possible)

2 - have not found an ollama model that works well with cn cli .. either you get "Error: 400 registry.ollama.ai/library/ does not support tools" . or the model does poorly when function calling (like qwen 2.5 coder)

A section in the docs for suggested models to use would be awesome.

Some positive feedback -- worked great with Gemini 2.5 Pro.