antechamber 1.0.22 → 1.0.24

package/CHANGELOG.md

@@ -7,6 +7,23 @@ and this project uses [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [1.0.24] - 2026-10-27
+
+### Fixed
+
+- Keep each reply in its own turn in OpenChamber 2.x after history is reloaded. A reply's request can start a few
+  milliseconds before OmO writes its prompt, so a restored reply sorted ahead of its prompt: the first turn's replies
+  vanished and each later turn's first reply was drawn in the turn before.
+
+## [1.0.23] - 2026-10-27
+
+### Fixed
+
+- Draw shell and eval cards in OpenChamber 2.x as shell cards: the command as code, then its live output. OpenCode
+  2.x renamed `bash` to `shell`, and OpenChamber 2.x drew `bash` cards with its generic body, listing `Command:` and
+  `Description:`. The v2 API now reports these cards as `shell`, and the OmO Compatibility extension heads `shell`
+  cards too.
+
 ## [1.0.22] - 2026-10-26
 
 ### Fixed

package/dist/session-history.js

@@ -142,6 +142,8 @@ export function parsePiSessionText(s, agentName, raw) {
     let currentModel = { providerID: "unknown", modelID: "unknown" };
     let currentThinkingLevel;
     let lastUserId = "";
+    // When the newest user-role record (prompt, context, compaction, user shell) was created. A reply must sort after it.
+    let userAt = Number.NEGATIVE_INFINITY;
     // Like live agent_end, a new user turn closes the previous run: its own
     // unresolved provider cards end with that run's stop reason.
     let runAssistant;
@@ -166,6 +168,7 @@ export function parsePiSessionText(s, agentName, raw) {
             const compaction = compactionMessages(s, e.id ?? `r${indexOf.get(e) ?? 0}`, e.summary, entryTime(e), currentModel, currentThinkingLevel);
             out.push(...compaction);
             lastUserId = compaction[0].info.id;
+            userAt = compaction[0].info.time.created;
             continue;
         }
         if (e.type === "custom_message") {
@@ -193,6 +196,7 @@ export function parsePiSessionText(s, agentName, raw) {
                     ? [{ type: "text", text: e.content }]
                     : [];
             const time = entryTime(e);
+            userAt = time;
             if (e.id)
                 s.tree.messageEntries[contextID] = e.id;
             out.push({
@@ -236,6 +240,7 @@ export function parsePiSessionText(s, agentName, raw) {
             if (e.id)
                 s.tree.messageEntries[msgId] = e.id;
             lastUserId = msgId;
+            userAt = created;
             const info = {
                 id: msgId,
                 sessionID,
@@ -263,6 +268,7 @@ export function parsePiSessionText(s, agentName, raw) {
             const stem = userId?.slice(0, -1) ?? mappedIds[0] ?? `msg_${sessionID}_r${idx}`;
             const msgId = `${stem}z`;
             lastUserId = `${stem}u`;
+            userAt = created;
             if (e.id) {
                 s.tree.messageEntries[msgId] = e.id;
                 s.tree.messageEntries[lastUserId] = e.id;
@@ -320,16 +326,17 @@ export function parsePiSessionText(s, agentName, raw) {
                 `msg_${sessionID}_r${idx}`;
             if (e.id)
                 s.tree.messageEntries[msgId] = e.id;
+            // The reply starts when its request starts (`m.timestamp`), which can be a few ms before pi writes the prompt
+            // entry that `userAt` comes from. OpenChamber 2.x groups turns by creation time, so a reply created before its
+            // prompt would move into the previous turn, or vanish before the first one.
+            const started = Math.max(typeof m.timestamp === "number" && Number.isFinite(m.timestamp) && m.timestamp <= created
+                ? m.timestamp
+                : created, userAt + 1);
             const info = {
                 id: msgId,
                 sessionID,
                 role: "assistant",
-                time: {
-                    created: typeof m.timestamp === "number" && Number.isFinite(m.timestamp) && m.timestamp <= created
-                        ? m.timestamp
-                        : created,
-                    completed: created,
-                },
+                time: { created: started, completed: Math.max(created, started) },
                 parentID: lastUserId,
                 modelID: currentModel.modelID,
                 providerID: currentModel.providerID,

package/dist/v2.js

@@ -180,17 +180,22 @@ export function toV2AssistantMessage(info) {
         msg.error = i.error;
     return msg;
 }
+/** OpenCode 2.x renamed `bash` to `shell`; OpenChamber 2.x draws a shell card (command, live output) only for `shell`. */
+function v2ToolName(tool) {
+    return tool === "bash" ? "shell" : tool;
+}
 function toolContent(part) {
     const st = part.state;
+    const name = v2ToolName(part.tool);
     const start = st.status === "pending" ? undefined : st.time.start;
     const end = st.status === "pending" || st.status === "running" ? undefined : st.time.end;
     const base = {
         type: "tool",
         id: part.callID,
-        name: part.tool,
+        name,
         // keep the SDK v1 spellings too — harmless and tolerates older readers
         callID: part.callID,
-        tool: part.tool,
+        tool: name,
         executed: false,
         time: {
             ...(start !== undefined ? { created: start, ran: start } : {}),
@@ -555,11 +560,12 @@ export class V2EventTranslator {
     }
     onToolPart(directory, part) {
         const st = this.state(part.sessionID);
+        const name = v2ToolName(part.tool);
         let ts = st.tools.get(part.id);
         if (!ts) {
             ts = {
                 callID: part.callID,
-                name: part.tool,
+                name,
                 started: false,
                 inputEnded: false,
                 called: false,
@@ -576,7 +582,7 @@ export class V2EventTranslator {
         if (state.status === "pending") {
             if (!ts.started) {
                 ts.started = true;
-                frames.push(this.frame(directory, "session.tool.input.started", { ...base, name: part.tool }));
+                frames.push(this.frame(directory, "session.tool.input.started", { ...base, name }));
             }
             const raw = state.raw ?? "";
             if (raw.length > ts.raw.length) {
@@ -586,13 +592,13 @@ export class V2EventTranslator {
             }
             return frames;
         }
-        // mapTool renames a call when it leaves pending (eval -> bash). OpenChamber 2.x takes the tool name only from
+        // mapTool renames a call when it leaves pending (eval -> shell). OpenChamber 2.x takes the tool name only from
         // input.started, so announce the card again under its new name before its input ends.
-        if (!ts.started || (ts.name !== part.tool && !ts.inputEnded)) {
+        if (!ts.started || (ts.name !== name && !ts.inputEnded)) {
             ts.started = true;
-            frames.push(this.frame(directory, "session.tool.input.started", { ...base, name: part.tool }));
+            frames.push(this.frame(directory, "session.tool.input.started", { ...base, name }));
         }
-        ts.name = part.tool;
+        ts.name = name;
         if (!ts.inputEnded) {
             ts.inputEnded = true;
             frames.push(this.frame(directory, "session.tool.input.ended", {

package/extensions/omo-compat/README.md

@@ -11,10 +11,10 @@ What it does today:
   instead of the generic "Agent Task".
 
 - **Eval cell headers.** OpenChamber 1.24 streams live output only for shell
-  cards, so antechamber shows OmO eval cells as shell cards. With this extension
-  their header reads `JS Eval` (or `Python Eval`) and the cell's summary instead
-  of "Shell Command" and the first line of code. Other shell cards keep their
-  normal header.
+  cards, so antechamber shows OmO eval cells as shell cards (`bash` in OpenChamber
+  1.x, `shell` in 2.x). With this extension their header reads `JS Eval` (or
+  `Python Eval`) and the cell's summary instead of "Shell Command" and the first
+  line of code. Other shell cards keep their normal header.
 
 ## Requirements
 

package/extensions/omo-compat/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-compat",
-  "version": "1.0.22",
+  "version": "1.0.24",
   "description": "OpenChamber extension: displays OmO tool calls the way OmO means them when OpenChamber runs on antechamber",
   "private": true,
   "type": "module",
@@ -22,6 +22,11 @@
           "title": "{metadata.evalTitle}",
           "subtitle": "{metadata.evalSubtitle}"
         },
+        {
+          "match": "shell",
+          "title": "{metadata.evalTitle}",
+          "subtitle": "{metadata.evalSubtitle}"
+        },
         {
           "match": "task",
           "title": "{metadata.agentTitle}",

package/extensions/omo-dag/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-graph",
-  "version": "1.0.22",
+  "version": "1.0.24",
   "description": "OpenChamber extension: live, interactive graph of the OmO sub-agents behind the current session",
   "private": true,
   "type": "module",

package/extensions/omo-work/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber-omo-work",
-  "version": "1.0.22",
+  "version": "1.0.24",
   "description": "OpenChamber 2.x Work Status section: OmO todo phases, monitors, eval cells and background work of the current session",
   "private": true,
   "type": "module",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "antechamber",
-  "version": "1.0.22",
+  "version": "1.0.24",
   "description": "OpenCode-compatible HTTP/SSE server that lets OpenChamber drive the pi coding agent (and OmO) over RPC",
   "type": "module",
   "license": "MIT",