server: report the isolate working directory from get_info - #26773
Merged
ngxson merged 2 commits intoAug 8, 2026
Conversation
Without an explicit cwd, get_info fell back to the server process working directory even when a tools runtime was configured. That named a host path no tool would ever run in, since an isolate starts in a directory of its own. It now asks the isolate for its working directory in that case, and keeps the process one only when the tools run on the host.
ngxson
reviewed
Aug 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
get_info reports the working directory the tools actually run in.
When a tools runtime is configured, the tools run inside the isolate, which starts in a directory of its own. get_info was still reporting the server process working directory, so it named a host path nothing would ever run in. It now asks the isolate instead.
Nothing changes when the tools run on the host, or when a working directory is set from the WebUI: that value is still reported as is.
Additional information
Without fix, this return the llama-server CWD :
built-in tools on a minimalist/basic telegram bot
UI CWD work as before :
Requirements