Config error in vscode extension.

Open
#13,374 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 8 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
ubuntu, vscode

Research direction

The payload names no source file, so the entry point is the config loading and validation path that runs when the VS Code extension starts. Reproduce the failure on Ubuntu by pointing the extension at a local server on another machine, and capture the error that is currently swallowed or hidden. Done means that error text, or the config field it refers to, is shown prominently when setup fails. Ask the maintainers which config file and error channel to target before starting.

Written by the indexing model from the issue text.

Description

What error? I don't know, I was unable to find the log. Maybe this should be streamlined for the first time setup.

The system was Ubuntu 26.04, trying to connect with Ollama serving on another computer in local network.

Edit: wording.

Dominant language
TypeScript
Stars
36.5k
Forks
5.6k
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from continuedev/continue

All issues in continuedev/continue

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.