From 238902a51d45659af6d87d1138394f21a3018db2 Mon Sep 17 00:00:00 2001 From: Steve Androulakis Date: Fri, 31 Jan 2025 08:58:04 -0800 Subject: [PATCH] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 0fdb9d0..7bf42fa 100644 --- a/README.md +++ b/README.md @@ -135,4 +135,5 @@ Access the UI at `http://localhost:5173` - Currently hardcoded to the Temporal dev server at localhost:7233. Need to support options incl Temporal Cloud. - In a prod setting, I would need to ensure that payload data is stored separately (e.g. in S3 or a noSQL db - the claim-check pattern), or otherwise 'garbage collected'. Without these techniques, long conversations will fill up the workflow's conversation history, and start to breach Temporal event history payload limits. - Continue-as-new shouldn't be a big consideration for this use case (as it would take many conversational turns to trigger). Regardless, I should ensure that it's able to carry the agent state over to the new workflow execution. +- Perhaps the UI should show when the LLM response is being retried (i.e. activity retry attempt because the LLM provided bad output) - Tests would be nice!