Before a successful Build deploys, there is no running Preview to test.
Preview Your Project
Preview is the running result of an accepted Build. Use it to test the product, inspect real elements, and send feedback back to Chat before you publish.
The Preview tab is for using the build, not watching progress. Build progress, understanding, and node states stay in Chat and the Graph; Preview shows the deployed result once it is ready. Before a Preview is deployed, Castaly runs automated tests and attempts to repair implementation issues when it can.
When Preview becomes useful
Section titled “When Preview becomes useful”After you accept a Build Plan, Castaly implements the work, runs automated tests, repairs issues when possible, and then deploys the running version.
When the Project reaches Preview ready, open the tab and use the Project like a real user would.
If the preview link expires, Resume restores the same build’s Preview without rebuilding.
Test the running Preview
Section titled “Test the running Preview”Test the Preview like someone using the product for the first time. Focus on the path you expect to publish, not only the page that changed.
- Key pages load without obvious errors or empty states.
- Primary flows work from start to finish.
- Content and layout match your intent from the Spec and Graph.
- Features behave as expected in the running app, not only in the plan.
- Runtime-dependent features may need secrets before they fully work.
If something does not match the Project definition, send feedback in Chat before publishing.
Send element-level feedback
Section titled “Send element-level feedback”When a Preview is live, the Preview toolbar shows Inspect. Use it to attach feedback to a specific element instead of describing it from memory.
Turn on Inspect
Click Inspect in the Preview toolbar. Click it again to turn it off.
Pick an element
Click any element in the running preview. Castaly captures what it is — text, label, role, and where it sits — and opens a short feedback note next to your selection.
Write a note
Add a note describing the change you want. A note is required; an empty note won’t create feedback.
Review the feedback chip
Your feedback shows up as a chip above the Chat composer, pinned to that element. You can remove it before sending.
Send from Chat
Inspect feedback never sends itself. Add as many notes as you need, then send them with your next Chat message.
Inspect only collects feedback. It doesn’t change the preview, edit the Spec, or send anything on its own.
What happens after you send feedback
Section titled “What happens after you send feedback”Feedback from Preview becomes part of the next Chat request.
Castaly reads the element context
It uses the selected element, captured details, and your note to understand exactly what part of the Preview you mean.
It combines context with your instruction
The element points to the location. Your message explains the change you want.
It clarifies if needed
If the feedback changes a product decision, Castaly asks before updating the Project definition.
It updates the definition or prepares the next action
Castaly may update the Spec and Graph, explain the issue, or prepare work for the next Build.
To apply Preview feedback to the running app, build again from the updated Spec.
Preview states
Section titled “Preview states”The tab tells you exactly where the preview stands.
No Build has deployed yet. Run Build to create a Preview.
A Build is running. Castaly implements the work, runs automated tests, attempts repairs when possible, and shows the deployed Preview once checks pass.
The Preview is live. Walk through it, test flows, and use Inspect for element-level feedback.
The preview link timed out. Use Resume to restore the same build’s Preview.
Castaly could not prepare the Preview. Retry the Preview action or follow the recovery shown in the workspace.
A required runtime secret is missing. Preview still opens, but the feature that needs that secret may not work, and Publish stays blocked until you add it.
When you see Configuration required, use Set up to open Project Settings at the runtime secrets section and add the missing key. See Runtime Secrets for setup details, or Resolve Blockers for the full blocker map.
Next: when the preview looks right, Publish Your Project.