@chipschat/acp 1.0.32 → 1.0.34

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 CHANGED
@@ -131,6 +131,13 @@ its asks). Then nothing reaches Chips as a card. Put them where they ask:
131
131
  Permissions page: Claude Code's `permissions` lists from your settings and each agent's folder,
132
132
  and the mode; for Codex, its mode. It reads them and never writes them. Needs Chips SDK 1.0.10;
133
133
  on an older one nothing is sent.
134
+ - A person can pick another mode for a while on the harness's settings page in Chips (Chips ADR
135
+ 0300): Claude Code's Default, Accept edits, Auto or Bypass permissions; Codex's Read-only,
136
+ Workspace access, Auto review or Full access, those the adapter offers. Each session goes into
137
+ the pick, the open ones at once, and back into the mode above when its time is up. A pick the
138
+ adapter doesn't offer leaves it in the mode above. This is for the kinds as known here, started
139
+ in the mode above; a config with another `mode` or `command` gets no picker. Needs Chips SDK
140
+ 1.0.11; on an older one the sessions stay in the mode above.
134
141
 
135
142
  ## Live
136
143
 
@@ -168,7 +175,7 @@ minutes and loaded again with its memory. Fourteen runs, none failed, $0.35, all
168
175
  | Context gauge, cost | `usage_update` (`used`/`size`; `cost` in USD, the turn's share) |
169
176
  | The reply | `agent_message_chunk`s gathered into one message; `NO_REPLY` alone is the turn passed |
170
177
  | Files in the reply | each `MEDIA:<path>` line of the reply sent as an upload with its words, only from the agent's folder (`sendAnswer`); the post says why one could not go |
171
- | Approval card | `session/request_permission`, asked in the agent's own words where the call has a `description` (Claude Code's commands: "Syntax-check game.js? `node --check game.js`"), else "Allow it to" and the call's title; allowed always picks `allow_always`, except for a command, which picks `allow_once` since Chips remembers it by how each part starts (Chips ADR 0239); no picks `reject_once`; Stop answers `cancelled`; the card hears how the call went |
178
+ | Approval card | `session/request_permission`, asked in the agent's own words where the call has a `description` (Claude Code's commands: "Syntax-check game.js? `node --check game.js`"), else "Allow it to" and the call's title; a yes picks `allow_once`, an Always too while Chips keeps the rule (Chips ADR 0239), so switching the rule off in Chips brings the asks back; with the harness's Chips's rules off (`keeps: "harness"`, Chips ADR 0300) an Always picks `allow_always` where the ask offers exactly one and the call is not a `switch_mode`, so Claude Code's plan ask, whose always options are "use auto mode" and "bypass permissions", is answered with its once; no picks `reject_once`; Stop answers `cancelled`; an ask that expires with nobody's answer is answered `cancelled` too, its prompt is stopped (`session/cancel`), and the turn ends on one line in the space: "Nobody answered, so I stopped. Ask me to carry on."; the card hears how the call went |
172
179
  | Question card | `elicitation/create` form of up to four choice or yes/no fields; anything else is declined; Stop answers `cancel` |
173
180
  | Stop | `session/cancel` |
174
181
  | Pause (Chips ADR 0293) | each run says `pausable: true` as it starts; Pause is `session/cancel` with the run kept and nothing posted, and Resume the next prompt of the same session: "You were paused partway through this. Carry on from where you stopped. Nothing you wrote before the pause reached the room, so write your whole reply.", then anything steered meanwhile. A Pause before a prompt holds it; one while an approval or question card waits stops nothing, and the answer reaches the agent on Resume |
@@ -1,9 +1,9 @@
1
1
  # Third-party notices
2
2
 
3
- `dist/main.js` in @chipschat/acp 1.0.32 carries these packages, bundled in. Each one's
3
+ `dist/main.js` in @chipschat/acp 1.0.34 carries these packages, bundled in. Each one's
4
4
  licence follows.
5
5
 
6
- ## @chipschat/harness 1.0.10 (Apache-2.0)
6
+ ## @chipschat/harness 1.0.11 (Apache-2.0)
7
7
 
8
8
  Apache License
9
9
  Version 2.0, January 2004
@@ -207,7 +207,7 @@ Apache License
207
207
  See the License for the specific language governing permissions and
208
208
  limitations under the License.
209
209
 
210
- ## @chipschat/protocol 1.0.10 (Apache-2.0)
210
+ ## @chipschat/protocol 1.0.11 (Apache-2.0)
211
211
 
212
212
  Apache License
213
213
  Version 2.0, January 2004