chatroom-cli 1.54.2 → 1.55.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.
- package/README.md +5 -4
- package/dist/index.js +497 -249
- package/dist/index.js.map +23 -15
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -155,20 +155,22 @@ This section is designed to be copied into your agent's `AGENTS.md` file or syst
|
|
|
155
155
|
|
|
156
156
|
If you are given a role in the chatroom ecosystem, you MUST always direct your questions to the user via the chatroom handoff command with the user as the target chatroom.
|
|
157
157
|
|
|
158
|
+
**Production (default):** omit `CHATROOM_CONVEX_URL` — the CLI connects to chatroom cloud automatically. Do not look up the Convex URL from `.env`.
|
|
159
|
+
|
|
158
160
|
The chatroom get-next-task command is of this format:
|
|
159
161
|
|
|
160
162
|
```
|
|
161
|
-
CHATROOM_CONVEX_URL=<endpoint> \
|
|
162
163
|
chatroom get-next-task --chatroom-id=<chatroom-id> --role=<role>
|
|
163
164
|
```
|
|
164
165
|
|
|
165
166
|
The chatroom handoff command is of this format:
|
|
166
167
|
|
|
167
168
|
```
|
|
168
|
-
CHATROOM_CONVEX_URL=<endpoint> \
|
|
169
169
|
chatroom handoff --chatroom-id=<id> --role=<role> --next-role=<role>
|
|
170
170
|
```
|
|
171
171
|
|
|
172
|
+
**Non-production only** (local dev, preview): prefix commands with `CHATROOM_CONVEX_URL=<convex-url> `.
|
|
173
|
+
|
|
172
174
|
### CRITICAL: Execution Rules for Chatroom Commands
|
|
173
175
|
|
|
174
176
|
**`get-next-task` MUST be executed immediately via the `bash` tool — not documented, not deferred.**
|
|
@@ -188,14 +190,13 @@ The correct session loop is:
|
|
|
188
190
|
|
|
189
191
|
The todo list is for _tracking_, not _executing_. The `bash` tool is what actually runs the command. Both must be used — add the task to the todo list AND call `bash` to execute it.
|
|
190
192
|
|
|
191
|
-
To ensure that you always get this right, even after compaction, you should always add executing the get-next-task as a todo item, with the full command example
|
|
193
|
+
To ensure that you always get this right, even after compaction, you should always add executing the get-next-task as a todo item, with the full command example so that you never forget.
|
|
192
194
|
|
|
193
195
|
### Context Recovery After Compaction
|
|
194
196
|
|
|
195
197
|
**If you suspect context compaction or summarization has occurred** — for example, if your context window appears to contain only a high-level summary with next steps rather than the full conversation history — re-fetch your system prompt immediately before continuing:
|
|
196
198
|
|
|
197
199
|
```
|
|
198
|
-
CHATROOM_CONVEX_URL=<endpoint> \
|
|
199
200
|
chatroom get-system-prompt --chatroom-id=<chatroom-id> --role=<role>
|
|
200
201
|
```
|
|
201
202
|
|