Run Telegram turns with full access by default

README.md

@@ -35,14 +35,14 @@ only keeps connection-management commands.
 /unarchive_session <thread_id>
 ```
 
-`ALLOW_PLAIN_TEXT=true` makes regular Telegram messages behave like `/ask`.
-Use `/work <prompt>` for write-capable tasks such as editing files, committing,
-pushing, or opening pull requests. Plain text and `/ask` stay read-oriented by
-default.
+`ALLOW_PLAIN_TEXT=true` makes regular Telegram messages run as full-access Codex
+turns. Use `/work <prompt>` when you want to be explicit, but regular messages
+and `/ask` use the same write-capable sandbox by default.
 
-On Synology/NAS Docker deployments, keep `CODEX_WRITE_SANDBOX=danger-full-access`
-for `/work`. The stricter `workspace-write` sandbox may fail with bubblewrap
-namespace errors inside the container.
+On Synology/NAS Docker deployments, keep `CODEX_READONLY_SANDBOX` and
+`CODEX_WRITE_SANDBOX` set to `danger-full-access`. The stricter
+`workspace-write` sandbox may fail with bubblewrap namespace errors inside the
+container.
 
 If no `/repo` is set, the bridge tries to auto-select a workspace folder when a
 Telegram prompt mentions an exact folder name such as `card_game` or
@@ -147,6 +147,7 @@ Example Telegram workflow:
 
 - Codex state and auth live under the mounted `codex-home` volume.
 - The app-server listens on `ws://127.0.0.1:4500` inside the container.
-- Normal chat messages use a persistent app-server WebSocket per Telegram chat.
+- Normal chat messages use full-access Codex turns with a persistent app-server
+  WebSocket per Telegram chat when available.
 - Idle persistent WebSockets are closed after `PERSISTENT_WS_IDLE_SECONDS`.
 - Session commands call app-server thread APIs.