McBasic™Get McBasic™ ↗Use AI assistance with explicit review
Configure a provider, control the source shared with it and inspect a candidate before applying changes.
Understand the current status#
AI assistance is an evolving feature in the current source builds. Provider configuration and controlled test success do not prove every installed provider can complete a real generation session. The release notes distinguish implemented UI and transport work from remaining real-provider qualification.
Configure the local provider#
Use LM Studio (local) for loopback Responses API requests. The guide covers the endpoint, loaded model, optional key, request limits and failures.
Select an existing provider deliberately#
The IDE supports configuration paths for an external Codex installation, API-backed responses and a local LM Studio provider. External Codex is selected from an existing installation; McBasic™ does not install or bundle that executable. A macOS permission chooser can grant access to the selected file. A generation model is still required for generation even when connection setup can proceed without one.
Select the kind of assistance#
Ask and Explain answer without editing; Plan interviews before drafting; Fix uses current diagnostics or a behavioral bug report; Review lists findings and edits only after Apply selected; Build proposes checked changes. Learn the six chat modes and use Add to Chat to limit the editable target.
Review the exact scope#
Before sharing source or accepting a plan, review which project documents are in scope. A provider connection is not blanket consent to send every file. Use context chips and Show exact content; see context and request size for budgets and storage. If a candidate requests a package reference or migration, inspect that dependency or SQL separately from the code diff. Rejecting a candidate should preserve the existing project.
Choose the application policy#
The current default is Automatically, with Undo: checked changes apply automatically. Choose Ask me first in AI Provider Settings to stop at Ready to apply with Apply and Discard. Read plans, apply and undo before beginning. Inspect full handlers, bindings and the diff, then Check and Run the result yourself, including the failure path. Keep a Git checkpoint before a substantial assisted change; Undo and source history solve different recovery problems.
Stop without losing the boundary#
Use Stop when a request should be interrupted. The current transport work preserves the connection long enough to request cancellation before cleanup. A stopped or failed request is not a successful generation. Do not repeatedly approve broader access simply to make an unexplained provider failure disappear.
Practice with a disposable project#
The AI review exercise gives you an exact prompt, consent checks, a candidate-review checklist and rejection/recovery tests. It explicitly stops if the selected real provider cannot connect; it does not relabel a connection failure as a completed tutorial.
20f4bfed6b · Build manifestSources & maintenance
Original web explanation, reviewed against these repository sources. API tables and example files follow the implementation.
src/McBasic.Build/LmStudio.cssrc/McBasic.Build/AiProvider.csmacos/McBasicIDE/Sources/AIRequestBudget.swiftmacos/McBasicIDE/Sources/AIProviderController.swift