Read AI activity and recover safely
Tell a provider response, a compiler check, a repair and a completed application change apart.
Read the phase, not just the elapsed time#
| Activity | Meaning | Your next check |
|---|---|---|
| Reading the project | McBasic™ is preparing authorized context | Verify the selected target if the request is unexpectedly large. |
| Looking up… | The provider requested a McBasic™ reference topic | This is reference material, not permission to read arbitrary files. |
| Writing… | A candidate response/change is arriving | Wait for Check and the change card. |
| Checking… | The candidate is being validated | Do not treat generated text as applied code. |
| Repairing, attempt n of 3 | A failed candidate is being revised | Inspect the diagnostic and any renewed permission request. |
Separate tokens, reference topics and persisted history#
Input/output counters use what the provider reports; unavailable values appear as a dash. A stage’s counters include its checks and repairs. The reference count is distinct topics read, not a guarantee of correctness. When McBasic™ is reading locally or running Check, no provider counters are shown.
Open Details on a change or stage card for its timestamped activity timeline. The timeline is saved with the conversation; live counters are not. Displaying activity does not start extra provider requests.
Recognize a quiet request without restarting it blindly#
After one minute without a provider signal, the status says when activity was last seen. Provider requests, including LM Studio, stop after ten minutes without activity and have a sixty-minute overall ceiling. Stop requests cancellation and pauses a running plan; it is not a successful result.
Continue when the provider starts a new conversation#
From build 835, if a provider cannot resume its stored conversation and answers the current request in a new one, McBasic™ keeps that reply and follows the new conversation identifier. This avoids a Retry loop caused solely by the identifier changing after a restart.
The request still carries the selected project context, decisions and recent exchanges. A provider response is not permission to apply unreviewed code: normal candidate checks, scope and apply policy still govern modifications. Inspect the latest response before retrying so you do not mistake an accepted answer for a failed request.
Resume against the current project#
- Read the pause reason and the latest Check report.
- Confirm provider/model, current chips and scope.
- Resolve a missing target, over-budget context or dependency decision before retrying.
- Use Resume or Retry; the stage is regenerated against current source.
- Inspect the resulting diff and run your own acceptance checks.
A changed project or provider can invalidate a checked proposal. Do not repeatedly widen scope to make a diagnostic disappear. See plan recovery and context budgets.
20f4bfed6b · Build manifestSources & maintenance
Original web explanation, reviewed against these repository sources. API tables and example files follow the implementation.
docs/manual/16-working-with-the-ai-assistant.mdmacos/McBasicIDE/Sources/AIActivityStore.swiftmacos/McBasicIDE/Sources/AIProviderController.swift