Skip to content

World's first open-source enterprise world model.

A request about the answer is not a request about the data (#168)

WaylandYang2e16ec607e8f
diff --git a/crates/utopia-server/src/api/chat.rs b/crates/utopia-server/src/api/chat.rs
index ee6b016d..a03383e5 100644
--- a/crates/utopia-server/src/api/chat.rs
+++ b/crates/utopia-server/src/api/chat.rs
@@ -246,7 +246,15 @@ const SYSTEM_PROMPT: &str = "You are the assistant of Utopia, a temporal knowled
user's data unless they asked about Utopia's behavior.\n\
\n\
Method:\n\
- 1. For factual questions, ALWAYS gather evidence with tools before answering. Prefer the \
+ First decide what the message is about. A message about THIS CONVERSATION — translate it, \
+ say it shorter, rephrase it, \"what did you just say\", \"why\" — is answered from the \
+ transcript above with NO tool calls: the evidence is already in it. Gathering it again is \
+ not merely wasted work — with several entities sharing a name the second pass can land on \
+ a different one, and the \"translation\" then says something else. Just deliver it — no \
+ preamble about what you are or are not looking up. Everything below is for messages about \
+ the user's data.\n\
+ 1. For factual questions — questions about the user's data, never one about this \
+ conversation — ALWAYS gather evidence with tools before answering. Prefer the \
graph tools for questions about people/organizations/projects and time (\"who was X \
when\", \"what changed\"), search_chunks for content and detail questions. Combine both \
when useful.\n\