Skip to content

stop giving blocked and failed requests a click zone of their own - #158

Merged
hkonsti merged 2 commits into
mainfrom
hkonsti/failed-tool-call-click-zone
Oct 28, 2026
Merged

hkonsti merged 2 commits into
mainfrom
hkonsti/failed-tool-call-click-zone

Conversation

@hkonsti

@hkonsti hkonsti commented Oct 28, 2026 •

Copy link
Copy Markdown
Collaborator

On the home chart, a blocked or failed request always got a hit target, widened to at least 8px and as tall as the bar, which took clicks meant for the task under it. This removes that special case: a request of any outcome gets a target only where its stretch of the track is at least 8px wide, so a click on a short red or amber mark goes to the bar and opens the task. The rule lives in the shared timeline code, so the task page's timeline behaves the same way.

🤖 Generated with Claude Code


Open workspace in Conductor

…the timelines

A request that didn't go through always had a target, widened to at least 8px, which took the
click from the bar under it. Now every request gets a target only where its stretch is wide
enough to point at, so a click on a short red or amber mark opens the bar's task.
The step's text can show before the effect that remembers the agent runs, so reading it right
away failed now and then in ci.
@hkonsti
hkonsti merged commit 8e12db5 into main Oct 28, 2026
3 checks passed
@hkonsti
hkonsti deleted the hkonsti/failed-tool-call-click-zone branch October 28, 2026 01:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant