Release v1.0.3 · egeyesss/overterm

Added

Pi support. Pi sessions are recognised and get their own tab mark, label and detection patterns, instead of showing up as node.
Pi reports its own turns. oTerm installs an extension into ~/.pi/agent/extensions/ so a Pi session says exactly when a turn starts, finishes or needs you, rather than being read off the screen. There is a switch for it in the settings beside the Claude Code one, and deleting the file sticks.

A turn short enough that the window never collapsed no longer takes the terminal's keyboard focus. Answering a quick question needed a click first.
A terminal's automatic replies now go to its own session. With two tabs open, a background agent's cursor position and palette replies were being typed into whichever tab was on screen, which showed up as junk like 35;3R or 11;rgb:... at an idle prompt.
A tool that renames its own process is identified properly. This is why Pi read as node.
A session writing oTerm's markers is no longer assumed to be Claude Code, which renamed Pi sessions once they had the extension.
The busy-line scan measures up from where a program's interface ends rather than from the bottom of the terminal, so it is not thrown off by blank rows on a session that has not scrolled yet.

Pi does not report a failed turn differently from a finished one. Its extension API does not expose whether a run ended on an answer or an error, and oTerm treats both as the turn ending.
Pi's permission event only fires for prompts raised by extensions. A Pi install with no permission gate may never send one, in which case a session waiting on a question is revealed by the stall timer instead.
There is no frontend test suite yet, so the input routing fix is held in place by types rather than by a test.
If stray colour codes ever appear in a window with only one tab open, that is a different cause and worth reporting on #18.

Full Changelog: v1.0.2...v1.0.3