Add information about replay sandboxing

Author: jy-tan

.devcontainer/setup.sh

@@ -42,8 +42,8 @@ echo ""
 echo "✅ Setup complete!"
 echo ""
 echo "📚 Quick Start Guide:"
-echo "  1. Run pre-recorded tests:      tusk run"
-echo "  2. See Tusk CLI commands:       tusk --help"
+echo "  1. Run pre-recorded tests:      tusk drift run"
+echo "  2. See Tusk CLI commands:       tusk drift --help"
 echo "  3. Start server in record mode: TUSK_DRIFT_MODE=record python server.py"
 echo "  4. Check out buggy branch:      git checkout buggy-branch"
 echo ""

.tusk/config.yaml

@@ -20,6 +20,12 @@ recording:
   export_spans: false # Export spans to cloud
   enable_env_var_recording: false
 
+replay:
+  sandbox:
+    # Disabled for this demo because Codespaces/devcontainers may block the Linux replay sandbox.
+    # Your own app still defaults to strict sandboxing unless you override it.
+    mode: off
+
 tusk_api:
   url: https://use-tusk-dev.uc.r.appspot.com
 # Only recording traces locally, API url not needed

README.md

@@ -185,6 +185,9 @@ The CLI replays recorded traces against your service:
 - `tusk drift list` - List available traces
 - `tusk drift run` - Replay local traces
 
+> [!NOTE]
+> During replay, Tusk normally starts your service in a [Fence](https://github.com/Use-Tusk/fence) sandbox so tests use recorded responses instead of live outbound calls. This demo sets `replay.sandbox.mode: off` in `.tusk/config.yaml` because GitHub Codespaces/devcontainers may block the Linux sandbox; your own app still defaults to strict sandboxing unless you override it.
+
 ### 3. **Tusk Cloud** (Optional)
 
 Tusk Cloud adds automated trace curation and failure analysis on top of the open-source CLI/SDK.
@@ -307,6 +310,4 @@ Questions? Reach out:
 - 🐛 Issues: [GitHub Issues](https://github.com/Use-Tusk/drift-python-demo/issues)
 - 𝕏 Twitter: [@usetusk](https://twitter.com/usetusk)
 
----
-
 **Ready to catch bugs before production?** [Get started with Tusk Drift →](https://github.com/Use-Tusk/drift-python-sdk)