fix(seer): Tidy up the workflows table#114545
Merged
Conversation
github-actions
Bot
added
the
Scope: Frontend
trevor-e
changed the title
Base automatically changed from
trevor-e/fix/seer-night-shift-early-persist-agent-run-id
to
master
May 1, 2026 09:44
agentic_triage_strategy lives under tasks/seer/night_shift/ and is only ever called from the night shift cron, so the callback-based decoupling from SeerNightShiftRun wasn't earning its keep. Take the run directly and persist agent_run_id in place — fewer indirections, the cron call site collapses back to a one-liner. Co-Authored-By: Claude <noreply@anthropic.com>
There's only one caller and it always has a run, so the Optional was unnecessary defensive coding. Drop the None default and the corresponding null check. Co-Authored-By: Claude <noreply@anthropic.com>
The added paragraph just narrated what the code shows. Co-Authored-By: Claude <noreply@anthropic.com>
The container capped the table at 50% of the viewport at lg+ breakpoints, which squeezed the 9-column layout and clipped content on full-width windows. Let the table fill the available width instead. Co-Authored-By: Claude <noreply@anthropic.com>
The Status column showed "Completed" the entire time a run was executing, which was a lie — the row was created at the start of the run and the only backend signal we have is the error message. The Explorer link covers the "is something happening" question, so just remove the column. When a run errored, surface the message inline in the Issues cell instead of hiding it behind a row expansion. Co-Authored-By: Claude <noreply@anthropic.com>
chromy
force-pushed
the
trevor-e/fix/seer-workflows-table-clipping
branch
from
b794720 to
287c74d
Compare
Re-cap the workflows table at 60% on lg+ so the Ask Seer drawer can sit beside it instead of overlapping. Move the Explorer link to be the first column after the expand chevron — it's the most useful action on each row, so put it where you don't have to look for it. Co-Authored-By: Claude <noreply@anthropic.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9ce6a58. Configure here.
3 tasks
cleptric
pushed a commit
that referenced
this pull request
May 5, 2026
A few small fixes to the `/seer/workflows/` table: **Cap the table at 60% on wide screens** The original 50% cap squeezed the table on its own but kept room for the Ask Seer drawer to sit beside it. 60% gives the table more breathing room while still leaving the drawer space. **Drop the Status column, surface errors inline** The Status column showed "Completed" the entire time a run was executing, which was a lie — the row is created at the start of the run and the only completion-adjacent backend signal we have is `error_message`. The Explorer link already covers "is something happening" for in-flight runs, so the column wasn't earning its keep. When a run errors, the message now renders inline in the Issues cell. **Move Explorer to the first column after the chevron** It's the most useful action on each row, so put it where you don't have to look for it. Stacked on #114544. --------- Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A few small fixes to the
/seer/workflows/table:Cap the table at 60% on wide screens
The original 50% cap squeezed the table on its own but kept room for the Ask Seer drawer to sit beside it. 60% gives the table more breathing room while still leaving the drawer space.
Drop the Status column, surface errors inline
The Status column showed "Completed" the entire time a run was executing, which was a lie — the row is created at the start of the run and the only completion-adjacent backend signal we have is
error_message. The Explorer link already covers "is something happening" for in-flight runs, so the column wasn't earning its keep. When a run errors, the message now renders inline in the Issues cell.Move Explorer to the first column after the chevron
It's the most useful action on each row, so put it where you don't have to look for it.
Stacked on #114544.