stakwork / stakwork/stakgraph

Stakgraph: Set Base URL command does not persist when connected to remote server

Open
#92 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
112
Forks
21
Avg merge
5h 55m
Merged PRs (30d)
115

Description

Description

When using the VSCode extension, the Stakgraph: Set Base URL command appears to successfully set the new base URL. However, when the extension is connected to a remote server, initiating a new chat session using Stakgraph Chat unexpectedly reverts the base URL back to localhost.

Steps to Reproduce:

  • Open VSCode and connect to a remote server
  • Run the command Stakgraph: Set Base URL and enter a valid remote URL e.g. https://mcp.repo2graph.sphinx.chat/
  • Start a new chat session via Stakgraph Chat.

Observe that the base URL used for the chat session reverts to http://localhost.

Expected Behavior:

  • The base URL set via Stakgraph: set base url should persist across all operations, including when connected to a remote server and initiating a new chat session.

Actual Behavior:

  • The base URL is reset to localhost when starting a chat session after setting it on a remote connection.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Reproduce the issue through the VSCode extension's “Stakgraph: Set Base URL” command and the “Stakgraph Chat” entry point while connected to a remote server. Trace how the configured URL is stored and how a new chat session selects its URL; done means the configured remote URL remains in use instead of reverting to http://localhost.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.