Check Logs

The user already has a turborepo dev TUI running in another herdr pane. Find that existing pane, focus the requested task, read its logs, and answer from evidence. Never start a new dev server from this skill.

If the user gave an app name in the argument, use it. If not, infer from context — the most recent app they were editing, what they just mentioned, or what shows a failure glyph (⨯) in the sidebar.

Turbo TUI reference

• The screen has two columns: a sidebar listing every task (e.g. @gam3s/frontend#dev, //#dev:cms, @gam3s/backend#dev) and a log column showing the selected task's stdout/stderr.
• The sidebar has glyphs: » for running, ⨯/✗ for failed. The header at the top of the right column is <task-name> > <message> — that tells you which task you're actually looking at.
• Only the focused task's logs appear in the buffer. Other tasks' output is not in scrollback until you select them.
• Keybinds (turbo ≥ 2.x): ↑/↓ or j/k move sidebar selection (also swaps the log column), / opens a search/filter, u/d scroll logs, U/D page logs, t/b jump to top/bottom of the focused task's logs, m shows the keybind help.
• Never press q (quits the TUI) or i (gives the user's keyboard to the running process). Use Enter only to confirm a / search selection — outside search it can focus/interact depending on TUI state. The skill is read-only.

Steps