Proven once One setup, ready and reversible

Make one local model setup work.

You choose a supported local model setup. LocalCode checks this Mac, shows what it will change, prepares the model server and optional editor integration, proves the declared checks, and gives you a safe way back.

See where it helps ↓View the retained evidence →

This provider lifecycle was exercised on one documented Apple Silicon profile. The preview is retired. The current alpha failed its human acquisition and Aider workflow, is blocked from release, and does not provide an autonomous coding agent.

You have a model and a Mac. The missing part is knowing that the provider is configured, reachable and reversible before an application connects to it.

Why it matters

The difficult part starts after the model downloads.

A model file is not a usable coding setup. Runtime versions, launch flags, context limits, endpoint behavior, prompt and edit formats, agent configuration and process ownership all have to agree.

WITHOUT LOCALCODE

You are the integration layer.

  • Guess whether the artifact fits once runtime and context overhead are included.
  • Translate model instructions into runtime flags and agent configuration.
  • Discover incompatibility after a healthy endpoint produces unusable agent behavior.
  • Remember what changed, which process is safe to stop and how to undo it.
WITH THE M1 LIFECYCLE

The setup has one lifecycle.

  • One pinned profile names the artifact, runtime, context, endpoint and optional consumer.
  • One read-only plan exposes every mutation and its authority before anything changes.
  • Provider readiness and optional editor compatibility are reported as different claims.
  • Status, disconnect and rollback operate only on exact LocalCode-owned state.

Where you use it

Small, practical jobs for one machine.

M1 is useful when you already know which supported profile you want. It removes setup and lifecycle work; it does not yet decide which profile is best.

01

Private repository

Connect a local application to a loopback model endpoint. The retained Aider path is interactive editing, not an autonomous repository agent.

02

Flight tomorrow

Download the approved stack now and prove that the exact provider or Aider path cold-starts with non-loopback networking denied.

03

Local-model experiment

Try a pinned setup without overwriting normal Aider or repository configuration, then disconnect or restore the prior state.

04

Parent agent prepares a provider

Let Codex or Claude drive the same read-only plan and approval contract, then receive an exact endpoint instead of inventing runtime configuration.

05

Application needs an API

Prepare only the verified OpenAI-compatible endpoint. Do not install or imply compatibility with a coding consumer.

06

Reuse what is already installed

Adopt exact compatible artifacts and endpoints where possible while keeping ownership boundaries explicit.

What happens

From a chosen profile to something you can use.

The terminal result is not “installed.” It is a currently valid provider with an exact identity, verification evidence and reversal boundary. Optional editor or agent integrations require separate evidence.

01

Inspect

Read the Mac, artifacts, runtimes, tools and loopback endpoints. Change nothing.

02

Plan

Show downloads, installs, process starts, configuration writes, limitations and rollback.

03

Approve

Bind authority to the exact plan digest. Changed material state invalidates it.

04

Prepare

Install or adopt the pinned components and start only the declared local provider.

05

Prove

Check artifact identity, API behavior and exact instruction response. Label an optional supplied-file editor probe separately.

06

Control

Connect, revalidate, disconnect or roll back without guessing which process or files belong to LocalCode.

User journeys

Four ways to use the same control plane.

Interactive setup, provider-only serving, parent-agent operation and offline preparation reach the same provider policy and lifecycle. Aider remains an optional editor adapter.

01

I want to use Aider with this local provider.

$ localcode setup --channel candidate --profile qwythos-aider-whole --project .

Result: An isolated interactive-editor launch contract. The supplied-file probe does not establish autonomous repository access or task completion.

02

My application only needs a local model API.

$ localcode serve --channel candidate --profile qwythos-aider-whole --offline-ready

Result: A verified loopback endpoint and model identity; no coding consumer is installed or claimed ready.

03

I want Codex or Claude to prepare it for me.

$ localcode prepare plan --consumer aider --for focused-coding --channel candidate --profile qwythos-aider-whole --project . --json

Result: The agent presents the same plan and digest, waits for authority, then returns the same readiness and lifecycle contract.

04

I need to know it will work without the internet.

$ localcode setup --channel candidate --profile qwythos-aider-whole --offline-ready --project .

Result: The managed stack is cold-restarted and the declared path is repeated with non-loopback networking denied.

What “complete” means here

One narrow promise, exercised end to end.

The retained evidence covers provider readiness and one supplied-file Aider probe for Qwythos/MLX on one 24 GB M4 Pro. A separate Qwen provider later passed the normal lifecycle. Neither result establishes autonomous agent behavior or general coding quality.

Read the versioned acceptance record →
2modes

Provider-only or provider plus Aider.

14recovery boundaries

Interrupted mutation paths exercised.

1offline proof

Cold declared path with external networking denied.

4lifecycle controls

Status, launch, disconnect and rollback.

The boundary

Useful now.
Not automatic yet.

This feature solves: “I chose this supported setup; make it work safely on this machine.”

It does not solve: “Choose the best setup for this task, RAM state and my preferences.” That is the next product milestone.

See the product journey →

Demonstrated in 0.4.0rc2

If you choose the retained profile, LocalCode can control its provider lifecycle.

Open the retained release →

Retired MIT-licensed technical preview.
Source bundle, checksum, erratum and evidence retained.