0.0.44 Add sender_id field to ProtocolMessage

• Added an additional field sender_id in ProtocolMessage. This is intended to help bot creators differentiate between who sent a particular message, which is useful in a multi-bot chat.

0.0.43 add should_insert_attachment_messages

Release Notes:

• (deprecated) concat_attachments_to_message: this function added file content from user attachments directly into the text of the last user message. This method of adding attachments is suboptimal for LLMs and is being deprecated. Use the newly added should_insert_attachment_messages instead. This function will be removed in a future release.
• (added) should_insert_attachment_messages: this function adds file contents from user attachments into their own individual messages and inserts them right before the last user message. This provides better LLM performance than concat_attachments_to_message. Note that this breaks the user-bot message alternation. If the LLM you are using requires that, try using make_prompt_author_role_alternated.
• (added) make_prompt_author_role_alternated: this function takes in a conversation, and concats consecutive messages from the same role. This is useful for LLM providers that require role alternation.

Breaking Changes:

This release makes should_insert_attachment_messages=True by default, and disables the deprecated concat_attachments_to_message by default.

0.0.42

What's Changed

• Adding attachment URL to post_message_attachment response.

Full Changelog: 0.0.41...0.0.42

0.0.41

What's Changed

• Adding attachment URL to post_message_attachment response. by @YushengAuggie in #96

Full Changelog: 0.0.39...0.0.41

0.0.40

What's Changed

• Adding attachment URL to post_message_attachment response. by @YushengAuggie in #96

New Contributors

• @YushengAuggie made their first contribution in #96

Full Changelog: 0.0.39...0.0.40

0.0.39

• Fix regression where bots that do not override get_response_with_context() would emit a spurious "hello" response.
• Allow coroutines as callables for tool calls. Thanks @canwushuang for the contribution.

0.0.38 add multibot setting

There are two changes in this release:

• enable_multi_bot_chat_prompting is a new setting (Default False), which if enabled, will have Poe combine previous chat history into a single message with special prompting so that the current bot will have sufficient context about a multi bot chat.
• the timeout for bot messages has been increased from 120s -> 600s.

0.0.37 Add attachment parsing functionality

Add 3 bot-level settings:

1. expand_text_attachments: whether to send parsed content from text attachments with the attachment object in ProtocolMessage. Defaults to True
2. enable_image_comprehension: whether to send parsed image description from image attachments with the attachment object in ProtocolMessage. Defaults to False. Will limit the # of image attachments per message to one.
3. enforce_author_role_alternation: whether Poe should modify the messages to follow strict user/bot alternation before sending to the bot. Defaults to False.

Added concat_attachment_content_to_message_body helper function that is called before get_response, which takes parsed content from attachments and concatenates it to the message content. It is enabled by default, but can be disabled by passing in concat_attachments_to_message=False when creating the PoeBot class.

0.0.36: Fix bug with function calling

Addresses the issue where you are forced to use function calling for every message if you pass in function info. After this fix, you should be allowed to send regular, non-function using messages without any failure.

0.0.35

• Allow initializing a fastapi-poe app using an existing FastAPI instance