NexusRBX
Workflow guide

Projects and continuity

Keep generated code, artifacts, Studio context, and follow-up work connected across NexusRBX project sessions.

Updated June 28, 20265 min read
Open AI workspaceTroubleshoot a project

Project state

A NexusRBX project should keep enough context to continue a build without forcing the creator to repeat every prompt. That includes generated artifacts, Studio pairing state, summaries, and safe retry information.

ArtifactsGenerated scripts, setup notes, image assets, validation output, and review summaries.
Studio contextManifest matches, target paths, source hashes, snapshot IDs, and structured Studio acknowledgments.
Handoff statePublic prompt intents and authenticated workspace state should survive auth or refresh interruptions when possible.

Handoff

A resilient continuation

  1. Capture the generation intent before navigation or authentication.
  2. Restore the intent in /ai after sign-in.
  3. Open the first-run workspace with the prompt still available.
  4. Save useful output as project artifacts so follow-up work can reference it.
Was this page helpful?