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

# From my codebase

> Prompt an agent to write simpleuat-project-setup.json, upload it, preview, and apply. Paid on Pro+.

Use this when the source of truth is the repo (routes, features, env names) and you don't want to invent the tree in the wizard.

**Paid on Pro+.** If the option is missing, check [plans](/account/plans) and [missing feature](/troubleshooting/missing-feature) (flags/role).

<Steps>
  <Step title="Copy the prompt">
    From **From my codebase** in project setup. Give it to your coding agent in the real repo.
  </Step>

  <Step title="Get simpleuat-project-setup.json">
    The agent should produce that filename. Don't hand-edit YAML into a random shape and hope.
  </Step>

  <Step title="Upload">
    Back in SimpleUAT, upload the JSON.
  </Step>

  <Step title="Preview, then apply">
    Same discipline as Smart Import: read the preview. Apply creates project structure (suites/cases/environments as the file describes).
  </Step>
</Steps>

**Import history** lists past codebase setup uploads so you can retry without hunting Slack.

This is not live CI, not "the app reads GitHub every night," and not pack JSON. After apply, it's normal project content you maintain.

<Columns cols={2}>
  <Card title="Can I change it after?" icon="pencil" href="/setup/can-i-change-it">
    Yes. JSON is a starter.
  </Card>

  <Card title="Plans" icon="credit-card" href="/account/plans">
    Upgrade at /settings/billing.
  </Card>
</Columns>