hermes - 💡(How to fix) Fix Title: HTTP 400 on Fireworks custom endpoint — first turn only, fallback succeeds [1 comments, 1 participants]

TL;DR

The issue may be caused by Hermes adding specific fields to the request body on session initialization that are not present on fallback retries, and verifying these differences is the first step to resolving the problem.

Guidance

• Investigate the request body differences between the initial message and fallback retries, focusing on fields like stream_options, user, and non-standard headers.
• Check the Hermes documentation to confirm if stream_options is sent on turn 1 and if a user field with session ID is injected.
• Compare the system prompt format with and without SOUL.md injection to see if it affects the endpoint's acceptance.
• Test the custom endpoint with the exact same request body and headers as the fallback retries to isolate the issue.

Example

No code snippet is provided as the issue lacks specific implementation details.

Notes

The root cause is uncertain without further information from Hermes or the custom endpoint. The Fireworks support ticket may provide additional insights.

Recommendation

Apply workaround: Modify the request body on session initialization to match the fallback retries, potentially by removing or modifying the suspected fields, to test if this resolves the HTTP 400 issue.