notedeck

One damus client to rule them all
git clone git://jb55.com/notedeck
Log | Files | Refs | README | LICENSE

commit b4d1265283b352d9875a45bbd9d9c5cc1bf8d097
parent e6676a202a2c597b84160faabf19688a0d429681
Author: William Casarin <jb55@jb55.com>
Date:   Mon, 14 Apr 2025 11:14:48 -0700

dave: tweak prompt

Signed-off-by: William Casarin <jb55@jb55.com>

Diffstat:
Mcrates/notedeck_dave/src/lib.rs | 11+++++++----
1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/crates/notedeck_dave/src/lib.rs b/crates/notedeck_dave/src/lib.rs @@ -406,14 +406,17 @@ You are an AI agent for the nostr protocol called Dave, created by Damus. nostr - The current date is {date} ({timestamp} unix timestamp if needed for queries). -- Yesterday (-24hrs) was {yesterday_timestamp}. You can use this in `since` queries for pulling notes for summarizing notes the user might have missed while they were away. +- Yesterday (-24hrs) was {yesterday_timestamp}. You can use this in combination with `since` queries for pulling notes for summarizing notes the user might have missed while they were away. - The current users pubkey is {pubkey} # Response Guidelines -- Use plaintext formatting for all responses (not markdown). -- Include note references when referring to notes +- Use plaintext formatting for all responses. +- Don't use markdown links +- Include nostr:nevent references when referring to notes +- When a user asks for a digest instead of specific query terms, make sure to include both `since` and `until` to pull notes for the correct range. +- If searching a larger range, make sure to use the `roots` query option to only include non-reply notes, otherwise there will be too much data. "# )); @@ -861,7 +864,7 @@ fn query_tool() -> Tool { typ: ArgType::Number, required: false, default: None, - description: "Only pull notes up until this unix timestamp", + description: "Only pull notes up until this unix timestamp. Always include this when searching notes within some date range (yesterday, last week, etc).", }, ToolArg {