lampboard 0.2.4

Two defects reported from use, and one of them was in yesterday's fix.

Requires macOS 14 or later (macOS 26 for dictation). Signed with a Developer ID and notarized by Apple.

Amber is for a turn somebody is blocking

A Codex row blinked amber — the state that means "this is stopped until you answer" — for requests Codex approves by itself. Amber only lifts when the command finishes, so an automatic approval kept a row blinking for as long as the work took: 6.0 s, 6.4 s and 31.0 s during one audit, each of them also firing a notification nobody needed.

Who answers a request is not in the event Codex sends. It is in the session's rollout, which that event names, and it changes mid-session — so it is read for every request. When it cannot be read the request is shown: a false amber costs a glance, a swallowed one costs a stopped turn nobody knows about.

The lane name is gone

The row menu had "Rename the lane…" one line under "Rename this conversation…". It gave every conversation of that agent in the project the same name, including ones opened later, and said so only after you had chosen it. Renaming one Codex conversation renamed them all.

Removed, along with the names already saved under it — without that they would have kept applying with no menu left to clear them. What stays is the name of a project and the name of one conversation.

GET /sessions now reports the project's name in label where it reported the lane's. It is the only change visible outside the panel.

Also

Renaming a conversation from the chat window now reaches the column immediately. It was saved correctly and the row kept the old name until an unrelated event arrived, because the panel rebuilds on state changes and a rename is not one.