dsh-py-codeact 0.3.2 → 0.3.3

package/lib/index.js

@@ -5,7 +5,7 @@
  *
  * So this is NOT a `CodeRuntime` backend — it could not conform. It is an ordinary tool plugin that owns its own kernel: one IPython process per conversation tree with a shell per agent, globals surviving between calls, the model's action space being Python code and its observation that cell's output.
  *
- * It still emits `tool/code-dispatch-start` / `tool/code-dispatch`, so bridged tool calls render as SUBTOOL rows in the existing trajectory UI with no client change.
+ * It emits the session format's PTC dispatch events, so bridged tool calls render as SUBTOOL rows in the existing trajectory UI with no client change.
  *
  * @module dsh-py-codeact
  */
@@ -660,7 +660,9 @@ export function apply(ctx, config = {}) {
       console.warn(`[dsh-py-codeact] no agent on execution ${exec.callId}: sub-calls will run but not appear as SUBTOOL rows`)
     }
     const trace = { rootCallId: exec.rootCallId, parentCallId: exec.callId, subCallId, name, arguments: args }
-    session?.append('tool/code-dispatch-start', trace)
+    // V3 rejects the old Code Mode tags even though their payload is unchanged. Older hosts in our peer range still require them.
+    const dispatchEvent = session?.header?.version >= 3 ? 'tool/ptc-dispatch' : 'tool/code-dispatch'
+    session?.append(`${dispatchEvent}-start`, trace)
 
     // Every outcome has to emit the terminal event, throws included: if `ctx.tools.execute` rejects rather than returning `{isError:true}` (an abort, a policy wrapper throwing), the Python side is still answered, but the SUBTOOL row would sit in the trajectory as "running" forever.
     try {
@@ -674,7 +676,7 @@ export function apply(ctx, config = {}) {
         signal: exec.signal,
       })
 
-      session?.append('tool/code-dispatch', { ...trace, isError: outcome.isError, content: outcome.content })
+      session?.append(dispatchEvent, { ...trace, isError: outcome.isError, content: outcome.content })
       // Pixels cannot travel through the bridge: `value` is JSON, so a `read_image` result reaches the cell as width/height/attachmentId and NOTHING to look at. Re-attach the blocks the way Code Mode does, and the image lands in the conversation right after this cell — the model sees it on its next step. Without this the model believes the call succeeded, gets metadata, and cannot tell why it still cannot see anything.
       if (!outcome.isError && contentHasImage(outcome.content ?? [])) {
         exec.deferContext(createUserMessage({ content: outcome.content, source: { kind: 'plugin', plugin: 'dsh-py-codeact' } }))
@@ -684,7 +686,7 @@ export function apply(ctx, config = {}) {
       // falling back to the wrapper there would hand the cell the one shape it was promised not to see.
       return toolCallReply(outcome, entry.envelopes.get(from)?.has(name))
     } catch (error) {
-      session?.append('tool/code-dispatch', { ...trace, isError: true, content: [{ type: 'text', text: String(error?.message ?? error) }] })
+      session?.append(dispatchEvent, { ...trace, isError: true, content: [{ type: 'text', text: String(error?.message ?? error) }] })
       throw error
     }
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-py-codeact",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "CodeAct agent loop for the DeepSeek Harness: a persistent IPython session as the model's action space, with harness tools bridged in as a virtual `__dsh__.tools` module.",
   "license": "MIT",
   "repository": {