Offer Troubleshoot as a profile, and say plainly when it has no log
This commit is contained in:
@@ -59,6 +59,8 @@ as the GPU and UPS cards.
|
||||
| AI | Model residency, context size, VRAM, index size and staleness, tokens used today |
|
||||
| Conversations | The last `$AI_CHAT_HISTORY_MAX` chats. Click to reopen, × to delete |
|
||||
| Assistant | Ask a question without leaving the dashboard |
|
||||
| ⤢ | Expands the conversation to about two and a half times its height. Remembered |
|
||||
| Profile buttons | Which contract answers — General Chat, Varaverk Assistant, Code Sketcher, Troubleshoot |
|
||||
|
||||
---
|
||||
|
||||
@@ -93,6 +95,12 @@ Switching profile with the buttons keeps what is on screen but stops sending ear
|
||||
model. Carrying cited, retrieval-grounded answers into a mode with no retrieval makes the model
|
||||
keep referring to sources it can no longer see.
|
||||
|
||||
**Troubleshoot from here has no log open.** On the Scheduler tab it reads whatever log you have
|
||||
in front of you; picked from the dashboard there is nothing attached, so it says so and tells you
|
||||
how to give it evidence — open the log on the Scheduler tab, or name the script in the question,
|
||||
which resolves that script's run record and log on its own. What it will not do is describe a log
|
||||
it was never given.
|
||||
|
||||
## Conversations are shared with the AI tab
|
||||
|
||||
The same store backs both. Start a thread here, finish it on the AI tab, or the reverse — it is
|
||||
|
||||
Reference in New Issue
Block a user