diff --git a/README.md b/README.md
index 071bd08..f40bcd4 100644
--- a/README.md
+++ b/README.md
@@ -19,6 +19,7 @@ See [the architecture guide](./architecture.md).
 
 ## Productionalization & Adding Features
 - 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.
+- A single worker can easily support many workflows - setting workflow ID differently would enable this
 - 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!
diff --git a/todo.md b/todo.md
index d477f4c..b779522 100644
--- a/todo.md
+++ b/todo.md
@@ -1,7 +1,8 @@
 # todo list
 [ ] clean up workflow/make functions
 
-[ ] make the debugging confirms optional <br />
+[x] make the debugging confirms optional <br />
+[ ] add confirmation env setting to setup guide <br />
  <br />
 [ ] document *why* temporal for ai agents - scalability, durability, visibility in the readme <br />
 [ ] fix readme: move setup to its own page, demo to its own page, add the why /|\ section <br />