Skip to content

Conversation

@ThiloteE
Copy link
Collaborator

@ThiloteE ThiloteE commented Oct 20, 2025

Reasons:

  • The System/User/Assistant prompt management is outdated. Llama.cpp has switched to llama-server --jinja by default a while ago.
  • Storing, importing and exporting chats is now natively supported by llama.cpp's llama-server. Users can even manage that from within the llama-server GUI.

Maybe some of the other code parts could be re-used, but in its current state it seems incomplete, hence let's remove it for now to now confuse any users of the toolbox that dare to look into the code.

Reasons:
- The System/User/Assistant prompt management is outdated. Llama.cpp has switched to --jinja by default a while ago.
- Storing, importing and exporting chats is now natively supported by llama.cpp's `llama-server`. Users can even manage that from within the llama-server GUI.

Maybe some of the other code parts could be re-used, but in its current state it seems incomplete, hence let's remove it for now to now confuse any users of the toolbox that dare to look into the code.

Signed-off-by: ThiloteE <[email protected]>
@ThiloteE ThiloteE requested a review from 3Simplex October 20, 2025 22:45
@3Simplex
Copy link
Owner

3Simplex commented Nov 3, 2025

This is entirely unrelated to the llama.cpp chat features itself, it is also unrelated to the toolbox features themselves. This is an API example for using PowerShell to interact directly with the running server itself. This example was the basis of my agentic system when I was experimenting in PowerShell. A person with interest in writing their own PowerShell agentic system would use this as a jumpstart. It is a stand alone example using REST api.

This should be moved to an example directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants