Attyx v0.4.15

Answer agents without leaving the dashboard (#290)

attyx dashboard is no longer read-only. Press i on any agent row to expand it in place and respond right there — no jumping to the pane, no switching windows.

The inline panel shows the agent’s latest message for context, then lets you:

• Reply to an agent. Type a message and press Enter; Attyx sends it straight to that agent’s pane.
• Pick an option. If the agent is waiting on a numbered prompt, the dashboard turns those choices into selectable buttons.
• Grant permission. Approval prompts show up the same way, so you can approve or deny with a single key.

Selecting an agent that needs input opens the picker automatically; other rows open a reply box. Esc cancels, and sending never steals focus from the dashboard.

Scan agents by tab and session (#290)

The dashboard now shows a TAB column, so agents are easier to tell apart when several are running in one session. Agents are also grouped under their session name, which makes multi-session swarms much easier to read at a glance.

attyx list agents --json includes the tab name too, as tab_name.

agent read and capture now support opencode and Pi (#288)

attyx agent read and attyx agent send --capture now work with opencode and Pi agents, not just Claude Code and Codex. That means you can read the last assistant message or capture the output from a completed turn across all supported agents.

This also gives the dashboard’s inline reply panel better context for opencode and Pi panes.

Agent-status dots work in xyron (#287)

Starting Claude Code, Codex, opencode, or Pi inside a xyron shell now lights the agent-status dot immediately, then clears it when the agent exits. Previously xyron sessions could stay invisible until the agent emitted its own status update.

Popups find attyx reliably (#289, #291)

Popup commands now get the Attyx CLI directory on their PATH, so config entries like a dashboard popup can run attyx even when the app was launched outside a terminal.

The PATH override is passed through the child environment instead of rewriting the shell command, so normal command lookup keeps working and unusual PATH values no longer break popup launch.