Verify POST /chat still accepts {message, chat_id} after agent.py refactor #6

New Issue

alvis · 2026-03-24T01:56:50Z

alvis commented

2026-03-24 01:56:50 +00:00

Problem

All bench and integration tests POST to /chat with {"message": ..., "chat_id": ...}. Confirm the legacy /chat endpoint in the refactored agent.py still handles this payload shape correctly.

Fix

Read the /chat endpoint handler and confirm payload parsing is unchanged, or update tests to use /message with {"text", "session_id", "channel"} if the endpoint was removed/changed.

## Problem All bench and integration tests POST to `/chat` with `{"message": ..., "chat_id": ...}`. Confirm the legacy `/chat` endpoint in the refactored `agent.py` still handles this payload shape correctly. ## Fix Read the `/chat` endpoint handler and confirm payload parsing is unchanged, or update tests to use `/message` with `{"text", "session_id", "channel"}` if the endpoint was removed/changed.

alvis referenced this issue

2026-03-24 02:46:01 +00:00

Remove Bifrost: replace test 4 with LiteLLM health check #14

alvis closed this issue

2026-03-24 02:46:02 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: alvis/adolf#6