mirror of
https://github.com/ggerganov/llama.cpp.git
synced 2024-11-01 15:40:21 +01:00
82 lines
3.7 KiB
Markdown
82 lines
3.7 KiB
Markdown
|
|
||
|
# SimpleChat
|
||
|
|
||
|
by Humans for All.
|
||
|
|
||
|
|
||
|
## overview
|
||
|
|
||
|
This simple web frontend, allows triggering/testing the server's /completions or /chat/completions endpoints
|
||
|
in a simple way with minimal code from a common code base. Inturn additionally it tries to allow single or
|
||
|
multiple independent back and forth chatting to an extent, with the ai llm model at a basic level, with their
|
||
|
own system prompts.
|
||
|
|
||
|
The UI follows a responsive web design so that the layout can adapt to available display space in a usable
|
||
|
enough manner, in general.
|
||
|
|
||
|
NOTE: Given that the idea is for basic minimal testing, it doesnt bother with any model context length and
|
||
|
culling of old messages from the chat.
|
||
|
|
||
|
NOTE: It doesnt set any parameters other than temperature for now. However if someone wants they can update
|
||
|
the js file as needed.
|
||
|
|
||
|
|
||
|
## usage
|
||
|
|
||
|
One could run this web frontend directly using server itself or if anyone is thinking of adding a built in web
|
||
|
frontend to configure the server over http(s) or so, then run this web frontend using something like python's
|
||
|
http module.
|
||
|
|
||
|
### running using examples/server
|
||
|
|
||
|
bin/server -m path/model.gguf --path ../examples/server/public_simplechat [--port PORT]
|
||
|
|
||
|
### running using python3's server module
|
||
|
|
||
|
first run examples/server
|
||
|
* bin/server -m path/model.gguf
|
||
|
|
||
|
next run this web front end in examples/server/public_simplechat
|
||
|
* cd ../examples/server/public_simplechat
|
||
|
* python3 -m http.server PORT
|
||
|
|
||
|
### using the front end
|
||
|
|
||
|
Open this simple web front end from your local browser
|
||
|
* http://127.0.0.1:PORT/index.html
|
||
|
|
||
|
Once inside
|
||
|
* Select between chat and completion mode. By default it is set to chat mode.
|
||
|
* If you want to provide a system prompt, then ideally enter it first, before entering any user query.
|
||
|
* if chat.add_system_begin is used
|
||
|
* you cant change the system prompt, after it is has been submitted once along with user query.
|
||
|
* you cant set a system prompt, after you have submitted any user query
|
||
|
* if chat.add_system_anytime is used
|
||
|
* one can change the system prompt any time during chat, by changing the contents of system prompt.
|
||
|
* inturn the updated/changed system prompt will be inserted into the chat session.
|
||
|
* this allows for the subsequent user chatting to be driven by the new system prompt set above.
|
||
|
* Enter your query and either press enter or click on the submit button.
|
||
|
If you want to insert enter (\n) as part of your chat/query to ai model, use shift+enter.
|
||
|
* Wait for the logic to communicate with the server and get the response.
|
||
|
* the user is not allowed to enter any fresh query during this time.
|
||
|
* the user input box will be disabled and a working message will be shown in it.
|
||
|
* just refresh the page, to reset wrt the chat history and or system prompt and start afresh.
|
||
|
* Using NewChat one can start independent chat sessions.
|
||
|
* two independent chat sessions are setup by default.
|
||
|
|
||
|
|
||
|
## Devel note
|
||
|
|
||
|
Sometimes the browser may be stuborn with caching of the file, so your updates to html/css/js
|
||
|
may not be visible. Also remember that just refreshing/reloading page in browser or for that
|
||
|
matter clearing site data, dont directly override site caching in all cases. Worst case you may
|
||
|
have to change port. Or in dev tools of browser, you may be able to disable caching fully.
|
||
|
|
||
|
Concept of multiple chat sessions with different servers, as well as saving and restoring of
|
||
|
those across browser usage sessions, can be woven around the SimpleChat/MultiChatUI class and
|
||
|
its instances relatively easily, however given the current goal of keeping this simple, it has
|
||
|
not been added, for now.
|
||
|
|
||
|
By switching between chat.add_system_begin/anytime, one can control whether one can change
|
||
|
the system prompt, anytime during the conversation or only at the beginning.
|