[x] Let's add prompt templating and store/load the prompts from either 1 file or different files for each template. We will do this as a first step before implementing @CHAT-IDEA.md 
# Idea for interactive "chat app" that lets me manipulate the full gateway call and send a call to the gateway, and monitor the results. The end would go to the gateway would operate on dev-server.
## Mode switch- We can change between manipulating the call that gets sent to the gateway and the first gateway call that gets sent to the model.
## UI: Built for a single call, tooling model, just like what is implemented on prod and dev now. Top of screen: select mode(Gateway call vs Model call), independant template selector(based on mode). Top half: text box with template preloaded, editable, send button. Bottom half, scollable running log of gateway send, rcon, thinking(if available), gateway recieve, basically everything useful including what happens on the server.
## Log is created in a separate file from training. It can be accessed later for training audits and to create training data. Training log records results as if the model were operating normally.
## There would be different templates for god mode or sudo or self play, each a gateway call with the corresponding first model call.
# Take design liberties if you can achieve the same result and make a better ui.
# Implement existing applications if they fit the use case.
# caddy is pct 600 on pve241, this would be chat.api.mortdec.ai hidden behind google oauth. It would run on pct 650 which is on pve112