docs: mirror WORKER_ID tip to versioned_docs v0.6 (from #1648 )

Folding in xmh1011's strict-improvement hunk from #1648: the versioned snapshot for v0.6 should carry the same production tip as the live doc. Same prose, same `:::tip` block. Includes the auto-regenerated skills/ reference.
docs: add HINDSIGHT_API_WORKER_ID tip to API quickstart
2026-05-19 14:53:35 -04:00 · 2026-05-13 12:59:01 -04:00
3 changed files with 17 additions and 0 deletions
@@ -52,6 +52,12 @@ docker run --rm -it --pull always -p 8888:8888 -p 9999:9999 \
 - **API**: http://localhost:8888
 - **Control Plane** (Web UI): http://localhost:9999

+:::tip Set a stable `HINDSIGHT_API_WORKER_ID` in production
+The worker uses the container hostname as its identity, which Docker sets to the container ID by default. That value changes on every restart, so any task that was being processed when the container went down stays parked under the old ID with no way for the new container to recognize it as its own.
+
+Set `HINDSIGHT_API_WORKER_ID` to a stable value (e.g., `-e HINDSIGHT_API_WORKER_ID=hindsight-prod`) so the worker keeps the same identity across restarts. This is recommended even for single-container deployments. For diagnosis and recovery commands, see [Admin CLI - Recovering stuck operations](/developer/admin-cli#recovering-stuck-or-zombie-operations).
+:::
+
 </TabItem>
 </Tabs>

@@ -52,6 +52,12 @@ docker run --rm -it --pull always -p 8888:8888 -p 9999:9999 \
 - **API**: http://localhost:8888
 - **Control Plane** (Web UI): http://localhost:9999

+:::tip Set a stable `HINDSIGHT_API_WORKER_ID` in production
+The worker uses the container hostname as its identity, which Docker sets to the container ID by default. That value changes on every restart, so any task that was being processed when the container went down stays parked under the old ID with no way for the new container to recognize it as its own.
+
+Set `HINDSIGHT_API_WORKER_ID` to a stable value (e.g., `-e HINDSIGHT_API_WORKER_ID=hindsight-prod`) so the worker keeps the same identity across restarts. This is recommended even for single-container deployments. For diagnosis and recovery commands, see [Admin CLI - Recovering stuck operations](/developer/admin-cli#recovering-stuck-or-zombie-operations).
+:::
+
 </TabItem>
 </Tabs>

@@ -38,6 +38,11 @@ docker run --rm -it --pull always -p 8888:8888 -p 9999:9999 \
 - **API**: http://localhost:8888
 - **Control Plane** (Web UI): http://localhost:9999

+> **💡 Set a stable `HINDSIGHT_API_WORKER_ID` in production**
+> 
+The worker uses the container hostname as its identity, which Docker sets to the container ID by default. That value changes on every restart, so any task that was being processed when the container went down stays parked under the old ID with no way for the new container to recognize it as its own.
+
+Set `HINDSIGHT_API_WORKER_ID` to a stable value (e.g., `-e HINDSIGHT_API_WORKER_ID=hindsight-prod`) so the worker keeps the same identity across restarts. This is recommended even for single-container deployments. For diagnosis and recovery commands, see [Admin CLI - Recovering stuck operations](../admin-cli.md#recovering-stuck-or-zombie-operations).
 > **💡 LLM Provider**
 > 
 Hindsight requires an LLM with structured output support. Recommended: **Groq** with `gpt-oss-20b` for fast, cost-effective inference.