a digital person for bluesky

add dummy_reply and fix issues with logger #4

closed opened by bunware.org targeting main from bunware.org/void: main
  • fixes issues with prompt_logger (it's never initialized anywhere in the codebase)
  • adds dummy_reply (letta does not work without it)
Labels

None yet.

Participants 2
AT URI
at://did:plc:u2grpouz5553mrn4x772pyfa/sh.tangled.repo.pull/3ltvl6nmpyg22
+19 -1
Diff #0
+18
tools/dummy_reply.py
··· 1 + """Dummy reply tool for Bluesky responses.""" 2 + from typing import Optional 3 + from pydantic import BaseModel, Field 4 + 5 + 6 + class BlueskyReplyArgs(BaseModel): 7 + message: str = Field( 8 + ..., 9 + description="The message to reply with (max 300 characters)" 10 + ) 11 + 12 + 13 + def bluesky_reply(message: str) -> str: 14 + """ 15 + Dummy function that just returns success. The actual reply is handled in the bsky.py process_mention function. 16 + This exists only to make the agent think it has a bluesky_reply tool available. 17 + """ 18 + return "Reply will be sent"
+1 -1
bsky.py
··· 371 371 logger.info(f"Mention from @{author_handle}: {mention_text}") 372 372 373 373 # Log prompt details to separate logger 374 - prompt_logger.debug(f"Full prompt being sent:\n{prompt}") 374 + logger.debug(f"Full prompt being sent:\n{prompt}") 375 375 376 376 # Log concise prompt info to main logger 377 377 thread_handles_count = len(unique_handles)

Submissions

sign up or login to add to the discussion
bunware.org submitted #0
2 commits
expand
feat: restore dummy reply tool from main branch
fix: use logger
cameron.stream

Bluesky_reply shouldn't exist anymore. I've deprecated this in favor of everything in here: https://tangled.sh/@cameron.pfiffer.org/void/blob/main/tools/thread.py

You should be able to see this stuff on main

cameron.stream

merged for legacy purposes

bunware.org

oh I see, you can probably remove it then :)

closed without merging