Skip to content

Migrate LM Studio to the provider abstraction without behavior regressions #38

Closed

Description

@triggeredcode

Goal

Make the existing provider the first production adapter for the new architecture.

Depends on

Scope

  • Implement the LM Studio adapter behind the provider contract.
  • Preserve streaming, cancellation, schema-constrained output, lane sampling, model status/load, and current retry behavior.
  • Keep the existing default model migration-compatible.
  • Run the current eval suite and compare baseline metrics.

Acceptance criteria

  • Existing users can continue with their current LM Studio configuration.
  • Input, Command, and Advisor behavior remains within the existing quality bar.
  • No renderer-side network proxy is required for inference.
  • Any metric regression is documented before merge.

Activity

  1. triggeredcode commented on Oct 19, 2026

    @triggeredcode
    OwnerAuthor

    Claimed. Implemented on feat/provider-context-roadmap in commit 6bed655 and included in draft PR #46. Mocked/full-suite checks passed; the attempted real-model comparison was invalid because LM Studio hit a Metal out-of-memory error before generation, so no live-quality claim is being made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions