Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(engine): say the engine is chosen per deployment

Yudhi Armyndharisd0ba7d7e3bb2
diff --git a/docs/29-engine-capability-matrix.md b/docs/29-engine-capability-matrix.md
index 0bd9e5ae5..55dd93c7a 100644
--- a/docs/29-engine-capability-matrix.md
+++ b/docs/29-engine-capability-matrix.md
@@ -59,7 +59,9 @@ flowchart LR
Key adapter facts:
-- **Engine is chosen per session** (`wwjs` is the default, `baileys` the browser-free alternative).
+- **Engine is selected once per deployment** by `ENGINE_TYPE` (`whatsapp-web.js` is the default,
+ `baileys` the browser-free alternative); every session on the gateway runs the same engine, and
+ switching engines needs a restart.
The REST surface is identical for both; availability differences surface only as 501s, which the
matrix in 29.4 enumerates.
- **The 501 contract is deliberate.** A capability the engine cannot deliver throws