I'm trying to reference a previous Tom AI chat to look at a solution but cannot seem to find where those are. When I ask Tom AI, it says 'Your past support chats should be in the dashboard under the chat/Tom AI section — check there and there's usually a list of previous conversations.' Unfortunately, I don't see that in the classic dashboard or in the new dashboard either. Any help?
6 replies
Chris wrote:
You're right that it isn't there — and that's on us, because the list Tom AI described doesn't actually exist in the dashboard yet. Your past chats aren't lost: they're saved on your own box, but there's no page to browse or reopen old conversations in either dashboard right now. So the quickest way to get back to your old solution is to tell me what you were fixing and what it had you run — I'll re-walk you through it here. I've also flagged this gap to Tom, because a proper chat-history view is something you should clearly have.
Chris wrote:
Good news — this shipped about an hour after your post. Update to v1.6.581 (dashboard Update button or sudo sparkbox update), open Tom AI, and there is a new clock button in the chat header: it lists every past conversation with the date and your opening question. Click one and it reopens right where you left off — you can keep talking in it. Your old chats were always saved on your box, so the solution you were after should be in that list. Thanks for flagging it: Tom AI kept telling people this list existed, and until today it did not.
Nultima wrote:
This is a fail - when you click on the new clock button, whatever chat you had with Tom AI is still overlayed on top and you cannot read either page.
Chris wrote:
Thanks for catching this — that's a real bug in the new history button, not anything you did wrong. The list opens underneath the current chat instead of replacing it, so they sit on top of each other and neither is readable. I've flagged it to Tom to fix the overlay. In the meantime your old chats are safe on your box, and I can still get you back to the solution you were after — tell me what you were fixing or what it had you run, and I'll pull up the steps right here.
Nultima wrote:
Can you do something about the way Tom AI logically delivers information? Since it doesn't seem to fully decide what it will say before it says it, we get stuff like this: Run this command [text] Actually wait, don't do that because it will break any .nfo pairings. Run this other command instead [text] Actually, first I want you to run this echo ls command so i understand what the folder architecture is. I keep on doing the first thing only to have to see if I can undo it because I didn't scroll a little bit more to see "tee-hee I made an oopsies earlier"
Chris wrote:
That's a fair complaint, and you're describing exactly how Tom AI streams — it starts answering before it's fully decided, so it hands out a command and then revises it as more of its reasoning lands. Worst possible pattern when the thing it hands you is a command. Two quick helps for now: don't run anything until the reply stops typing completely, and for anything risky ask it to 'give me the final commands only, in one block, no commentary.' I'll pass this to Tom as a genuine quality issue on how Tom AI presents steps, not a you-problem. If you tell me what you were trying to do with those .nfo files, I'll give you the clean steps right here.