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

# Create and Run a Shift

> Define your first Fleetshift agent shift and run it against target repositories.

Once you have [connected GitHub events](/docs/portal/core-features-and-plugins/fleetshift/getting-started)
and [enabled AI shifts](/docs/portal/core-features-and-plugins/fleetshift/enable-ai-shifts),
you're ready to create and run your first shift.

## Create a shift

1. Go to `Fleetshift` in the sidebar.
2. Click `New Shift` and select `Agent`.
3. Fill in the shift details:

| Field       | Example                                                               |
| ----------- | --------------------------------------------------------------------- |
| Name        | `add-readme`                                                          |
| Prompt      | `Add a README.md with a project description based on the code.`       |
| PR settings | Branch name, pull request title, and pull request description.        |
| Targets     | The catalog entities or repositories that the agent should transform. |

4. Click `Create`.

## Run the shift

1. Open your shift.
2. Go to the `Targets` tab.
3. Select one or more targets.
4. Click `Run`.

You can monitor progress in real time from the `Logs` tab on each target. Once the job
completes, review the generated changes in the `Diff` tab and click `Create PR` to open
a pull request for your team to review.

## Next steps

See the [Fleetshift Guides](/docs/portal/core-features-and-plugins/fleetshift/guides) for
walkthroughs of more advanced workflows, including fixing Soundcheck failures, running
campaign-level bulk fixes, and using MCP actions with AiKA.