Simulation and session services

Mogick isolates stateful engineering runtimes by task. A task can own its Julia process, model service, MCP context, and connector session so parallel tasks do not accidentally share models or runtime state.

Services start on demand or while a task is being prepared. Switching tasks does not stop a running service. Archiving, deleting, or choosing Release resources cleans up the runtime assigned to that task while retaining the appropriate conversation record.

The UI distinguishes startup, ready, unavailable, disconnected, and failed states. A service failure should produce a readable message in the relevant tab or response. Restarting a service never rewrites project files by itself.

Use /mcp to inspect the MCP servers and tools visible to the current task. For model files, close and reopen the .mo tab after the model service becomes ready.