> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Share context, files, and collaborators across tasks in a Rocket.new project.

export const LlmsDirective = () => <blockquote className="llms-directive">
    For the complete documentation index, see <a href="/llms.txt">llms.txt</a>.
    For a lightweight markdown version of this page, append .md to the URL.
  </blockquote>;

<LlmsDirective />

A project is a space in Rocket where all related work lives together. Every Solve task and Build task you create inside a project automatically shares the same files, connected services, and team members. It acts as a knowledge container for an initiative, whether that is launching a product, redesigning a website, or exploring a market.

The practical benefit is that you front-load your context once. Upload your company overview, financial model, or strategy deck when you create the project, and every task inside it has that foundation from the start. No re-uploading, no re-explaining.

<Info>
  **Intelligence is separate from projects.** Monitoring and the Intelligence dashboard live outside of projects entirely. They operate at the platform level, not scoped to any single project. You can still use Intelligence insights to inform what you Solve or Build. They are managed from the Intelligence panel.
</Info>

## What's inside a project

<CardGroup cols={2}>
  <Card title="Tasks" icon="bullseye-arrow">
    Solve and Build tasks that represent the actual work. A project can hold any number of tasks, and each task has its own chat history, outputs, and conversation.
  </Card>

  <Card title="Context" icon="arrows-repeat">
    Files from your device, connected documents, and Notion pages that inform your tasks. See [Context](/getting-started/project/context/overview).
  </Card>

  <Card title="Collaborators" icon="users">
    Team members who can view, edit, or comment on the project and its tasks.
  </Card>

  <Card title="Solve & Build" icon="rocket">
    Two task types available inside a project. Solve for strategic research, Build for app creation.
  </Card>
</CardGroup>

## When to use a project

| Scenario                                    | Use a project                                 | Use a standalone task                                             |
| :------------------------------------------ | :-------------------------------------------- | :---------------------------------------------------------------- |
| Building a product with research and an app | Yes, group the Solve and Build tasks together |                                                                   |
| Quick one-off question about a market       |                                               | Yes, create a Solve task directly                                 |
| Team working on a website redesign          | Yes, shared context and collaboration         |                                                                   |
| Testing a single app idea solo              | Either works; a project adds organization     | Either works; standalone is faster to start                       |
| Ongoing monitoring of a competitor          |                                               | No project needed. Intelligence is managed at the workspace level |

<Note>
  You can always add a standalone task to a project later. There's no penalty for starting simple.
</Note>

## The project lifecycle

<Steps>
  <Step title="Create">
    Start a new project from the home screen. Give it a name that describes the initiative.
  </Step>

  <Step title="Add tasks">
    Create Solve and Build tasks inside the project. Each task gets its own conversation, but they all share the project's files and connected services.
  </Step>

  <Step title="Collaborate">
    Invite team members to the project. Everyone works in the same shared space with access to all tasks, files, and context.
  </Step>

  <Step title="Iterate">
    Keep adding tasks, uploading files, and refining outputs. Context flows between tasks within the project, so later work benefits from earlier research.
  </Step>
</Steps>

<Card icon="pen-to-square" href="/getting-started/project/manage" horizontal arrow="true">
  **Create, rename, archive, and delete projects.** Step-by-step instructions.
</Card>

## How context flows

Grouping tasks in a project means shared context. Files uploaded to the project are available to every task automatically. No re-uploading or re-referencing required.

When you run a Solve task to research a market and then start a Build task in the same project, Rocket can use the research findings to inform the build if you use [cross-task context](/getting-started/task/task-context). Connected services provide live data across the board.

This works in both directions. A Build task's outputs can prompt new Solve questions, and Solve findings can shape what you build next.

<Info>
  Context flow is automatic within a project. You do not need to manually copy information between tasks. Rocket surfaces relevant context when it is useful.
</Info>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I have multiple projects at once?">
    Yes. There's no limit on the number of projects you can create. Most teams organize by initiative: one project per product, campaign, or research task.
  </Accordion>

  <Accordion title="Does Intelligence live inside projects?">
    No. Intelligence is a workspace-level dashboard entirely separate from projects. You run the Intelligence setup wizard once for your workspace, and the Intelligence panel in your sidebar manages all monitoring from that point.

    Currently, Solve or Build can not refer to Insights from Intelligence.
  </Accordion>

  <Accordion title="Can I move a task between projects?">
    Yes. You can add any standalone Solve or Build task to a project from the task's **...** menu. A task can only belong to one project at a time.
  </Accordion>

  <Accordion title="What happens when I archive a project?">
    Archived projects become read-only. All tasks, files, and history are preserved, but you can't create new tasks or make edits. You can unarchive a project at any time to resume work.
  </Accordion>

  <Accordion title="Is there a limit on tasks per project?">
    There's no hard limit on the number of tasks in a project. However, each task consumes credits based on your plan, so your total active work is governed by your subscription. See [Credits](/getting-started/credits) for details.
  </Accordion>
</AccordionGroup>

## What's next?

<CardGroup cols={2}>
  <Card title="Context" icon="arrows-repeat" href="/getting-started/project/context/overview">
    Learn how files, connected services, and task outputs create shared context.
  </Card>

  <Card title="Tasks" icon="bullseye-arrow" href="/getting-started/task/overview">
    Understand how Solve, Build, and Intelligence tasks work.
  </Card>
</CardGroup>