Getting StartedSolveBuildIntelligenceLearnHelpWhat's New
PROJECTContext

Overview

Understand how project context in Rocket.new shares files, connected services, and prior findings between Solve research and Build tasks.

Context is the information Rocket has access to when working on a task. Inside a project, that context is shared. Every task can draw on the same files, connected documents, and outputs from earlier tasks without re-uploading or re-explaining anything.

The more relevant work you do inside a project, the richer the shared foundation becomes.

Context is scoped to a project. Tasks in different projects do not share context with each other.

What counts as context

Context typeWhat it includes
My Device.md, .pdf, .xlsx, .csv, .jpg, .jpeg, .png
Google DriveGoogle Docs, Google Sheets
NotionNotion pages (.md)
Task outputsFindings, decisions, and outputs from earlier Solve and Build tasks
Chat historyClarifications and refinements from any task's conversation

How context flows between tasks

Once you have multiple tasks in a project, their outputs become context for each other. A few common patterns:

What happens
Solve then BuildResearch findings shape what gets built, including features, positioning, and design
Build then SolveDevelopment reveals new questions that trigger deeper research
Solve then SolveLater research builds on earlier findings without duplicating work
Build then BuildBranding and technical decisions carry forward into new tasks

Standalone tasks vs project tasks

You don't need a project to use Rocket. Standalone tasks work fine for one-off questions and quick builds. The difference is context.

Standalone taskTask in a project
Works on its ownYesYes
Accesses shared filesNoYes
Benefits from other tasks' outputsNoYes
Uses connected servicesNoYes

If you start with a standalone task and later want shared context, you can add it to a project at any time without losing any history.

Tips

  • Upload files early. Add brand guidelines, product specs, or reference docs when you create the project so every task starts with the right foundation.
  • Be specific in prompts. Even with shared context available, explicit references get better results: "Based on the competitive analysis from earlier, build a landing page that emphasizes our differentiators."
  • Keep related work together. The more relevant tasks you group in one project, the richer the shared context becomes.

What's next?

On this page