Urgent.News

What's breaking now, across thousands of outlets.

AI

Why an AI coding agent can look idle while it's working: Termexo 0.10.8–0.10.9

I maintain Termexo, an MIT-licensed Windows workbench for Claude Code, Codex, OpenCode, Grok Build, and Antigravity. When several agent terminals are open, the useful question is not simply whether they produced output. It is which agent is running, which needs approval, and which result still needs a human review . The last five releases, v0.10.5 through v0.10.9, improve that path from starting…

Termexo, an MIT-licensed Windows workbench for Claude Code, Codex, OpenCode, Grok Build, and Antigravity, has released updates 0.10.8 and 0.10.9 to enhance its functionality. The updates aim to clarify the status of agent terminals, which can sometimes appear idle even when actively working.

Previously, the order in which agent events, terminal input, and recovery states were displayed in the UI was not guaranteed to match the chronological order of events. For instance, an idle state from startup could follow a running state, leading to the agent being incorrectly perceived as idle while still functioning.

With the update to version 0.10.8, Termexo addressed this issue by checking the installed CLI behavior of all five supported agents. OpenCode 2 now reports execution, input requests, failures, and completions using its current plugin interface. Grok Build utilizes lifecycle hooks. The UI now interprets keyboard input more contextually, ensuring that Esc, Enter, and approval actions do not all be interpreted as the agent running.

In version 0.10.9, Termexo redesigns the display of agent status. Instead of placing status on the workspace row, the update presents a compact set of icons in terminal order. The icons reflect the agent's state: gray for idle, animated green for running and thinking, red for errors and approval, and green check for completion. Hovering over an icon reveals the terminal's current name, including any rename.

The green check symbol indicates completion of the task, not acceptance of the generated code. Users are still required to open the terminal, review the output and changes, and then click Confirm completion to clear the reminder. After returning to idle, a live terminal resumes its idle state, while an exited terminal becomes stopped.

Termexo also addresses a potential issue with the Git branch display. In version 0.10.9, the branch is read from Git for the selected terminal's launch directory, rather than showing a saved default such as main after a repository change. Selecting another terminal clears the old branch until its own check completes. Non-Git directories and unknown results remain blank.

The branch display is specific to the terminal's launch directory, not the shell's working directory. If a user navigates to a different repository within the shell, the label in Termexo's corner does not follow the change.

The update to version 0.10.5 introduced task-board state and snapshot management using local SQLite. Version 0.10.7 guides users through project selection and CLI checks during their first workspace creation, with repair and retry options. The update saves the project before launching the agent and preserves user-entered settings if saving fails. Termexo currently supports Windows x64, and the update can be downloaded from the project's website, along with access to the source code and a 30-second workbench recording.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

Wie nutzt man GPT-6.1 Sol API

Um die GPT-6.1 Sol API aufzurufen, senden Sie eine POST-Anfrage an https://api.openai.com/v1/responses mit "model": "gpt-6.1-sol" und Ihrem Schlüssel als Bearer-Token.

  • Send POST request to https://api.openai.com/v1/responses
  • Set model to gpt-6.1-sol and use Bearer Token
  • Migrating from gpt-6-sol mostly involves string swaps

More from Wednesday 30 September →