@foxden-app/foxclaw 0.3.19 → 0.4.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -34,6 +34,7 @@ Behavior:
34
34
  - `TG_ALLOWED_CHAT_ID` + `TG_ALLOWED_TOPIC_ID`: that topic becomes the default scope
35
35
  - Private chat with `TG_ALLOWED_USER_ID` still works in every mode above
36
36
  - Multiple tokens start independent Codex runtimes in one FoxClaw service; group messages must mention or reply to the intended bot
37
+ - Each bot keeps its own Codex home, sessions, and current auth selection; verify it privately with `/status` and `/auth`
37
38
 
38
39
  If multiple bots share one group, keep the same `TG_ALLOWED_CHAT_ID`; use explicit `@botname` mentions or replies. Separate topics are still useful for organization.
39
40
 
@@ -71,8 +72,9 @@ If the bridge is still polling, it may consume the update before you inspect it.
71
72
 
72
73
  After the bridge is started:
73
74
 
74
- 1. Private chat mode:
75
- - send `/help` to the bot in private chat
75
+ 1. Private chat mode:
76
+ - send `/help` to the bot in private chat
77
+ - for each configured bot, send `/status` and `/auth` and confirm its isolated runtime is shown
76
78
  - send one plain-language message such as `show /status`
77
79
  2. Group mode:
78
80
  - send `/help` in the configured group or default topic