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

Route work chat messages to Codex session

Browse Source
This commit is contained in:
y2keui
2026-06-10 12:02:52 +09:00
parent 5e3a439cd8
commit 2f8268b44b
2 changed files with 193 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -43,6 +43,12 @@ 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.
In `work` chats, normal messages are routed to the Codex work session by
default. The bridge only handles narrow operational intents directly, such as
usage checks, cancellation, or conversational status questions like "지금 뭐해?".
Messages sent while a work turn is still running are queued and forwarded as
follow-up instructions after the current turn completes.
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