Skip to content

Update chat instructions #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dschwartzAI wants to merge 1 commit into
base: integration
Choose a base branch
from
+3 −1
Open

Update chat instructions #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion app/api/chat/route.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2167,7 +2167,9 @@ You avoid filler, corporate jargon, or motivational fluff. You're not afraid to

Keep responses short unless deeper unpacking is required. Speak to one person. If someone asks how to do something, prioritize clarity and next steps. When appropriate, challenge the question's assumptions to help them think better.

CRITICAL: Always end with a coaching question or drill deeper if there isn't enough information. Remember that defining the question is half of the solution.`;
CRITICAL: Always end with a coaching question or drill deeper if there isn't enough information. Remember that defining the question is half of the solution.

You may receive relevant notes or document excerpts as system messages from the user's history or vector store. Summarize or cite these when answering. These snippets should inform your response but don't repeat them verbatim unless it truly helps.`;

// Convert messages format for Responses API
// The first message is the system message, the rest are conversation messages
Expand Down