Overview Event Log and Gateway Log panels do not stay aligned when their content heights differ

[abhshabvz782-jpg]

Summary

On the Overview page, the Event Log and Gateway Log panels do not stay visually aligned when their content heights differ, which leaves mismatched bottoms and visible blank space.

Steps to reproduce

1. Start the dashboard from the current openclaw source checkout.
2. Open the Overview page.
3. Expand both Event Log and Gateway Log.
4. Let the page refresh until the two panels have different content lengths, or reproduce with one panel containing more rows than the other.
5. Observe that the two cards no longer share the same bottom edge; one panel can leave a large blank area or grow past the other instead of staying aligned.

Expected behavior

The two Overview log panels should remain visually aligned as a pair.
If Gateway Log is longer, it should scroll inside its own content area instead of extending the card height beyond Event Log.
If Event Log is longer, the Gateway Log card should preserve aligned bounds instead of leaving mismatched panel edges.

Actual behavior

When the panel content heights diverge, the Event Log and Gateway Log cards stop lining up.
This creates obvious bottom-edge mismatch and wasted blank space in the shorter panel.

Environment

• OpenClaw version: 2026.3.14
• Operating system: Windows 10 Pro 10.0.19045 (Build 19045)
• Install method: Source checkout with local dashboard/demo UI build
• Model: NOT_ENOUGH_INFO
• Provider / routing chain: NOT_ENOUGH_INFO

Evidence

Observed as a user-visible Overview layout issue involving the Event Log and Gateway Log cards.
Relevant UI classes observed during investigation were card ov-event-log and card ov-log-tail.
No crash or backend error log was required to reproduce the issue.

Impact and severity

• Affected: Dashboard users monitoring the Overview page
• Severity: Medium
• Frequency: Reproduced whenever the two panels contain different amounts of content
• Consequence: The Overview page looks visually broken and is harder to scan quickly

Additional information

NOT_ENOUGH_INFO

This issue was intended to be a bug report, specifically a behavior bug.
The GitHub sidebar currently shows no label and no type.
Could a maintainer please add the bug label and, if applicable, set the issue type to Bug?

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 24, 2026, 7:52 PM ET / 23:52 UTC.

Summary
Keep open. Current ClawHub main still lacks the reported Overview Event Log/Gateway Log UI, the cited ov-event-log/ov-log-tail classes, and a matching /overview route, so this is not implemented on main and needs maintainer routing rather than cleanup closure.

Reproducibility: no. Source inspection of current main finds no /overview route, Event Log/Gateway Log panels, or cited ov-* classes, so the reported in-repo UI cannot be exercised.

Next step
The reported Event Log/Gateway Log surface is absent from current ClawHub main, so maintainers need to identify or transfer the owning UI before a fix PR is safe.

Review details

Best possible solution:

Keep this as maintainer triage until the owning Overview UI is identified; then transfer/recreate it in the right repository or implement equal-height paired cards with internal scrolling in the actual component.

Do we have a high-confidence way to reproduce the issue?

No. Source inspection of current main finds no /overview route, Event Log/Gateway Log panels, or cited ov-* classes, so the reported in-repo UI cannot be exercised.

Is this the best way to solve the issue?

Unclear. The equal-height/internal-scroll fix sounds plausible for the actual UI, but the best in-repo solution cannot be chosen until maintainers identify the owning component or repository.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The report may belong to another OpenClaw runtime/dashboard repository or an older local demo build, but it lacks a screenshot, route path, or owning-repository pointer to transfer confidently.
• If ClawHub is expected to own this Overview page, the relevant route/component is currently missing, so a narrow CSS/card fix cannot be scoped from current main alone.

Codex review notes: model internal, reasoning high; reviewed against 3ef5f14d84a7.

Label changes

Label changes:

• remove clawsweeper:not-repro-on-main: Current issue advisory state no longer selects this label.

Label justifications:

• P3: The reported problem is a visual layout and ergonomics issue with limited blast radius, not a crash, data loss, or security problem.
• impact:other: If valid, the issue affects dashboard scanability and operator UX, which is maintainer-visible but outside the specific owned impact classes.

Evidence reviewed

What I checked:

• Live issue state and prior review: The live issue is still open, has no maintainer-authored resolution, and the latest ClawSweeper review also kept it open because the reported UI is absent from current main.
• Reported identifiers absent: A current-source search for the reported panel names and cited classes found no matching ClawHub Overview log-panel implementation; hits were unrelated settings, management, catalog, docs, Monaco overview CSS, and backend event-log tests. (3ef5f14d84a7)
• No runtime overview route: The generated route tree includes /management and /dashboard, but no /overview route matching the report. (src/routeTree.gen.ts:93, 3ef5f14d84a7)
• Current dashboard surface: The /dashboard route renders Skills and Plugins collection blocks, not Event Log or Gateway Log cards. (src/routes/dashboard.tsx:240, 3ef5f14d84a7)
• Only Overview surface found: The only in-app Overview view found is a management placeholder that points staff to focused queues; it does not contain log panels. (src/routes/management.tsx:682, 3ef5f14d84a7)
• Repository scope: README describes ClawHub as a public skill registry and OpenClaw package catalog, not the runtime dashboard surface described by the issue. (README.md:15, 3ef5f14d84a7)

Likely related people:

• Patrick Erichsen: Blame ties the current /dashboard route, management Overview placeholder, and dashboard/management CSS blocks to the v0.23.0 baseline commit. (role: current dashboard and management surface contributor; confidence: high; commits: a128c101adca; files: src/routes/dashboard.tsx, src/routes/management.tsx, src/styles.css)
• Vyctor H. Brzezowski: Recent main commits and shortlog show substantial nearby UI/style work in src/styles.css, making this a plausible routing candidate if maintainers decide the report maps to ClawHub UI. (role: recent adjacent UI contributor; confidence: medium; commits: 3ef5f14d84a7, 40e345f4a990, 82197de7e1da; files: src/styles.css)
• DB Hurley: History search shows the earlier user dashboard feature commit in the dashboard lineage, though current-file blame is dominated by the later baseline graft. (role: earlier dashboard feature introducer; confidence: low; commits: d4b947af4719; files: src/routes/dashboard.tsx)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve.

Keep open. The report is concrete, but current ClawHub main does not contain the reported Overview Event Log/Gateway Log UI, the cited ov-event-log/ov-log-tail classes, or an /overview route; under the ClawHub cleanup policy, issues should stay open for maintainer triage rather than be auto-closed.

Required change / next step:

This is not a safe automated fix candidate because the reported Event Log/Gateway Log surface is absent from current ClawHub main; maintainers need to identify or transfer the owning UI before code changes are possible.

Review details

Best possible solution:

Maintain this as a triage item until maintainers identify the owning Overview UI surface. If it belongs outside ClawHub, transfer or recreate the report there with screenshot/DOM details; if ClawHub should own it, add or locate the route/component first, then implement equal-height paired cards with an internal scroll area for the longer log.

Acceptance criteria:

• After the owning UI is identified, verify in a browser with uneven Event Log/Gateway Log row counts that both cards share bounds and the longer panel scrolls internally.
• If ClawHub files are changed, run bun run format:check, bun run lint, and bun run test.

What I checked:

• Reported UI identifiers absent: Exact searches for ov-event-log, ov-log-tail, Event Log, Gateway Log, log-tail, and related card class prefixes returned no matches in ClawHub source/docs after excluding unrelated seed content. (7bef2a0b65d4)
• No runtime Overview route: The generated route tree includes /dashboard, management, package, plugin, skill, settings, and profile routes, but no /overview route matching the reported page. (src/routeTree.gen.ts:190, 7bef2a0b65d4)
• Dashboard is inventory UI: The current /dashboard route renders published Skills and Plugins inventory panels with rows/actions; it does not render Event Log or Gateway Log cards. (src/routes/dashboard.tsx:119, 7bef2a0b65d4)
• Dashboard styles are unrelated: The dashboard CSS block defines dashboard-* owner grid, collection, list, row, and status styles, with no reported ov-* log panel classes. (src/styles.css:5363, 7bef2a0b65d4)
• Tests cover inventory rows only: The dashboard tests exercise skills/plugins rows, summaries, statuses, empty/loading states, and action menus; there are no Overview log fixtures or layout assertions for Event Log/Gateway Log panels. (src/routes/dashboard.test.tsx:223, 7bef2a0b65d4)
• Repository scope points to registry/catalog: README describes ClawHub as a public skill registry and OpenClaw package catalog, not the runtime dashboard surface described by the issue. (README.md:13, 7bef2a0b65d4)

Likely related people:

• Patrick Erichsen: Current blame and recent history for src/routes/dashboard.tsx, dashboard tests, and owner security/rescan surfaces point to Patrick's dashboard inventory work. (role: recent maintainer and current dashboard route owner; confidence: high; commits: ecf09b868a98, a28d94c34573, ef2846b2e4c7; files: src/routes/dashboard.tsx, src/routes/dashboard.test.tsx, src/components/skeletons/DashboardSkeleton.tsx)
• Val Alexander: Blame for the current dashboard CSS block and shortlog across the dashboard/style files show substantial recent UI/style ownership, including the current main commit. (role: adjacent public UI and dashboard CSS maintainer; confidence: medium; commits: 11a20f575528, 22bb94cee27f, 7bef2a0b65d4; files: src/styles.css, src/routes/dashboard.tsx)
• Peter Steinberger: The grafted v0.11.0 baseline introduced the README/VISION scope text, route tree, dashboard route, and styles that define this checkout's current ClawHub surface. (role: baseline ClawHub introducer and repo-boundary routing candidate; confidence: medium; commits: 8752e4bb7e92; files: README.md, VISION.md, src/routeTree.gen.ts)

Remaining risk / open question:

• The reported UI may belong to another OpenClaw runtime/dashboard repository or an older local demo build, but the issue does not include a screenshot, route path, DOM excerpt beyond class names, or repository pointer to transfer confidently.
• If ClawHub is expected to own this Overview page in the future, the relevant route/component is currently missing, so a narrow fix cannot be scoped from current main alone.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 7bef2a0b65d4.