# KORA Studio Local Server Preview Page

## Status

The KORA Studio local server root renders a static first-run preview for the server skeleton. It is still not a full frontend and does not make KORA Studio production-ready.

The preview should frame KORA Studio as a local-first AI Task Execution Router workspace. It should not describe Studio as an LM Studio replacement or a generic local chatbot.

## Static UI Prototype

The page is a self-contained HTML preview served from `/`. It uses embedded CSS only and does not load external scripts, external stylesheets, CDNs, generated assets, frontend build tools, or runtime integrations.

Page sections:

- Header with `KORA Studio`, `Local Preview Scaffold`, and AI Task Execution Router workspace copy
- Status cards for local server state, disabled provider calls, disconnected model/runtime integration, browser launch availability, and disconnected Ollama integration
- Your Computer
- Model Capability Estimate
- Runtime Status
- Catalog vs Installed
- Setup Guidance
- Disabled Download/Run Actions
- KORA Boost Boundary
- Execution Viewer with fixture/mock events
- Standard Mode vs KORA Boost fixture comparison
- Report Viewer Placeholder with fixture metadata
- Endpoint panel for `/health` and `/status`
- Limitations panel with explicit no-provider, no-model/runtime, no-Ollama, local-browser-launch, and no unsupported-claims boundaries
- Footer with local-only and claim-safe wording

Required future UI narrative:

- System Profile: show what the computer can physically run, including OS, CPU/GPU, RAM/VRAM/unified memory, runtime, and installed models.
- Model Capability: distinguish physically runnable local models, larger-model workflow feasibility, and optional external/provider/distributed routes.
- KORA Boost Explanation: explain that Standard Mode sends every step to the model, while KORA Boost routes deterministic and structured work to CPU/local fast paths first.
- Execution Path UI: show deterministic code, structured lookup, local model, larger model, and external/provider/distributed route disabled by default.

## How to Run

```bash
python3 -m kora studio
```

Open the local page at:

```text
http://127.0.0.1:8765/
```

The server remains localhost-only by default. Browser auto-launch is enabled by default and can be suppressed with:

```bash
python3 -m kora studio --no-browser
```

The compatibility command `python3 -m kora studio --serve` also starts the local server. If browser launch fails, Studio prints the local URL and keeps serving locally.

Developer options include `kora studio --no-browser`, `kora studio --port 8765`, and `kora studio --status`. An optional future browser selector such as `--browser chrome` is not implemented yet.

## Endpoints

- `/` serves the static first-run UI prototype
- `/health` returns local health status JSON
- `/status` returns local preview status, system profile, model capability estimate, runtime status, model catalog recommendations, setup guidance metadata, execution viewer fixture events, Standard Mode vs KORA Boost fixture metrics, report viewer placeholder metadata, KORA Boost copy, docs paths, and fixture paths

## Current Limitations

- no full frontend yet
- no Ollama integration
- no provider calls
- no cloud sync
- no model/runtime integration yet
- no project UI yet
- no API keys required
- no model download
- no model execution
- no runtime model list command
- no private model directory scan
- no arbitrary report file scan
- no active report export
- no client-side calls, telemetry, local storage, or session storage

## Claim Boundary

The page is for deterministic-first local workflow exploration. It does not create production claims, API-cost claims, energy claims, benchmark claims, provider-validation claims, or deployment-readiness claims.

KORA does not make large models smaller, does not remove RAM/VRAM/unified-memory/model-loading requirements, and does not claim to run unsupported larger models on local hardware. Larger-model workflow feasibility depends on actual memory, runtime support, quantization, and validation.

## Privacy Boundary

The placeholder page is static and self-contained. It does not expose environment variables, provider responses, private data, private internals, campaign material, or proprietary datasets.
