oct 17, try omi chat (agentic) and tell

[beastoin]

hi, thinh's here. I need your help to improve the omi chat. please try it (its ready for all, just use your current omi app) and let me know:

• in which cases did the chat fail (not work as expected / could be better) for you?
• what should it be?

notice that uid should be kept private (I might dm you to ask about it, don't share it publicly) and, don't panic about failure cases :).

---
new updates on omi chat: #3238

show case >>> https://x.com/_thinx/status/1979051501579293034

[aaravgarg]

Discussed a yacht party partnership few mins ago and instead of referencing that it reference some bs

[beastoin]

what is the answer should it be man? e.g., which partner? e.g., share the convos as well if you want to mention a convo.

--- i just texted to omi again.

{
  "id": "2b226858-b038-4b36-9c96-acb0ed753431",
  "text": "You recently discussed \"yacht party\" partnerships, but the context was all business—not an actual party. The conversations focused on expanding your sales and distribution (especially in India and Asia), how to structure affiliate/reseller/partner models, shipping logistics, and how to handle privacy or security for sensitive meetings—think B2B rather than a social event.\n\nRegarding whether those partnerships make sense:\nYes, exploring local partners/distributors could make a lot of sense for your goals. Your team highlighted the challenges of not having local shipping/fulfillment in places where you already have demand, and these partnership models (affiliate, reseller, shipping partner) are intended to fill exactly that gap. The discussions also covered essential concerns like commission structure, privacy, scalability, and clarity between device sales vs. subscriptions—all relevant for a healthy business partnership, especially with tech/security-conscious partners.\n\nSo, if your aim is to boost reach and efficiency in new regions and you have strong privacy/security/commission agreements in place, these kinds of partnerships seem like a smart way forward for your business. If you meant something different by \"yacht party partnership,\" though, let me know!",
  "created_at": "2025-10-19T03:51:13.237643Z",
  "sender": "ai",
  "app_id": null,
  "plugin_id": null,
  "from_external_integration": false,
  "type": "text",
  "memories_id": [
    "3e85ce60-c6ec-4719-866f-a119cc09b3eb",
    "ee028f11-7ba3-4f64-9e03-71a24136d429"
  ],
  "memories": [
    {
      "id": "3e85ce60-c6ec-4719-866f-a119cc09b3eb",
      "structured": {
        "title": "Team Schedules Follow-Up Sales Meeting",
        "emoji": "📈"
      },
      "created_at": "2025-10-14T05:06:42.184534Z"
    },
    {
      "id": "ee028f11-7ba3-4f64-9e03-71a24136d429",
      "structured": {
        "title": "Business Partnership Models and Security Discussed",
        "emoji": "🤝"
      },
      "created_at": "2025-10-15T05:06:23.195235Z"
    }
  ],
  "reported": false,
  "report_reason": null,
  "files_id": [],
  "files": [],
  "chat_session_id": "3b1412e1-f25b-439d-ab66-06b0dd2b6f6b",
  "data_protection_level": null,
  "ask_for_nps": false
}

[beastoin]

oh i see, >>> tracking here #3259

[beastoin]

aired, try again please, sir.

[aaravgarg]

asked at 645 PM

convos of that time it failed to fetch:

[beastoin]

i see. the system was messed up by the recent commits. will fix.>>> #3254

[beastoin]

PR >>> #3255

[beastoin]

aired, pls try it and lmk - all the time-related questions >>>

[aaravgarg]

failed to fetch details of a convo of same day literally

convo:

[beastoin]

oh i see >>> tracking here #3259

[beastoin]

aired, try again please, sir.

[aaravgarg]

it said it will cancel but didnt mark task as done:

even after refresh:

[beastoin]

ops, i guess the current tools do not have the capacity to cancel the action items. haha.

[aaravgarg]

Found another daily life use case example of bad retrieval within past few hours discussed context

[beastoin]

yeah, please try again, then lmk if you find it still messed up. don't forget to do a simple trick - clear the current chat. btw, lmk.

[aaravgarg]

time is still having issues:

i asked what i discussed 2 hours ago when it was 1 AM but it referred to a convo few mins ago instead of 2 hours ago

@beastoin

[aaravgarg]

I asked at 1 AM so smng like this should be referenced:

[beastoin]

yeah it's the citation. btw how about the response message? is it accurate?

logs:

• found 3 convos.

agentic_context_dependent_conversation node
The default Firebase app does not exist. Make sure to initialize the SDK by calling initialize_app().
🌍 _get_agentic_qa_prompt - User timezone: America/Los_Angeles, Current time: 2025-10-19 01:12:05
🔧 Tool started: get_conversations_tool
🛡️ Safety Guard: Tool call 1/10 - get_conversations_tool
🔧 get_conversations_tool called with params:
   start_date: 2025-10-18T23:12:05.962656-07:00
   end_date: 2025-10-19T01:12:05.962656-07:00
   limit: 3
   offset: 0
   include_discarded: False
   statuses: processing,completed
   max_transcript_segments: 20
   include_transcript: True
   include_timestamps: False
✅ get_conversations_tool - uid: GPW***
📊 max_transcript_segments capped at: 20
📅 Parsed start_date '2025-10-18T23:12:05.962656-07:00' as 2025-10-18 23:12:05 UTC-07:00
📅 Parsed end_date '2025-10-19T01:12:05.962656-07:00' as 2025-10-19 01:12:05 UTC-07:00
📊 get_conversations_tool - found 3 conversations
🔍 get_conversations_tool - Found 0 unique person IDs
🔍 get_conversations_tool - Converted 3 conversation objects
📚 get_conversations_tool - Added 3 conversations to collection (total: 3)
🔍 get_conversations_tool - Generated result string, length: 13489
✅ Tool ended: get_conversations_tool
🛡️ Safety Guard: Context size: 3453/500000 tokens (+3453)
🛡️ Safety Guard final stats: {'tool_calls': 1, 'max_tool_calls': 10, 'estimated_tokens': 3453, 'max_context_tokens': 500000, 'elapsed_seconds': 7.02126407623291, 'tools_used': ['get_conversations_tool']}
📚 Collected 3 conversations for citation

[aaravgarg]

No, the response message also talked about the citation reference only.

[beastoin]

i see, tracking here >>> #3257

[beastoin]

aired, pls try again.

[krushnarout]

It was supposed to update the todo’s deadline from tomorrow to today, but it created a duplicate instead.