Base module reference

The base layer (redelay/js-admin-nuxt4) ships these modules. Every project admin inherits all of them automatically — remove entries from the sidebar by overriding navigation, or disable a module by omitting its source (fork-and-trim).

AI modules

Three related framework modules surface in the admin:

• ai-llm — the provider registry. Reads every supported provider's credentials from env + admin settings and builds every provider that has credentials on Startup. Admin groups under /admin/settings/ai-llm: openai, anthropic, gemini, ovh, ollama, defaults. Each provider group has an api-key / base-url / default-model input that pre-populates with the current env value so operators can see what's wired up without digging through shell configs.
• ai-guard — builds a guard.Guard backend (Qwen3Guard-Gen on OVH is free) from GUARD_PROVIDER env + admin settings. The redelay/llm-guard FlowDSL router node consumes it.
• ledger — mounts /admin/llm/usage, /admin/llm/breakdowns, /admin/llm/pricing. The admin UI's System → AI section renders charts + an editable pricing table over this. Pricing updates take effect on the next LLM call — no restart.

Settings resolution — DB > ENV > YAML default

Every module ships a settings: block in its module.yaml. Each SettingField can declare an env_var: that names the environment variable used as a fallback when no admin-edited DB row exists. The settings.Service (in go-framework/modules/settings) resolves every read through three layers:

1. DB — explicit admin-edited value in the _settings MongoDB collection.
2. ENV — value of SettingField.EnvVar when set in the process environment.
3. Default — the YAML default: on the field.

The admin API's POST /admin/settings/get delegates to the service, so GET /admin/settings/schemas + POST /admin/settings/get together tell the admin UI both the schema AND the current effective value for every key — no blank fields for env-backed configuration on first boot. Writing a value goes through the same service, which also publishes a settings.updated event on the EventBus so peer workers invalidate their local resolver cache — no container restart needed for a cluster-wide refresh.

By default, the ENV fallback uses the convention {MODULE_ID}_{KEY} — both uppercased, with hyphens in the module id replaced by underscores. Only declare env_var: when you need a non-conventional name (legacy vars, third-party conventions):

settings:
  id: mymodule
  groups:
    - id: mymodule.defaults
      settings:
        - key: api_key
          label: API key
          type: string
          # No env_var — service reads MYMODULE_API_KEY automatically.
          default: ""
        - key: license_key
          label: Legacy license key
          type: string
          # Non-conventional name — declare explicitly.
          env_var: LEGACY_LICENSE_KEY
          default: ""

Worked examples from the tree:

No Go code is ever needed for the fallback — the settings.Service handles both the convention and the explicit override.

Vector search module

search — pluggable backend (Qdrant today, OpenSearch planned), index CRUD under /admin/search/*, semantic query under /search/*, FlowDSL nodes redelay/search-upsert + redelay/search-query. Embedding provider/model are runtime-switchable via admin settings, so the same deployment can move between OVH bge-m3 (€0.01/M) and local Ollama without redeploying.

FlowDSL Studio settings (admin-editable)

The flowstudio module (served on admin-api at /flowdsl) reads three settings at request time — edits take effect on the next page load without a restart:

Empty settings fall back to env defaults (FLOWDSL_LICENSE_KEY, FLOWSTUDIO_EMBED_URL, FLOWSTUDIO_UI_PATH).

Studio deep-linking

Any admin UI button can open the Flow Studio pre-selected on a specific flow, version, template, or deployment by appending query params:

http://admin.yourapp.com/flowdsl?flowID=flow.xxxx&versionID=ver.yyyy
http://admin.yourapp.com/flowdsl?templateID=default
http://admin.yourapp.com/flowdsl?deploymentID=dep.zzzz

The Go shell parses these into a window.__FLOWSTUDIO__.initial block; the hosted Studio app also reads window.location.search directly. Use the useFlowStudioLink() composable from the base layer's flows module to generate links from project admin pages:

const { linkTo, openFlow, openTemplate, openDeployment } = useFlowStudioLink()

// In a template:
<UButton :to="linkTo({ flowID, versionID })" target="_blank" external>
  Open in Studio
</UButton>

// Or programmatically:
openFlow(flowID, versionID)

linkTo reads the admin-api URL from runtimeConfig.public.apiBaseUrl and the mount path from runtimeConfig.public.flowdslUiPath (default /flowdsl, overridable via NUXT_PUBLIC_FLOWDSL_UI_PATH).

Shared components

Shared composables

Dashboard layout

layouts/dashboard.vue owns the sidebar + mobile topbar + session-expired modal. All pages with layout: 'dashboard' (the default for authenticated routes) sit inside it. Don't reach into it directly — extend via module navigation.

Runtime config keys