v1.0.40

Fixed

• Keep the conversation in order after a ! shell command. The history refresh that follows a shell command sent
  every earlier reply to OpenChamber again with the current time as its creation time, so OpenChamber moved those
  replies after the prompts they answered and placed the shell card among them. Replies now keep their own times.

v1.0.39

• fix(v2): give each task batch card its own tool id (#90)

v1.0.38

Fixed

• Reverting a /compact message works again. The revert was rejected as an unknown message and OpenChamber 2.x
  dropped the error silently. It now returns the conversation to where it was before the compaction.

v1.0.37

• feat(session-hosts): tear down private OmO hosts on macOS (#85)

v1.0.36

Added

• Clean up after the agent on macOS. Disposal now records the agent's process group and re-identifies each member
  before signalling it, so child processes that outlive the agent are stopped instead of being left behind. Linux
  keeps reading /proc; macOS reads /bin/ps, because Node has neither /proc nor pidfd there. A process that has
  already exited (zombie) never counts as a survivor.

v1.0.35

• test: resolve fixture paths with fileURLToPath (#86)

v1.0.34

Fixed

• Show a session's subagents under that session. A session list that OpenChamber sent while a new session's agent
  was still starting could adopt the agent's file as a second copy of the session, and subagents started
  later were filed under that copy, so the session showed none of them.

v1.0.33

Fixed

• Stop showing replies twice, and keep new messages and ! shell commands at the end of the conversation, in a
  session that has a shell command OmO never reported back (for example one stopped by the old one-minute deadline).
  Every read of the conversation re-parsed the session file without the live replies, so each reply read mid-turn
  gained a second, restored copy, and those copies piled up after newer messages. Restart OpenChamber's adapter to
  clear copies already in memory.

v1.0.32

Fixed

• Stop killing the agent when a shell command run from the composer takes longer than a minute, such as an
  interactive login. A user shell now runs until its command exits or you press Stop; only a shell that OmO still
  has not answered a minute after Stop stops the agent.
• Show a shell command's output live in its card while it runs, so a link or code a command prints before it waits
  (such as a login URL) can be copied. Before, the card stayed empty until the command ended. A command you stop
  keeps the output it printed.

v1.0.31

Fixed

• Show the MCP servers and their count before a session runs. A directory with no running agent used to report no servers,
  so the sidebar's "MCP servers" count sat at 0 in a new chat, on a dormant project and after the idle reaper stopped the
  last agent. The servers are now read by a short-lived agent started for that read alone.
• Keep that list current: antechamber announces mcp.status.changed when an agent starts, stops or reports new MCP state,
  so OpenChamber re-reads instead of keeping a stale count (it treats an answer as fresh for a minute).
• Stop a sign-in from failing with "pi process disposed" when OmO answers auth-start only while auth-complete is
  already running. The agent started for the sign-in was stopped mid-command; the completion now owns it until it ends.