-
For disappearing terminals, fix the state transition that drops their placements. Do not add recovery UI or a new user workflow unless explicitly requested.
-
Treat
BLUEPRINT.mdas navigation to its AI author. It must not open as a standalone rendered document; the Blueprint UI is the author chat or terminal's companion. -
Validate user-visible navigation in the running UI or E2E, not only with opener unit tests.
-
A terminal in the host catalog is not necessarily present in the layout. Navigation must attach and reveal the resource, not merely select its terminal key or focus a companion.
-
Blueprint authors belong in the main column. A test that only checks that the terminal and Blueprint are visible can pass while both are incorrectly placed in the bottom dock; assert the layout region.
-
When comparing terminal image paste across agents, trace both consumers of an empty bracketed paste. A text-only terminal can still trigger a CLI's native clipboard-image fallback; missing image transport alone does not explain different behavior.
-
For terminal input bugs, wait for the raw-mode process to signal readiness before sending a key or wheel event. Test again after the browser terminal remounts: fresh input can work while live PTY modes disappear from replay. A passing PTY protocol probe only establishes byte delivery; reproduce the real TUI behavior before changing key encoding or scroll policy.
-
When screenshot text is absent from a repository search, check ignored source files and the current checkout before concluding that the UI belongs to another repository. Exclude generated builds and dependencies explicitly when using
--no-ignore. -
When a user says a name-entry dialog should react to an existing path, check for feedback while typing; a server error after pressing Create does not satisfy that interaction.
-
Codex treats command text and Enter arriving in one burst as a paste with a newline. Submit slash commands with a separate, delayed Enter, and test the terminal's response rather than only an optimistic chip state.
-
When compacting ThinkRail developer instructions, distinguish launcher prompt appendixes from AGENTS.md/global agent rules; confirm the intended layer before editing.