[bug] AI response cancels on its own #2605
Description
I have imported an Onlook desktop created project into Onlook web, and was able to do a few things using the chat interface (update page themes, and start work on pulling an API), but eventually, the responses started to cancel themselves, leaving only my initial request in the chat. Some times, this even broke things in the site because the AI canceled making changes and left things unfinished.
This has cost me at least 50 chat credits in asking it to fix what it started.
I even tried to ask the AI to track the progress it was making so it could catch up with the work it left half completed, but it still starts a response, makes a few changes, and then stops eventually. Leaving me with only my initial prompt in the chat, back at square 1, asking it to fix it's mistakes, and tell it where to look, and how to find them.
I also mentioned this bug here: #2570 (comment)
In my opinion, if Onlook starts a project, change, feature, etc., it should be able to run npm run build after the initial changes are complete. Otherwise, that change should be considered incomplete.
One of the changes added to the project in question actually helps Onlook validate that any change it makes did not break anything. The plan was to run this after a group of steps to make a change or add a feature is complete. It has worked for other projects, so I thought I should share it here.
run-build.js
const { spawn } = require("child_process");
const fs = require("fs");
const build = spawn("bun", ["run", "build"], {
stdio: ["inherit", "pipe", "pipe"]
});
let output = "";
let errorOutput = "";
build.stdout.on("data", (data) => {
const text = data.toString();
console.log(text);
output += text;
});
build.stderr.on("data", (data) => {
const text = data.toString();
console.error(text);
errorOutput += text;
});
build.on("close", (code) => {
const fullOutput = output + errorOutput;
fs.writeFileSync("./build.log", fullOutput);
console.log(`Build process exited with code ${code}`);
console.log("Output written to build.log");
});