Wickedness/nas_connection
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Split Telegram assistant and work chats

Browse Source
This commit is contained in:
y2keui
2026-06-10 11:40:37 +09:00
parent f92fc8a718
commit 5e3a439cd8
4 changed files with 53 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@@ -35,14 +35,18 @@ only keeps connection-management commands.
/unarchive_session <thread_id>
```
`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.
`ALLOW_PLAIN_TEXT=true` forwards regular Telegram messages to Codex. Set
`WORK_TELEGRAM_CHAT_IDS` to one or more group chat ids to split the bot into
profiles: listed chats run as `work` chats with full-access repository turns,
and every other chat runs as a personal `assistant` chat for schedules,
reminders, saved records, briefings, and lightweight Gitea/status lookup. In
Telegram groups, disable bot privacy with BotFather if you want the bot to
receive normal non-command messages.
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.
On Synology/NAS Docker deployments, keep `CODEX_WRITE_SANDBOX` set to
`danger-full-access`. The stricter `workspace-write` sandbox may fail with
bubblewrap namespace errors inside the container. Personal assistant chats use
`CODEX_ASSISTANT_SANDBOX`, which defaults to `read-only`.
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