Review before applying
Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
A web interface is more than its first screen. Wavepilot is a workspace for moving through behavior, code and the next iteration of a browser-facing project.
const visible = tasks.filter(matchesFilter);
if (loading) return renderLoading();
return visible.length
? renderTasks(visible) : renderEmpty();Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
Base URL, credentials and a reachable server.
Describe loading, empty and error states as part of the same interface change.
const visible = tasks.filter(matchesFilter);
if (loading) return renderLoading();
return visible.length
? renderTasks(visible) : renderEmpty();A task list can look finished while still leaving people guessing. During a request, is it loading or empty? When a filter hides every task, should the screen suggest clearing it? Use Wavepilot, a Windows coding workspace, to turn those questions into a focused change in your web application's files.
Begin with the component that displays tasks and the code that supplies its data. Ask your connected model to explain how loading and filtering interact before proposing edits. Specify separate messages for an empty collection and a filter with no matches, so the interface offers the right next action in each case.
Once those states are defined, review the proposed code for transitions as well as appearance. Check whether an older response can replace newer filter results, whether retrying preserves the selection, and where keyboard focus goes after clearing a filter. Keep each iteration small enough to inspect against the behavior you requested.
Run the project's relevant tests and exercise the changed screen in your browser, including a slow response and repeated filter changes. Model choice remains separate from that verification: a model described as uncensored may be connected through a supported endpoint, but its provider determines restrictions, context limits and tool support. Generated UI code still needs your review.
Name the component, describe whether tasks are missing or merely filtered out, and state what the user should do next. Include the current loading behavior so the proposed change does not show an empty message before data arrives.
You need to run the application and check the screen yourself. Review proposed edits, run relevant project tests, and try slow loading, no matches and repeated clicks; a code suggestion alone does not verify the rendered result.
The term describes your selected model, not a built-in guarantee. Configure a supported OpenAI-compatible or Anthropic endpoint with credentials when required. The model and server determine available tools, context and restrictions.
A local endpoint requires a separately running model server and covers that connection only. Other connected tools or services may still send data elsewhere. Check those connections before sharing project context.
Wavepilot · Updated 2026-10-25