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

# Orbit AI Task Recipes: Step-by-Step Common Workflows

> Follow practical, step-by-step recipes for planning projects, explaining files, keeping work organized, reporting bugs, and approving device actions in Orbit AI.

Orbit AI Task Recipes are repeatable workflows for common jobs you can do in the app. Each recipe lists the steps, what to watch for, and where to go next. Pick the one that matches your goal and follow it from start to finish.

## Ask Orbit to plan a project

Use this recipe when you want a structured plan before building something.

<Steps>
  <Step title="Start a new chat">
    Open the app and start a fresh conversation so the context is clean.
  </Step>

  <Step title="Describe the project">
    State the target user, the problem, and the platform.
  </Step>

  <Step title="Ask for a plan with milestones">
    Request a short plan with milestones and risks before asking for implementation.
  </Step>

  <Step title="Review and correct">
    Review the plan and correct assumptions about budget, integrations, and data.
  </Step>

  <Step title="Work one milestone at a time">
    Ask for one milestone at a time and keep a record of decisions in the conversation or your own project notes.
  </Step>
</Steps>

<Note>
  For more on starting chats and managing context, see [Chat and History](/using/chat-and-history).
</Note>

## Ask Orbit to explain a file

Use this recipe when you want a summary, review, or extraction from a file.

<Steps>
  <Step title="Check the file for secrets">
    Confirm the file does not contain a secret or personal data you should not share.
  </Step>

  <Step title="Attach or excerpt the file">
    Attach it if the current composer supports the file type; otherwise provide a small, relevant excerpt.
  </Step>

  <Step title="State the desired output">
    Say whether you want a summary, explanation, review, or specific extraction.
  </Step>

  <Step title="Ask for evidence-based answers">
    Ask Orbit to distinguish direct evidence from guesses.
  </Step>

  <Step title="Verify the results">
    Verify extracted figures, quotations, and decisions against the original.
  </Step>
</Steps>

<Warning>
  Do not upload passwords, recovery phrases, private keys, or sensitive payment details. For attachment guidance, see [Chat and History](/using/chat-and-history).
</Warning>

## Keep work organized

Use this recipe to keep your Orbit workspace tidy and easy to navigate.

<Steps>
  <Step title="Use one conversation per task">
    Start a new conversation for each independent task so context stays focused.
  </Step>

  <Step title="Rename conversations">
    Give conversations descriptive titles using the rename control so you can find them later.
  </Step>

  <Step title="Use library filters and sort">
    Use the library filters and sort modes to find work quickly. See [Chat and History](/using/chat-and-history) for filter and sort options.
  </Step>

  <Step title="Separate team contexts">
    Use workspace selection to separate team contexts. See [Workspaces and Automations](/using/workspaces-and-automations) for workspace switching.
  </Step>

  <Step title="Save critical outputs externally">
    Save important outputs outside Orbit if they are business-critical or must be retained long term.
  </Step>
</Steps>

## Report a bug

Use this recipe when something in Orbit is not working as expected.

<Steps>
  <Step title="Gather context">
    Note the platform (browser, desktop, or mobile), the screen or route, and the approximate local time and time zone.
  </Step>

  <Step title="List steps to reproduce">
    Write the exact steps that lead to the issue.
  </Step>

  <Step title="State expected and actual results">
    Describe what you expected to happen and what actually happened.
  </Step>

  <Step title="Include a redacted error">
    Include a redacted error message if one is available.
  </Step>

  <Step title="Submit through Feedback">
    Use the Feedback section in Settings to send the report. Remove private account information, secret codes, and sensitive content from screenshots or pasted logs.
  </Step>
</Steps>

<Warning>
  Do not attach raw environment files, access tokens, account recovery links, payment details, or unredacted user data.
</Warning>

## Before granting a device action

Use this recipe whenever Orbit asks permission to perform an action on your device.

<Steps>
  <Step title="Read the requested action">
    Read the requested action and its target carefully.
  </Step>

  <Step title="Verify the destination">
    Verify the app, website, folder, filename, or destination is correct.
  </Step>

  <Step title="Cancel if unfamiliar">
    Cancel if the target is unfamiliar.
  </Step>

  <Step title="Inspect generated files">
    For any generated file, open or inspect the result before distributing it.
  </Step>
</Steps>

<Note>
  Desktop bridge actions may use Electron; mobile permissions are controlled by the OS. For platform differences, see [Desktop and Mobile](/using/desktop-and-mobile).
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.