🧵 for @Cole's demo today.

Here is the screenshot of that interface. The knowledge of WebP is informed by the “Context” seen above the user’s message. That context is a series of visited webpages. When we visit a webpage, we store a scrape of that webpage in our database, which is being used to answer the question.

I see, so you're basically building "what I would know if I had perfect comprehension and memory of everything I ever read" 😂 ❤️

Yeah, that, and I like to call the long-term goal “the cure for context switching,” which includes a few more proactive features.

Yeah, that "cure for context switching" framing is especially interesting as a point of comparison to Microsoft's Recall, Rewind.ai, and the old concept of LifeStreams, which seem more about aiding memory. Would love to hear more about what you have in mind here.

Yeah, I haven’t found memory to be nearly as painful as my experience of “context switching.” For example, communicating event announcements or invoicing clients (each of which happens every few weeks) is incredibly painful for me because of the activation energy required to start the task and resume the context that I was in several weeks ago. So, I want to basically ask “invoice”, get a suggestion for “prepare a new invoice” and get a list of bookmarks and summaries of the last invoice activity I had. Separately, I’d like to say “meet” (or to simply visit calendar.google.com) and have it see an upcoming meeting and suggest “prepare for meeting”, and so on.