Tool-run embedding for agents

Practitioner rule

When an agent compiles (or runs any long tool), do not treat stderr scrollback as the UX, and do not open one OS window per run.

OpenShellOrg defines a Tool Run bus: structured diagnostics in, short CLI stub + magic link out, shared daemon for history, embeddable library for host chrome.

Canon: Tool runs and diagnostics · Command channels.

What Dev-Centr should do

| Mode | When | |---|---| | embed (preferred in harnesses) | Mount run chips / diagnostic panels on the agent timeline; suppress standalone popup | | auto | If the harness registers as an embedding host, same as embed; else allow GUI | | headless | CI / pure automation — bus + log only | | gui | Rare — force standalone window |

Always still talk to the daemon when the user wants a second index of past compiles outside the chat scroll.

What Dev-Centr should not do

  • Invent a second diagnostics protocol

  • Merge stdout and stderr in harness capture by default (keep channels; optional explicit merged)

  • Own programmer-POV wording (HCI Nerdz) or OS tray/flash helpers (Desktop Tooling) as if they were the bus

Related