Documentation

Configuration

FridayLocalAI is intended to be governed through explicit settings and operational rules rather than hidden behavior and guesswork.

Configuration goals

Configuration in FridayLocalAI is not merely cosmetic. It is part of the system contract. Settings will ultimately determine how models are selected, how memory scopes behave, how artifacts are handled, and how local infrastructure is used under specific policies.

The long-term objective is a platform whose behavior can be shaped through understandable configuration rather than accidental side effects.

Core configuration areas

  • Local model runtime selection
  • Routing and task assignment behavior
  • Memory scope and persistence rules
  • Knowledge access and retrieval boundaries
  • Artifact generation settings
  • Operational logging and diagnostics

Why configuration matters

A system that cannot be governed becomes difficult to trust. FridayLocalAI is being built around the opposite premise: configuration should make behavior more explicit, not more mysterious.

That means future settings should support stable routing, scoped context, predictable defaults, and strong separation between local authority and external dependency.

Planned settings concepts

Model Management

List available models, note their capabilities, and support future routing-aware model administration.

Routing Policy

Deterministically select or suggest models and agents based on task type, capability, and system policy.

Memory Governance

Control where memory is written, how it is scoped, and what kinds of information remain available across contexts.

Configuration principles

FridayLocalAI is being developed with a strong bias toward traceability, continuity, and explicit contracts. In practice, that means configuration should support:

  • Stable system behavior over time
  • Separation between exploratory features and production-safe operation
  • Clear operational defaults
  • Minimal ambiguity about where information is stored and used
  • Practical administration for real humans rather than ceremonial dashboard theater

That last one matters. The software should help the operator, not cosplay as a control panel from a low-budget spaceship.