← All updates

Task decisions, runtime values, and steadier previews

Choose an answer inside the task, reuse task-specific values in environment settings, and open previews only after the application is ready.

Answer choices and confirmations inside the task

Rubic can pause during planning, development, or chat to ask for one or more choices, a confirmation, or a custom answer. The response stays attached to the task, and the work resumes from the same point.

Use task-aware runtime values

  • Reference the task ID and preview URL in Runtime Env, preview commands, and environment files.
  • Pass the same values to the application and connected services without hardcoding task-specific URLs.
  • See the supported placeholders while configuring a repository.

Wait for the application before marking a preview live

Rubic now checks that the preview command has started successfully and that the application is listening on the configured port before showing the preview as ready.

Get clearer help when something goes wrong

Server errors now keep a support code and request reference visible in the dashboard. Detail pages also stop failed live update attempts cleanly instead of leaving repeated connection warnings.