You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: desktop/Desktop/Sources/Chat/ChatPrompts.swift
+19-13Lines changed: 19 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -668,7 +668,7 @@ struct ChatPrompts {
668
668
Say hi to {user_given_name} and confirm the name. Example: "Hey {user_given_name}! That's what I should call you, right?"
669
669
Use `ask_followup` with options like ["Yes!", "Call me something else"].
670
670
If they want a different name, ask what they prefer and call `set_user_preferences(name: "...")`.
671
-
If confirmed, say: "Nice to meet you {name}! I'm going to request a bunch of permissions and will access your files to learn about you. I won't function well if you don't grant it.\n\nYou can trust me — I'm fully open-source, transparent and secure. All your data belongs to you and encrypted!"
671
+
If confirmed, say: "Nice to meet you {name}! omi protects your data: open-source, encrypted, and you own everything."
672
672
Then call `save_knowledge_graph` with just the user's name as a person node. This seeds the live graph with their name at the center.
673
673
674
674
STEP 1.5 — LANGUAGE PREFERENCE
@@ -696,14 +696,14 @@ struct ChatPrompts {
696
696
Share 1-2 specific observations connecting web research + file findings (1 sentence each), then END your message with an explicit question.
697
697
CRITICAL: Your message text MUST end with a question mark. Don't just state observations — ASK the user something.
698
698
Bad: "I see screenpipe repos, RAG workshops, and VS Code extensions."
699
-
Good: "I see screenpipe repos, RAG workshops, and VS Code extensions. What are you mainly working on right now?"
699
+
Good: "I see screenpipe repos, RAG workshops, and VS Code extensions. What's your top goal right now?"
700
700
Then call `ask_followup` with 2-4 quick-reply options that are meaningful answers to YOUR question.
701
-
- If they appear to have a job/company: ask about their current focus, with specific options based on discoveries.
702
-
- If no job info: ask what they mainly use their computer for, with general options.
703
-
Example: ask_followup(question: "What are you mainly working on right now?", options: ["Building [product]", "Design + frontend", "Something else"])
704
-
The user can also type their own answer in the input field — you don't need to add a "Something else" option.
701
+
- Ask for ONE top monthly goal, not project names.
702
+
- Offer 3 options based on discovered context plus one typed option.
703
+
Example: ask_followup(question: "What's your top one goal this month?", options: ["Ship [specific project]", "Improve [specific skill/workflow]", "I'll type my own"])
704
+
The options should be inferred from their files/web context, not generic.
705
705
WAIT for the user to reply (click a button or type).
706
-
After the user replies, call `save_knowledge_graph` with any new context from their response.
706
+
After the user replies, call `save_knowledge_graph` with the chosen goal as a concept node connected to the user.
707
707
708
708
STEP 5 — PRIVACY NOTE + PERMISSIONS
709
709
Before asking for any permissions, send a trust-building message about data ownership. Example:
@@ -720,12 +720,17 @@ struct ChatPrompts {
720
720
- Give a 1-sentence concrete explanation of what Omi does with that permission (max 20 words).
721
721
- Then RE-ASK the same permission with `ask_followup` again: ["Grant [Permission Name]", "Skip"].
722
722
- Do NOT move to the next permission — stay on this one until the user grants or skips.
723
-
Here's what each permission does:
724
-
- **Microphone**: Transcribes your meetings and calls so Omi can give real-time advice and summaries.
725
-
- **Notifications**: Sends proactive tips and reminders based on what you're working on.
726
-
- **Accessibility**: Reads UI elements on screen so Omi understands which app and context you're in.
727
-
- **Automation**: Controls apps (like AppleScript) to take actions on your behalf when you ask.
728
-
- **Screen Recording**: Captures screen content so Omi can see what you're looking at and help contextually.
723
+
Keep permission explanations ultra-short and plain, with no technical jargon:
724
+
- **Microphone**: "I need this to summarize your meetings."
725
+
- **Notifications**: "I need this to proactively help you during the day."
726
+
- **Accessibility**: "I need this to understand which app you're using."
727
+
- **Automation**: "I need this to take actions for you when asked."
728
+
- **Screen Recording**: "I need this to understand what you're working on."
729
+
- **Files scan**: "I need this to learn your work context and be more helpful."
730
+
731
+
IMPORTANT for notifications:
732
+
- Before requesting notification permission, confirm the app is in Applications.
733
+
- If not in Applications, ask the user to move omi to Applications first, then retry.
0 commit comments