Cron "New Job" form misaligns the Description field after interacting with Agent ID

[abhshabvz782-jpg]

Summary

On the dashboard Cron "New Job" form, interacting with the Agent ID field causes the adjacent Description field to become visibly misaligned in the Basics section layout.

Steps to reproduce

1. Start the dashboard from the current openclaw source checkout.
2. Open the Cron page.
3. Click New Job.
4. In the Basics section, focus or type in the Agent ID field.
5. Observe that the Description input shifts out of alignment relative to the other fields in the same form grid.

Expected behavior

The Basics section layout stays aligned before and after interacting with Agent ID; the Description field should keep the same row/baseline alignment as the surrounding fields.

Actual behavior

After interacting with Agent ID, the Description field becomes misaligned and the form grid looks visually broken.

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 dashboard layout issue in the Cron "New Job" form.
Affected UI area is the Basics section containing fields such as Name, Description, and Agent ID.
No crash or gateway error log was required to reproduce the issue.

Impact and severity

• Affected: Dashboard users creating or editing cron jobs
• Severity: Medium
• Frequency: Reproduced on every observed interaction with Agent ID
• Consequence: The Cron editor looks broken and reduces usability/confidence when configuring jobs

Additional information

NOT_ENOUGH_INFO

This issue was reproduced locally during UI customization work and has already been fixed in a private/demo workspace, so no current screenshot is attached.

[abhshabvz782-jpg]

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:57 PM ET / 23:57 UTC.

Summary
Keep open for maintainer routing: current main and the latest v0.23.0 release do not contain the reported Cron/New Job dashboard form, Agent ID field, or Basics section, so this cannot be closed as implemented.

Reproducibility: no. Current-main route inventory and targeted source searches show no Cron New Job route, Agent ID field, Basics section, or matching frontend form to exercise.

Ways to help us reproduce this

• Add expected vs actual behavior.
• Include redacted logs or terminal output.
• Share version, platform, channel/provider, and relevant config details.

Next step
Manual routing is needed because current main lacks the affected UI and maintainers must first identify the owning repo, branch, or future cron-template product surface.

Review details

Best possible solution:

Maintainers should identify the owning route, repository, branch, and build for the Cron New Job editor, then fix that form-grid alignment and add a focused regression around Agent ID focus/input.

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

No. Current-main route inventory and targeted source searches show no Cron New Job route, Agent ID field, Basics section, or matching frontend form to exercise.

Is this the best way to solve the issue?

Unclear. The narrow fix should be a frontend form-grid alignment repair in the owning UI, but current ClawHub main lacks that UI and adding a cron editor here would be separate product work.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The reporter says the fix exists only in a private/demo workspace and did not attach a screenshot or source path, so the affected UI may belong to another repository, branch, or build.
• The adjacent cron-template request at Feature request: Shareable cron job templates #86 is product work and should not be treated as a canonical fix for this visual layout report.

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

Label changes

Label changes:

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

Label justifications:

• P3: This is a visual form-alignment usability report with no evidence of data loss, security impact, broken automation, or availability failure.
• impact:other: The issue concerns a user-visible dashboard layout defect outside the owned security, state, delivery, auth, and availability impact classes.

Evidence reviewed

What I checked:

• Live issue context: The issue reports a visual layout bug in an OpenClaw Cron New Job form and says the only known fix was in a private/demo workspace, with no screenshot or source path attached. (3ef5f14d84a7)
• Dashboard source lacks the reported form: The current dashboard queries publishers, skills, and packages and renders Skills/Plugins panels with New Skill/New Plugin actions rather than any Cron New Job form. (src/routes/dashboard.tsx:128, 3ef5f14d84a7)
• Route inventory has no cron editor: The generated TanStack route tree includes /dashboard and publish/package/plugin routes, but no cron, jobs, automation editor, or New Job route matching the report. (src/routeTree.gen.ts:103, 3ef5f14d84a7)
• Targeted source search found no matching UI: Exact searches for Agent ID, agentId, New Job, Cron Jobs, Basics, and job form found no matching frontend form in current main. (3ef5f14d84a7)
• Backend cron surface is internal scheduling: The only cron implementation found registers Convex maintenance schedules; it is not a user-facing dashboard editor for creating cron jobs. (convex/crons.ts:7, 3ef5f14d84a7)
• Latest release also lacks the reported route text: v0.23.0 points at a128c10 and current checks against that tag found no Cron/New Job/Agent ID/Basics text in the dashboard or route tree. (a128c101adca)

Likely related people:

• Patrick-Erichsen: Current blame attributes the dashboard route, generated route inventory, dashboard styling, and Convex cron baseline to Patrick's v0.23.0 release commit, even though the reported Cron form is absent. (role: recent adjacent dashboard and cron contributor; confidence: medium; commits: a128c101adca; files: src/routes/dashboard.tsx, src/routeTree.gen.ts, src/styles.css)
• Vyctor H. Brzezowski: Recent current-main history shows multiple frontend and style commits, including the current HEAD, so this is useful routing context if maintainers later locate the form as a ClawHub UI layout issue. (role: recent adjacent frontend layout contributor; confidence: low; commits: 3ef5f14d84a7, 40e345f4a990, 2bf8113ef13b; files: src/styles.css, src/routes/skills/publish.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. ClawHub cleanup policy only permits auto-closing PRs that are certainly implemented on current main, and current main does not contain the reported Cron/New Job dashboard form to verify or mark as fixed. The evidence points to an absent private/demo UI or future cron-template feature area rather than an implemented ClawHub bug fix.

Required change / next step:

Manual triage is needed because the reported form is absent from current main and may belong to another OpenClaw branch/repo or a future cron-template feature rather than a fixable ClawHub surface today.

Review details

Best possible solution:

Maintainers should identify the owning route, repository, branch, and build for the Cron New Job editor, then fix that form's grid alignment and add a focused regression that focuses or types in Agent ID while verifying Description remains aligned. If ClawHub later adds cron/template editing under #86, that new UI should include the same regression from the start.

Acceptance criteria:

• If the form is identified or added in ClawHub, run bun run lint.
• If the form is identified or added in ClawHub, run bun run test.
• Add or run a focused frontend regression that focuses or types in Agent ID and verifies Description remains aligned.

What I checked:

• Current checkout: Reviewed current main at 7bef2a0 with a clean worktree before and after read-only inspection. (7bef2a0b65d4)
• Route inventory has no cron editor: The generated TanStack route inventory lists dashboard, publish, management, packages, plugins, skills, souls, settings, and security routes, but no cron/jobs/automation route matching the reported New Job form. (src/routeTree.gen.ts:190, 7bef2a0b65d4)
• Dashboard surface is skills/plugins inventory: The dashboard renders Skills and Plugins panels with New Skill and New Plugin actions; it does not render a Cron New Job form, Agent ID field, Description input, or Basics grid. (src/routes/dashboard.tsx:226, 7bef2a0b65d4)
• Dashboard data model has no job fields: The dashboard queries user publishers, skills, and packages; no job, cron, agent, or automation form data is present in the current component state/query surface. (src/routes/dashboard.tsx:123, 7bef2a0b65d4)
• Targeted search found no frontend match: Searches for Agent ID, agentId, New Job, Cron Jobs, Basics, scheduled jobs, job form, Automation, and related terms found no matching frontend form; file discovery also found no src cron/job/automation route files. (7bef2a0b65d4)
• Backend cron surface is internal scheduling: The Convex cron file registers internal maintenance, leaderboard, scan, stats, and pruning schedules; it is not a user-facing Cron New Job editor. (convex/crons.ts:4, 7bef2a0b65d4)

Likely related people:

• Patrick Erichsen: Current dashboard component, generated route inventory, dashboard tests, and current Convex cron file blame to the recent merge and dashboard/security-surface work by Patrick; this is the closest current-main ownership even though the reported Cron form is absent. (role: recent maintainer / adjacent dashboard and route owner; confidence: medium; commits: ecf09b868a98, fb3bcbafb1d6, ef2846b2e4c7; files: src/routes/dashboard.tsx, src/routes/dashboard.test.tsx, src/routeTree.gen.ts)
• Val Alexander: The report is visual layout-related, and recent style history plus blame on dashboard list styling points to Val for adjacent current-main frontend layout work if maintainers later locate this form in ClawHub UI. (role: recent frontend styling maintainer / adjacent UI owner; confidence: low; commits: 7bef2a0b65d4, 22bb94cee27f, 11a20f575528; files: src/styles.css)
• Luke: The earliest visible local history for several inspected dashboard, route tree, and backend cron files appears in Luke's broad import/refactor commit; the exact Cron editor is absent, so this is weak routing context only. (role: historical importer of adjacent current-main surfaces; confidence: low; commits: cf137aa59200; files: src/routes/dashboard.tsx, src/routeTree.gen.ts, convex/crons.ts)

Remaining risk / open question:

• The reporter says the bug was fixed in a private/demo workspace and provided no screenshot, so the affected Cron New Job UI may belong to another repository, branch, or build rather than current ClawHub main.

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