Skip to content

Required approach for the backend? #145

Open
@ca9

Description

@ca9

Hi,

is it in the documentation roadmap to at some point provide the basic backend/endpoints needed to support this UI?

- POST /agent/threads - Create new threads
- GET /agent/info - Health check
- POST /agent/threads/{thread_id}/history - Get thread history
- POST /agent/threads/{thread_id}/runs/stream - 
- Standard LangServe endpoints (/agent/invoke, /agent/stream, etc.)

Between streaming support from langserve and checkpointing from langgraph - which somehow arent compatible OTB with each other, I found working with this frontend without additional guidance slightly messy.

  • Either we wrap langserve to create checkpoint, which as a "wrapper" on a fastapi wrapper didnt seem great?
  • Alternatively we can give langserve a miss and self-implement streaming on langgraph, hand-crafting each response/query object. Doable, but not great either.

Whats the recommended self-hosted/deployed backend for this? I feel like there's a small missing layer here, but I might be wrong.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions