A preparation checklist informed by Rittika Jindal’s OpenCode and Ollama report: runtime, project dependencies and independent acceptance checks.
The model has downloaded, but the test command needs another package. Without a connection, that can stop the task just as surely as an unavailable cloud API. Prepare the path from opening a project to checking a repair, rather than treating the model download as the finish line.
Rittika Jindal, who identifies as a Principal Engineer at Thomson Reuters, reported an expense-total repair on a Mac on October 27. Her account describes a one-line edit followed by five passing original tests, with the tests unchanged. It is one author's example, not validation for every repository. The useful reading separates conditions from outcomes: what was ready before disconnecting, what the connectivity checks established and how the edit was accepted.
Divide preparation into three parts. Startup covers the installed tools, model and provider. The project includes source, dependencies, test data and the documentation you expect to need. Acceptance means knowing the check command and expected behavior. Walk through all three before losing connectivity. Retain the exact launch command: opening an agent another way may select different configuration.
The companion repository routes both model roles to a local service and pins OpenCode 1.19.4 in its instructions. Those are conditions of the reported example, not a recommendation to change your system to that version. Ollama's integration reference distinguishes local from cloud models and explains configuration precedence. The presence of Ollama alone does not determine where a request goes.
Keep connectivity evidence separate from code acceptance. A local response establishes that the service is reachable. A failed external request describes that attempt at that moment. A provider list is not a complete check of the environment either. Judge the proposed repair using unchanged tests and a file diff, independently of how confidently the agent explains it.
NODVIEW inspected the published account and configuration but did not reproduce the offline run. A useful preparation exercise leaves you knowing what to launch, how to check the result and which remaining actions need a connection. Establish that before the journey or outage, rather than at the first missing dependency.