MW/SimBridge
TR
JSON / JSONL / Markdown → validation → conflict checks. Importing does not automatically start a simulation.
01 — 06 QUEUE
Different computers.
One connected workflow.
MW-SimBridge coordinates the CST automation already installed on your Windows computers at home, at work and in the lab — from one queue.
Does not install CST or change your license.
Does not include a new solver.
02 — 06 PAIRING
The controller holds the queue. Each worker joins by invitation, with fingerprint verification and your approval.
Workers initiate outbound connections. LAN, an existing VPN or configured HTTPS access is required; the app does not reconfigure your network.
03 — 06 DISPATCH
CST version, runner binding, tags, resource budgets and working hours are checked together. If no computer is eligible, the job waits.
04 — 06 INTERRUPTION & RECOVERY
When a worker disconnects, a job that has already started becomes “unknown” at the controller. It is not automatically sent to another computer.
The job may still be running remotely. When the connection returns, its state is reconciled with the same computer; interrupted file transfers can continue.
This is not CST solver checkpoint / resume. Manually retrying an unknown job may run it twice.
05 — 06 RESULTS & REPORTS
Results return to the controller. JSON is the numeric source of truth; Markdown and HTML reports are generated from the same data.
A completed job does not necessarily meet its design objectives. Execution status and design objectives are reported separately.
Missing measurements are not filled with invented values. Their absence and reason are shown. CSV / JSONL export is also supported.
06 — 06 FIRST CONNECTION
Your existing CST installation and simulation automation stay in place. MW-SimBridge coordinates where jobs go and how results return.
Add your first computerYOUR CONTROL. ONE COORDINATED WORKFLOW.
From preparing jobs to collecting result files, each stage has its own checks.
JOBS / QUEUE
Start jobs in selection order, target a specific computer or pause new dispatches for a work group.
depends_on for job dependenciesCOMPUTERS / RESOURCES
Connection, runner readiness and eligibility to accept a job are evaluated separately.
RESULTS / RECORDS
Export reports, copy selected results to a folder and follow the history of each attempt.
Resource budgets are admission checks. They do not impose hard OS-level CPU / RAM limits unless the runner supports them.
“WHY ISN’T IT STARTING?” / A PRACTICAL GUIDE
Choose a scenario to see what the app checks and what you can do. This guide does not connect to your computers.
A job requiring CST 2025 is not sent to a computer with only CST 2026 installed.
It keeps the job queued and explains why a computer is ineligible. A job is not marked failed simply because no suitable computer is available.
Prepare a computer with a compatible CST installation and verified binding. Use “Any version” only if your job genuinely supports it.
A reachable computer may still be missing a resource package, CST verification or a local runner binding.
It lists missing requirements per computer. Automatic preparation checks the resource package, existing CST installation and binding for supported profiles.
Review and approve the suggestions. Define a local binding yourself for an unsupported runner. Automatic preparation does not install CST or grant approval tags on your behalf.
If a computer disconnects after a job has started, the same job is not automatically started on another computer.
It reconciles state with the same computer when it reconnects. An interrupted result transfer can resume from the last chunk; this does not restart the solver.
Check the computer and network first. A manual retry could run the same simulation twice. Do not assume that a solver resumes from where it stopped after a power failure.
License waits do not consume normal job attempts; they are managed with a separate limit.
When a license is busy, the job waits with increasing retry intervals. The app does not purchase licenses, extend entitlements or change your license server.
Set concurrent-job and license-wait limits to match your actual license capacity. The number of computers is not the number of concurrent solves you are licensed for.
IMPORTANT LIMITATIONS
End-to-end testing with real CST and testing between computers on different networks have not yet been performed.
Test-runner results are not real simulation data.
The test report dated 25 September 2026 records 120 passing tests on Linux. This does not mean that the Windows installer or real CST workflow has been validated in the field.
Read the test coverage ↗INSIDE THE APPLICATION
Computers, the queue and events that need attention.
The image below is an actual application screenshot (Turkish UI).
See why a job cannot start on each computer. Review suggestions for missing resources, versions, tags or bindings; apply changes with your approval.
Prepares resource packages, the installed CST version and supported runner bindings. It does not install CST or change license or network-security settings.
Single-use invitations, certificate-fingerprint checks and a separate identity for each computer. Workers receive jobs only after controller approval.
CONNECTS TO YOUR EXISTING AUTOMATION
The controller’s local REST API and the mw-simbridge command line can fit into your existing job-generation and reporting workflow.
127.0.0.1:8765/api/v1mw-simbridge validate isler.jsonl --batch-id tarama-01
mw-simbridge import isler.jsonl --batch-id tarama-01 --commit
mw-simbridge status --batch tarama-01
mw-simbridge report --batch tarama-01 --format csv --out ozet.csvYour example file, runner profile and API key must be configured. This page does not execute commands.
RESULT PACKAGE
Attempts, execution status and files are kept together. Compare a group or copy selected job outputs into your own folder.
execution_status
Shows whether execution completed technically.
objectives_met
Evaluates the design objectives separately.
<group> / <job> / ├── rapor.json Numeric source ├── rapor.md Readable summary ├── rapor.html Browser report └── dosyalar / Simulation outputs
Missing values stay null / — with an explanation. Reports produced by the test runner are marked TEST.
SETUP / WINDOWS x64
Start with the controller. Then add your first worker with its existing CST automation.
WINDOWS INSTALLER
Check GitHub Releases for the Windows installer. A direct download link appears here when a published ZIP is verified.
Check GitHub Releases ↗MW-SimBridge-<version>-Kurulum-x64.zip
You need CST with a valid license, working runner automation and an authorized network connection. Configure your license concurrency limit separately. Real CST and cross-network testing have not yet been performed.
Download and extract the published ZIP on the controller. It installs for your user account; Python and administrator privileges are not required.
Get the file only from the project source. Verify it against SHA256SUMS when provided with the release. Do not blindly bypass Windows security warnings.
Choose Controller for management only, or Combined mode if this computer will run jobs too. Configure network access and prepare the connection profile.
Choose Worker mode on the other computer. Join with a single-use invitation file or code, verify the fingerprint and approve it on the controller.
Verify the CST version, resource package and runner binding. Run the self-test, remembering it is not a real CST test. Then validate your setup with a small simulation you know.
Full user guide ↗READY TO SET UP?
Check off the steps you have prepared. This list is stored only in this browser; it does not measure your computer’s actual readiness.
A FEW CLEAR ANSWERS
No, but the worker needs an authorized, secure route to the controller. An existing VPN / Tailscale or configured HTTPS connection can be used. The app does not install a VPN or modify routers or firewalls. Cross-network end-to-end testing has not yet been performed.
No. Each worker needs a compatible CST installation, a valid license and existing simulation automation. This is not a solver or license manager; adding computers does not grant additional license rights.
Closing the interface does not stop background work. A network outage is also different from a shutdown: a power failure does not automatically resume a CST solve from where it stopped.
The GitHub repository is public, but no open-source license has been selected; all rights are reserved. The changelog and design decisions are available in the repository.