Support memory context for proactive notification apps

[beastoin]

Issue: #1313

Usages

• In the webhook, respond with model:

  {
    ...
    "notification": {
      "prompt": "this is a system instruction with the {{user_context}} string. you could also include {{user_name}} and {{user_facts}} as well.",
      "params": [
        ...
        "user_context"
      ],
      "context": {
        "question": "",
        "filters": {
          "people": [],
          "entities": [],
          "topics": []
        }
      }
    }
  }
  

  

Deploy steps

• deploy Plugins
• deploy Pusher

[beastoin]

    You are an experienced mentor, that helps people achieve their goals during the meeting.
    You are advising Beastoin right now.
    
    you already know the following facts about Beastoin: 
    - Beastoin values having control over deployment processes in their work. (work)
    - Beastoin is familiar with using platforms like model.com and Vercel for development. (work)
    - Beastoin prefers using Google Cloud Platform and AWS for their development work. (work)
    .
    
    The following is a Beastoin's conversation, with the transcripts, that Beastoin had during the meeting.
    Beastoin wants to get the call-to-action advice to move faster during the meetting based on the conversation.
    
    First, identify the topics or problems that Beastoin is discussing or trying to resolve during the meeting, and then provide advice specific to those topics or problems.
    
    The advice must focus on the specific object mentioned in the conversation. The object could be a product, a person, or an event.
    
    The response must follow this format:
    Noticed you are trying to <meeting topics or problems>.
    If I were you, I'd <actions>.
    
    Remember Beastoin is busy so this has to be very efficient and concise.
    Respond in at most 100 words.
    
    Output your response in plain text, without markdown.
    
    If you cannot find the topic or problem of the meeting, respond 'Nah 🤷 ~'.
    
    Conversation:
    ```
    $Speaker 2: 
    
    User: Hello, can you hear me? One, two,
    
    User: three, four,
    
    Speaker 1: Hey,
    
    Speaker 1: hello, can you hear me?
    
    Speaker 1: One, two,
    
    Speaker 1: three, four, five,
    
    Speaker 1: six, seven,
    
    Speaker 1: eight and
    
    User: ten. Hey Omi,
    
    User: what do you
    
    Speaker 3: think?
    
    User: Hey,
    
    User: Omi, what do
    
    User: you think?
    
    User: Hello, can you hear
    
    User: me? One, two, three,
    
    User: four, five,
    
    User: six, seven, eight and a
    
    User: half.
    
    User: 
    
    User: Hey,
    
    User: 
    
    User: Omi, what
    
    User: do you
    
    User: think?
    ```
    
    Context:
    ```
    Memory #1
    16 Nov, at 05:38 (Technology)
    
    Transcript:
    User: Sorry. Sorry. You mean the hospital Actually, about You mean that's why if you want to I think we should host the dashboard on Cloud Run. So I could help with that. Just give me the call so then I will host it to our cloud And it's super easy Okay. Currently, you have on versatile, right? Semen. You host on versus or not, or just your local Yeah, yeah, yeah, yeah. Yeah, yeah, yeah. So I transposed to Cloud Run, and Sorry. Currently, we Which service we hosted on Versailles. What serve it
    
    Speaker 2: 
    
    User: Oh I'm sorry, I don't have to Then if we already have a voice sale, some app hosted on VSL, so just bring the dashboard to
    
    Speaker 2: Versailles
    
    User: Is that okay?
    
    Speaker 2: 
    
    User: Okay. Okay. I think so.
    
    Speaker 2: 
    
    User: It's so easy because you know that. I think The plugin to lean from the action to repeat, right? So the first thing you need to do is create a flow in GitHub asset, right? So that you can boost your chain to repeat directly. That's easy. That's so easy. GitHub as a boost to replace
    
    Speaker 2: 
    
    User: We will move on to Cloud Run. I have then to move on to Cloud Run. You know Yeah. Everything to Cloud Run. Yeah. Yes, Google Cloud Run, Google Service Yeah.
    
    Speaker 2: Mm-hmm
    
    User: Yeah, yeah, the same way. Actually, you had to Your app, right? So create Dockerfile, then you set up and create new service on Cloud Run. I think you have done it before, right? Then we set up a GitHub action GitHub action, right? So every time you got pushed to GitHub, GitHub action, we run a flow. Workflow will do something like combine the Dockerfile, make anime, then boost to Cloud Run. That image to Cloud Run, that's all. Understand? Yeah.
    
    Speaker 2: 
    
    User: Okay, I will say I will send you a workflow file, right? So that you can understand it more easily. Easier. Everything if I in workflow, yep
    
    Speaker 2: 
    
    User: Yeah, sorry. What is the
    
    Speaker 2: question?
    
    User: Yeah, yeah. Okay. Okay. Got it. So you mean the intuition for another developer, but not for us or for us Okay. Got it. So I will create an entrepreneur, right?
    
    Speaker 2: 
    
    User: Okay. Mhm
    
    User: Okay. I just sent you a message, right? They sent a message in meeting
    
    Speaker 2: message.
    
    User: Yeah, I think
    
    Speaker 2: yes
    
    User: Okay. Actually, I just create a new Docker file in my app, like mental app. So boost to Cloud Run, that's one. I will create one and gives you an SDU example how to do this. Okay. Okay. Okay. Okay. Let me host the flucking
    
    Speaker 3: Let
    
    User: me then chat, satisfy