OpenHands/agent-canvas

[Bug]: Missing text chat when Create Automation button is clicked in modal

Closed

#825 opened on May 27, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (26 forks)github user discovery
buggood first issue

Repository metrics

Stars
 (43 stars)
PR merge metrics
 (Avg merge 2d 10h) (106 merged PRs in 30d)

Description

Operating System

macOS

Installation Method

npm (npx @openhands/agent-canvas or npm install -g @openhands/agent-canvas)

Agent Canvas Version

latest

Bug Description

When the user clicks the Create Automation button in the Create Automation modal the user is navigated to the new conversation page. We are missing prefilled text "Create an automation" that should prefill the chat input field with the cursor on the right side of it.

Steps to Reproduce

  1. Go to Automate
  2. Click Create Automation
  3. Click Create Automation button
  4. User goes to new conversation but no text is prepopulated

Actual Behavior

When the user clicks the Create Automation button in the Create Automation modal the user is navigated to the new conversation page. We are missing prefilled text "Create an automation" that should prefill the chat input field with the cursor on the right side of it. Instead it is just blank.

Expected Behavior

We are missing prefilled text "Create an automation" that should prefill the chat input field with the cursor on the right side of it.

Relevant Logs

Screenshots

No response

Additional Context

No response

Contributor guide

Research direction
Examine the modal component for Create Automation and trace the navigation logic to ensure the chat input prefills with 'Create an automation'.
Tech stack
typescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75