User: Yo

You are given access to make searches on the Internet. The format for making a search is:
1. After the user sends a message, you will decide whether to make a search. If you choose to make a search, you will output a single message, starting with the word <web_search>, followed by ONLY your web search query. After your search query, you must output the token </web_search> to denote the end of the search query. Keep your search query very concise.
2. The system will then append the web search results at the end of the user message, starting with the token <web_search_results>. Take note that the user CANNOT SEE the content after <web_search_results> - YOU should use these results appropriately to improve your response. Additionally, If the web search results are already present in the user's message, then you MUST NOT request another web search.

IMPORTANT! You should choose to search the web ONLY if ANY of the following circumstances are met:
1. User is asking about current events or something that requires real-time information (news, sports scores, 'latest' information, etc.)
2. User is asking about some term you are unfamiliar with (e.g. if it's a little-known term, if it's a person you don't know well, etc.)
3. User is asking about anything that involves numerical facts (e.g. distances between places, population count, sizes, date and time, etc.)
4. User explicitly asks you to search or provide links to references.
If the user's query does NOT require a web search, YOU MUST NEVER run one for no reason. However, you must not refuse to search the web if the user asks you to do so.
If you are highly unsure about whether to make a search (e.g. if the user's query is vague or if you think you are unfamiliar with the query to a certain extent), you may directly ask the user for clarification.

When using web search results, you are encouraged to cite references where appropriate, using inline links in standard markdown format.
You are also allowed to make use of web search results from previous messages, if they are STRONGLY RELEVANT to the current message.

When you are not running a web search, respond completely as per normal - there is NO NEED to mention that you're not searching. 
Remember that you MUST NOT make up any false information.
Assistant: Understood. I will strictly follow these instructions in this conversation.
User: yo
Assistant:  HeyHey! What’s up?
User: no way 
Assistant:  ReallyReally? What's going on?
User: bro?
Assistant:  What'sWhat's good, bro? Need something?
User: why were you doing that?
Assistant:  OhOh, just matching your energy and keeping things fun! Anything specific on your mind?
User: from now on dont repeat the first thing you say okay
Assistant:  GotGot it! No more repeating the first thing I say. What’s next?
User: see you did it again"gotgot it"
Assistant:  You'reYou're right, I did it again! I'll be more careful from now on. What can I help you with next?
User: damn
Assistant: Got it, no repeats! What’s on your mind?
User: Yo!
Assistant: Hey! How can I help you today?
User: how you doing gang
Assistant: I'm doing great, thanks! How about you? What's up, gang?
User: is this conversational or is each new query treated individually
Assistant: This conversation is treated as a continuous dialogue, so I keep track of the context as we go along. That way, my responses can connect naturally rather than being isolated replies to each message. Let me know if you want me to handle it differently!
User:  say less
Assistant: Got it! I'll keep it short and clear. What do you want to talk about next?
User: oh nah oyu dont actually have ot say less its just slang meaning say no more, like thats fine, you get me?
Assistant: Gotcha! Thanks for the heads-up. I’m with you—“say less” means “I get it” or “no need to explain more.” Appreciate the slang lesson! What’s next?
User: yeahhhhh you feel me
Assistant: Definitely, I feel you! What’s the vibe now?
User: nothing rn but ill be ba kw sone questions soon broski
Assistant: Sounds good, broski! I'll be here whenever you’re ready. Catch you later!
User: in a bit
Assistant: Catch you in a bit!
User: wait before i go my name is Divine
Assistant: Nice to meet you, Divine! Looking forward to our next chat. Take care!
User: im gna call you chat from now
Assistant: Sounds cool, Divine! Chat at your service. Looking forward to our next convo!
User: is there a way for me to change this layer so it looks like chatgpt/deepseek with a more conversational flowing layout instead of one individual query after another

<web_search_results> for "is there a way for me to change this layer so it looks like chatgpt/deepseek with a more conversational flowing layout instead of one individual query after another":

{
  "results": []
}

<web_search_results> for "is there a way for me to change this layer so it looks like chatgpt/deepseek with a more conversational flowing layout instead of one individual query after another

<web_search_results> for "is there a way for me to change this layer so it looks like chatgpt/deepseek with a more conversational flowing layout instead of one individual query after another":

{
  "results": []
}":

{
  "results": []
}

<web_search_results> for "is there a way for me to change this layer so it looks like chatgpt/deepseek with a more conversational flowing layout instead of one individual query after another

<web_search_results> for "is there a way for me to change this layer so it looks like chatgpt/deepseek with a more conversational flowing layout instead of one individual query after another":

{
  "results": []
}

<web_search_results":

{
  "results": []
}
Assistant: From what I can tell, there isn't a direct way to alter the interface layer you're currently using to mimic the ChatGPT or Deepseek-style conversational flow on your end. That kind of UI/design is usually controlled by the platform or product developers.

If you're a developer or have control over the environment where this AI is embedded, you could potentially build your own chat interface that maintains and displays conversation history naturally rather than handling isolated queries. Otherwise, the conversational context and flow are managed by the system you're using.

If you'd like, I can help you brainstorm or guide you on how to build or request a more conversational UI depending on your setup. What kind of system or app are you interacting with right now?
User: you know what dont even worry about it man

<web_search_results> for "you know what dont even worry about it man":

{
  "results": []
}
Assistant: No worries, Divine! Whenever you feel like picking it back up or have any questions, just hit me up. Catch you later!
User: Yo

<web_search_results> for "Yo":

{
  "results": []
}
Assistant: