# Develop your integration

After [bootstrapping your integration with the GitBook CLI](/docs/developers/integrations/quickstart.md#bootstrap-your-app), you can continue using the CLI to develop and test your app.

{% stepper %}
{% step %}

#### Publish your integration

Before you're able to develop your integration, you will first need to publish it. You can do this by running the following command in the root directory for your integration:

```bash
gitbook publish
```

By default (defined in the CLI-generated `gitbook-manifest.yaml`), your integration will be published privately, and owned by the organization specified in the manifest.

After publishing your integration, the CLI will give you a link to install your integration into the organization you’ve set.

You need to install your app into at least 1 space or site in order to develop it locally.
{% endstep %}

{% step %}

#### Start your integration’s development server

While inside the root directory of your integration, run:

```bash
gitbook dev
```

This will start a development server tied to your organization.

{% hint style="info" %}
Running this command will start a development server for use by the integration only. **You do not need to navigate to the port the server is running on.**\
\
All integration traffic will automatically be served from your local server instead of the published version.
{% endhint %}
{% endstep %}

{% step %}

#### Develop your integration

It's recommended that you [disable browser caching](https://stackoverflow.com/a/7000899) for the most optimal experience when developing your app.

Any logs sent to the console or made through your integration's `RuntimeContext` will be surfaced in your browser's console.

{% hint style="warning" %}
Any UI changes made to your integration will need a browser refresh in order to be visible.
{% endhint %}
{% endstep %}
{% endstepper %}

### FAQ

<details>

<summary>Why don't I see any logs in my console?</summary>

Depending on where your console log is run in your integration, you may see it in your machine's console or your browser's console. Please check both to ensure your logs are working correctly.

</details>

<details>

<summary>I'm getting an error when visiting the URL listed in the console.</summary>

The URL provided in the console is used as a server for your integration. You do not need to visit this URL.

Instead, visit the GitBook space you provided in the dev command when starting your development server (i.e. `app.gitbook.com/o/org_id/s/space_id`).

</details>


---

# 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://gitbook.com/docs/developers/integrations/development.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.