Skip to content

v2.25.19 — Codex Host Support

Choose a tag to compare

@github-actions github-actions released this 09 Nov 09:36
· 87 commits to main since this release

Tersio 2.25.19 — Codex joins as a host, and the dashboard gets a batch of fixes.

Issues closed

  • #91 DSH host: entry never activates from npm install — exports point at .ts inside node_modules — thanks @nosidak
  • #93 DSH: rtk_run always fails with INVALID_TOOL_OUTPUT — string schema, object return — thanks @nosidak
  • #97 tersio update --host omp causes lock file version drift — thanks @FrancoStino

Pull requests

  • #96 feat: add Codex as a Tersio host
  • #98 fix: repin the OMP manifest when node_modules already matches
  • #95 fix: activate the DSH plugin from npm and answer rtk_run with a string

Everything that changed

Added

  • Tersio registers its Codex prompt hook in ~/.codex/hooks.json, beside rtk and headroom. Current Codex removed plugin-declared hooks, so the copy inside the plugin never ran and a literal /combo lite reached the model. Uninstall removes only Tersio's entry.
  • /headroom on|off|status is now a Codex slash command, with its own prompt file and $headroom skill. It stores the same headroomDefault the CLI writes and says the endpoint route applies at install or from the dashboard switch, because moving the route needs the running proxy.
  • A literal /combo lite answers in Tersio's prompt hook instead of the model: the mode applies and the command returns before a turn starts, with no network round trip.
  • Codex's prompt hook returns a systemMessage on every turn: the same 🧩 LITE | 🪨 caveman:LITE | … combo line the DSH bar and the CLI print. Codex Desktop exposes no plugin status bar, so the hook result is the surface.
  • /combo help lists the presets and changes nothing.
  • Codex is now a Tersio host: tersio install --host codex materializes a local marketplace and installs the portable plugin with its bundled MCP server. A prompt hook applies literal /combo, /caveman, and /ponytail commands and keeps those modes active for the session; per-mode skills expose $combo, $caveman, $ponytail, $pstack, $rtk, and $tersio, with /prompts:* fallbacks. Codex rollout sessions feed every dashboard page with requests, models, providers, API, payloads, errors, tools, real working-directory projects, and separate traces. Headroom routes Codex through its own init codex / unwrap codex commands and the dashboard detects CLI and desktop installs on macOS, Windows, and Linux; RTK remains out of the Codex v1 surface.

Changed

  • The upstream Agent copies chart labels each row with the agent's own mark instead of its name, so six agents fit without a wide axis. The caption and the chart's accessible name still spell every agent out.
  • The Caveman pin moves to v4.1.0. All three tracked rule bodies are byte-identical between v4.0.1 and v4.1.0, so no mode text changes; the pin only clears the stale badge. Caveman 4.1.0's two action items target its own proxy config and caveman-compress, neither of which Tersio writes.
  • tersio install --host omp rewrites the OMP manifest pin when node_modules already matches, so omp plugin doctor no longer reports version drift. Thanks to @FrancoStino (#97).
  • A blocked Codex command now prints the combo line under its confirmation, because Codex renders only reason and drops systemMessage.
  • Headroom's Codex route writes openai_base_url with the /v1 path, so Codex upgrades ws://…/v1/responses. A root URL answered 403 on the WebSocket upgrade before every turn fell back to HTTPS, which read as an error on each run.
  • The Codex install now says that its prompt hook needs one approval in /hooks. Codex skips a hook whose recorded trust hash no longer matches, and the install re-adds the plugin, so a literal /combo lite reaches the model and reports the slow path instead of answering.
  • A quick start drawer now holds its header and footer on the same skeleton as its body. Install and Update were reachable while the first read was still in flight, and headroom and rtk defaulted to "not installed" until health answered, so the footer offered Install for a tool that was already there.
  • The canvas mode badges for caveman, pstack, Ponytail, RTK, and Headroom now carry the version, tinted green when it matches the newest upstream the last check saw and orange when it is behind. An unmeasured check stays gray instead of claiming either, and the tooltip names both versions.
  • The dashboard harness badge shows the version alone, shortened to the release, and the Headroom drawer names the install option: durable or routed. DeepSeek Harness gained a version badge: /health asked the PATH wrapper, which is a stub that exits before answering, so the probe now prefers the desktop app's own CLI and reports 0.2.2-rc.1 instead of nothing.
  • The Ponytail rules load from the package's extensions/ponytail/skills when the module sits in dist/, which the build never copies skills into. Every emitted CLI used to report the broken-install stub instead of the real rules.
  • The Codex prompt hook reads session_id from its payload, so a mode command applies to the session that sent it instead of the host defaults.
  • Doctor groups advisory findings under a dedicated Warnings section and names Oh My Pi consistently. The Upstream check now compares Codex's generated hook and MCP files structurally, so absolute runtime paths no longer read as drift.
  • tersio now runs the command under bun whenever bun is installed, instead of the node its shebang names. The whole CLI follows, MCP server included, and TERSIO_RUNTIME=node keeps a machine on node. A real command spends about 15% less CPU; a command that only prints text pays roughly 30ms for the second boot.
  • The MCP server starts under bun directly when bun is installed, instead of booting node and then handing off to bun. Its process tree is one bun process at about 36 MB; a machine without bun stays on one node process at about 72 MB.
  • The MCP server no longer loads the whole dashboard to answer two tools. The agent-stats layer moved to its own module, so the server imports 30 files instead of 51.
  • The MCP server asks for a summary view instead of the dashboard full view. One tersio_stats call now costs about 18 MB of resident memory and 0.5s; it cost about 51 MB and 2s.
  • zlib is loaded when a cache row is first written or read, not at import, so a process that never caches never pays its 8 MB.
  • The proxy starts directly instead of through headroom install start, which kept a second 82 MB Python process alive for the life of the proxy.
  • A restart no longer brings that supervisor back either: the proxy is stopped and started directly with the upstream just written.
  • Uninstalling stops the proxy instead of leaving it serving a provider endpoint nothing points at.
  • Turning Headroom off for the last routed agent stops the proxy. One agent of two keeps it running.
  • A machine under 2 GB of memory is not given the proxy. The install names the floor as the reason, and TERSIO_HEADROOM_FORCE=1 overrides it.
  • Stopping the proxy only touches the port Tersio owns, so another tool running headroom on another port is left alone.
  • The installed tersio entry replaces its node process with bun in place, instead of keeping node alive to wait on a bun child, so a hand-off leaves one process instead of two.
  • The saved settings are parsed once and reused until the text changes, so restoring a session no longer parses the same file six times. The file is still read on every check, because a stat cannot see a same-size rewrite on Windows.
  • RTK output filtering keeps one temporary directory for the life of the process, instead of creating and removing one for every filtered result.

Fixed

  • The dashboard's Headroom update now passes --yes. Without the flag headroom asked a confirmation no TTY could answer, printed Aborted!, and left the binary where it was.
  • The Headroom drawer checks the release feed when it opens, so an available update is a button rather than a two-click hunt, and it waits three minutes for uv tool upgrade to finish instead of one.
  • The Headroom drawer names the agents that swap endpoints from the live routes. Codex and Oh My Pi keep headroom's own block, so they no longer read as endpoint swaps.
  • Quick start keeps its last read across navigation. Coming back paints the host state instead of a skeleton, and an install that was running when the page was left keeps its spinner, then reports its own result.
  • The proxy starts on the first agent session after a reboot. A proxy still binding its port was read as another tool's proxy, so the start was refused and the route pointed at a dead port. A proxy on Tersio's own port now waits instead of refusing.
  • A shell whose command line mentions headroom.cli proxy no longer counts as a proxy. pgrep -f matched the text, so a tersio doctor run could report one or refuse a start; only a Python interpreter counts now.
  • The proxy stops when the last agent session quits. Each session claims it, and a quit waits 2.5s before the stop so a restart does not race it. A session that dies without a quit stops refreshing its claim, which expires after 20 minutes.
  • A confirm prompt still reads its answer after the hand-off: the CLI opens its stdin reader when a prompt needs it, not when it boots.
  • The DSH plugin now activates from an npm install. The package root and ./dsh-plugin export the compiled dist/extensions/dsh/index.js instead of raw TypeScript, which Node refuses to strip under node_modules (ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING), so the entry never imported from the registry copy. Thanks to @nosidak (#91).
  • The DSH plugin reads its mode rules from the package root when it runs from dist/, so the caveman, Ponytail and pstack bodies no longer fall back to "rule is missing" on an npm install.
  • rtk_run in DeepSeek Harness answers the string its own schema declares. It returned { content } against a string schema, so every call failed with INVALID_TOOL_OUTPUT. A command that exits non-zero now returns its output as text instead of throwing. Thanks to @nosidak (#93).

Contributors

Thanks to @nosidak for #91 and #93, and to @FrancoStino for #97. Both reported the failures with enough detail to reproduce them.

Install

curl -fsSL https://github.com/KurutoDenzeru/tersio/releases/latest/download/install.sh | sh

Windows:

irm https://github.com/KurutoDenzeru/tersio/releases/latest/download/install.ps1 | iex

From npm: npm install -g @krtclcdy/tersio@2.25.19, or run it once with npx @krtclcdy/tersio@2.25.19 tersio install.

The tersio-npm.tgz asset is the same tarball the registry serves, for machines that install offline.