> For the complete documentation index, see [llms.txt](https://vibemx.gitbook.io/neuronai-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vibemx.gitbook.io/neuronai-studio/reference/publish-tags.md).

# Publish Tags

Laravel publish tags for vendor assets, config, and migrations.

## Tags

| Tag                          | Destination                                | When to use                                             |
| ---------------------------- | ------------------------------------------ | ------------------------------------------------------- |
| `neuron-config`              | `config/neuron.php`                        | Provider credentials (API keys, embeddings, stores)     |
| `neuronai-studio-config`     | `config/neuronai-studio.php`               | Customize studio configuration                          |
| `neuronai-studio-migrations` | `database/migrations/`                     | Modify migrations (optional — auto-loaded from package) |
| `neuronai-studio-views`      | `resources/views/vendor/neuronai-studio/`  | Override Blade templates                                |
| `neuronai-studio-lang`       | `lang/vendor/neuronai-studio/`             | Override Studio UI translations (`en`, `pt_BR`)         |
| `neuronai-studio-assets`     | `public/vendor/neuronai-studio/`           | Publish JS/CSS bundles                                  |
| `neuronai-studio-evaluation` | `evaluation.php`                           | Evaluation config stub                                  |
| `neuronai-studio-evaluator`  | `app/Evaluators/ExampleAgentEvaluator.php` | Example evaluator stub                                  |

## Commands

```bash
# Provider credentials
php artisan vendor:publish --tag=neuron-config

# Config
php artisan vendor:publish --tag=neuronai-studio-config

# Migrations (optional)
php artisan vendor:publish --tag=neuronai-studio-migrations

# Views (only when customizing)
php artisan vendor:publish --tag=neuronai-studio-views

# Translations (optional — override en / pt_BR catalogs)
php artisan vendor:publish --tag=neuronai-studio-lang

# Assets (required for UI)
php artisan vendor:publish --tag=neuronai-studio-assets --force
```

## Auto-loaded without publish

These load from the package automatically:

* Migrations via `loadMigrationsFrom()`
* Routes via `loadRoutesFrom()`
* Default views via `loadViewsFrom()`
* Translations via `loadTranslationsFrom()` (namespace `neuronai-studio`; locale follows the host app, or `NEURONAI_STUDIO_LOCALE` / `neuronai-studio.locale` when set)

## Asset rebuild workflow

After editing frontend source in the package:

```bash
npm install
npm run build
php artisan vendor:publish --tag=neuronai-studio-assets --force
```

## View override warning

If you published views and the UI looks outdated after a package update:

```bash
rm -rf resources/views/vendor/neuronai-studio
php artisan view:clear
```

Blade views load from the package by default — only publish views when you need to customize templates.

## See also

* [Installation](/neuronai-studio/getting-started/installation.md)
* [Frontend Bundles](/neuronai-studio/reference/frontend-bundles.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://vibemx.gitbook.io/neuronai-studio/reference/publish-tags.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.