suzumearch 0.2.29 → 0.2.30
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.
- package/README.md +0 -73
- package/cli.mjs +1771 -1794
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -101,79 +101,6 @@ Session-only scheduled tasks stop when SuzumeArch exits. Durable tasks are store
|
|
|
101
101
|
in `.suzume/scheduled_tasks.json` when the model explicitly creates them that
|
|
102
102
|
way.
|
|
103
103
|
|
|
104
|
-
## Discord Bot Bridge
|
|
105
|
-
|
|
106
|
-
Configure the bot:
|
|
107
|
-
|
|
108
|
-
```bash
|
|
109
|
-
export DISCORD_BOT_TOKEN="..."
|
|
110
|
-
export DISCORD_CHANNEL_IDS="123456789012345678,234567890123456789"
|
|
111
|
-
# Optional allowlists:
|
|
112
|
-
export DISCORD_GUILD_IDS="345678901234567890"
|
|
113
|
-
export DISCORD_USER_IDS="456789012345678901,567890123456789012"
|
|
114
|
-
# Owner IDs allowed to perform Discord write/delete/moderation actions:
|
|
115
|
-
export DISCORD_OWNER_IDS="678901234567890123"
|
|
116
|
-
# Optional privileged intent for reply text that does not mention the bot:
|
|
117
|
-
export DISCORD_MESSAGE_CONTENT_INTENT="false"
|
|
118
|
-
```
|
|
119
|
-
|
|
120
|
-
```powershell
|
|
121
|
-
$env:DISCORD_BOT_TOKEN="..."
|
|
122
|
-
$env:DISCORD_CHANNEL_IDS="123456789012345678,234567890123456789"
|
|
123
|
-
# Optional allowlists:
|
|
124
|
-
$env:DISCORD_GUILD_IDS="345678901234567890"
|
|
125
|
-
$env:DISCORD_USER_IDS="456789012345678901,567890123456789012"
|
|
126
|
-
# Owner IDs allowed to perform Discord write/delete/moderation actions:
|
|
127
|
-
$env:DISCORD_OWNER_IDS="678901234567890123"
|
|
128
|
-
# Optional privileged intent for reply text that does not mention the bot:
|
|
129
|
-
$env:DISCORD_MESSAGE_CONTENT_INTENT="false"
|
|
130
|
-
```
|
|
131
|
-
|
|
132
|
-
Then run `/discord on` inside SuzumeArch. `/discord` opens the configuration
|
|
133
|
-
menu; `/discord status` prints the active settings. `/discord on` persists
|
|
134
|
-
env-backed Discord token and ID settings into SuzumeArch config so they survive
|
|
135
|
-
future launches. You can also run `/discord save` after setting env vars to save
|
|
136
|
-
the current effective Discord configuration permanently.
|
|
137
|
-
|
|
138
|
-
You can also configure lists from inside the CLI:
|
|
139
|
-
|
|
140
|
-
```bash
|
|
141
|
-
/discord channel 123 234
|
|
142
|
-
/discord channel add 345
|
|
143
|
-
/discord guild 456 567
|
|
144
|
-
/discord user 678 789
|
|
145
|
-
/discord owner 890
|
|
146
|
-
/discord message-content on
|
|
147
|
-
/discord save
|
|
148
|
-
```
|
|
149
|
-
|
|
150
|
-
Single-value env vars and commands still work: `DISCORD_CHANNEL_ID`,
|
|
151
|
-
`DISCORD_GUILD_ID`, `DISCORD_USER_ID`, `DISCORD_OWNER_ID`,
|
|
152
|
-
`/discord channel <id>`, and `/discord guild <id>`.
|
|
153
|
-
|
|
154
|
-
The bot only queues messages when it is mentioned or replied to. Allowed
|
|
155
|
-
non-owner Discord users can ask for read-only Discord information such as roles,
|
|
156
|
-
channels, members, bans, and guild details. Owner IDs configured with
|
|
157
|
-
`DISCORD_OWNER_IDS` or `/discord owner` can also create/update/delete roles and
|
|
158
|
-
channels, kick/ban/unban members, assign roles, move or disconnect members from
|
|
159
|
-
voice, server mute/deafen, set nicknames, time out members, and request the bot
|
|
160
|
-
to join or leave voice channels. The bot needs the corresponding Discord
|
|
161
|
-
application permissions in the server for these actions to succeed.
|
|
162
|
-
|
|
163
|
-
Message Content is a privileged Discord Gateway intent. Keep it off unless you
|
|
164
|
-
need replies without an explicit bot mention to include readable text, and enable
|
|
165
|
-
the same intent in the Discord Developer Portal before running
|
|
166
|
-
`/discord message-content on`; otherwise Discord can reject the gateway
|
|
167
|
-
connection with a disallowed-intent close code. If startup stalls while Message
|
|
168
|
-
Content is requested, Suzume retries without that privileged intent so
|
|
169
|
-
mention-based prompts can still work.
|
|
170
|
-
|
|
171
|
-
Warning: Discord mode automatically switches the session to
|
|
172
|
-
`bypassPermissions` by default. Anyone who can post in the configured Discord
|
|
173
|
-
channels and passes the optional guild/user filters can trigger tools and shell
|
|
174
|
-
commands without per-action prompts. Use private channels, configure owner IDs
|
|
175
|
-
for administration, and use a dedicated bot token.
|
|
176
|
-
|
|
177
104
|
## Web Search
|
|
178
105
|
|
|
179
106
|
SuzumeArch can use a self-hosted SearXNG instance for external models:
|