# Quick start

{% hint style="info" %}
Frontitude's Developer CLI can be installed and tested on our [Starter plan](https://www.frontitude.com/pricing), which is completely free!
{% endhint %}

## Step 1: Get content into Frontitude

There are two ways to get content into Frontitude to work with.

**Pull-first (design-led):** create content in Frontitude first, then pull it into your codebase.

* [Import content from JSON files](https://www.frontitude.com/guides/import-copy-components-from-json-files)
* [Import content from design tools](https://www.frontitude.com/guides/upload-content-to-frontitude)
* Manually create [copy components](https://www.frontitude.com/guides/copy-components) in the copy library

**Push-first (code-led):** write new copy components directly in your codebase and push them up to your Frontitude copy library. Great for AI-assisted development where a coding assistant generates new UI strings inline with your code. See [Step 6](#step-6-push-new-keys-from-your-code) below.

## Step 2: Install the Developer CLI

Install the Developer CLI globally via NPM or Yarn:

{% tabs %}
{% tab title="NPM" %}

```bash
npm install -g @frontitude/cli
```

{% endtab %}

{% tab title="Yarn" %}

```bash
yarn global add @frontitude/cli
```

{% endtab %}
{% endtabs %}

## Step 3: Get access to Frontitude

{% hint style="warning" %}
Make sure the Developer CLI integration is turned on in your [workspace settings](https://app.frontitude.com/settings/integrations).
{% endhint %}

### Use an access token

[Create an access token](/developer-cli/authentication.md#workspace-level-access-token) to use it in the next step. This is more flexible since it allows you to use the Developer CLI on remote systems such as CI/CD pipelines or any kind of Bash scripts.

## Step 4: Initialize the Developer CLI

To initialize the CLI, run the next command and follow the instructions:

```bash
$ frontitude init
```

## Step 5: Pull content from Frontitude

To pull the latest content from your connected sources:

```bash
$ frontitude pull
```

This will fetch all of your content from the library/project into your codebase. To learn about the additional options of this command, please refer to [this section](/developer-cli/commands.md#pull).

## Step 6: Push new keys from your code

If you've added new strings to your codebase (for example, because you built a new feature), you can push those keys up to Frontitude in one command:

```bash
$ frontitude push
```

The CLI will show you a preview of what would be created and ask for confirmation. Only components with new unique keys are created; anything that already exists in Frontitude is left untouched.

To see what would be pushed without making any changes:

```bash
$ frontitude push --dry-run
```

See the [full push options](/developer-cli/commands.md#push) for tagging, messaging, and CI usage.

## That's it!

You now have the full round-trip: pull content from Frontitude into your codebase, and push new keys from your codebase back to Frontitude. Happy coding!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.frontitude.com/quick-start.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.