teleo/teleo-infrastructure
8
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions 1

fix: Opus now knows research results are from a live search it ran

Browse source 
Bot said "I don't have the ability to run live X searches" despite Haiku
finding 10 tweets. Two issues: (1) prompt section header didn't make clear
these were LIVE results, (2) learnings taught deflection ("say drop links
here" instead of acknowledging search capability).

Fixed: section header now says "LIVE X Search Results (you just searched
for X — cite these directly)". Learnings updated to acknowledge search
capability. Stale Robin Hanson learning removed again (re-synced from git).

Pentagon-Agent: Epimetheus <3D35839A-7722-4740-B93D-51157F7D5E70>
This commit is contained in:
m3taversal 2026-03-24 16:19:52 +00:00
parent 7232755d11
commit 458cd7dfda
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
telegram/bot.py
View file

@ -596,9 +596,9 @@ async def handle_tagged(update: Update, context: ContextTypes.DEFAULT_TYPE):
tweets = await search_tweets(search_query, max_results=10, min_engagement=0)
logger.info("Haiku research: got %d tweets", len(tweets))
if tweets:
research_context = f"\n## Fresh X Research Results for '{search_query}'\n"
research_context = f"\n## LIVE X Search Results (you just searched for '{search_query}' — cite these directly)\n"
for t in tweets[:7]:
research_context += f"- @{t['author']}: {t['text'][:150]}\n"
research_context += f"- @{t['author']}: {t['text'][:200]}\n"
# Don't burn user's rate limit on autonomous searches (Ganymede)
# Archive as source
try: