Edit existing HTML instead of regenerating from scratch

Open
#77 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
ai, frontend

Research direction

Start by reproducing the follow-up edit workflow with the linked 3d-plane-pitch-roll-and-yaw.html file and compare the original with the regenerated result. Done means applying only the requested change while preserving the existing HTML structure and prior customizations.

Written by the indexing model from the issue text.

Description

Problem

When editing HTML code in a follow-up message, the agent regenerates the entire file from scratch instead of editing the existing content in place.

Expected Behavior

The agent should apply targeted edits to the existing HTML, preserving the original structure and only modifying the relevant parts.

Steps to Reproduce

  1. Generate an HTML file (e.g., 3d-plane-pitch-roll-and-yaw.html)
  2. Send a follow-up message requesting a change to the generated HTML
  3. Observe that the agent regenerates the entire file instead of editing the existing one

Impact

  • Slower response times due to full regeneration
  • Risk of losing prior customizations or context
  • Poor user experience for iterative editing workflows
Dominant language
TypeScript
Stars
1.6k
Forks
202
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CopilotKit/OpenGenerativeUI

All issues in CopilotKit/OpenGenerativeUI

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.