Access and setup¶
Use the Sindri Console to configure a spacecraft, run its engineering models and review the recorded results. The command line supports the same underlying studies for repeatable and automated work.
Get access¶
Use the compatible runtime supplied through your existing Sindri access arrangement, or the Console address supplied by the person operating your server. There is no generally available installer documented here yet. Acquisition, installation, supported release platforms and update instructions will be added to this setup section as those distribution methods become available.
The example downloads contain editable study inputs; they do not install Sindri. You can read their recorded results without a runtime.
Open a local Console¶
If you have a supplied command-line runtime, check it and launch Console:
sindri --help
sindri console
Open the private Console URL printed by the launcher. It authorizes this browser tab to edit and run projects, and the browser removes the credential from the address bar. Keep that URL private. A bare address may let you read results without authorizing changes; after restarting the server, use its new launcher URL. Leave the launcher running while using Console.
When Configure opens, continue with your first Console run. If the command is missing or reports mismatched assets/resources, retain the diagnostic and contact your runtime provider for a compatible package. Do not substitute a different catalog merely to clear validation.
Connect to a supplied server¶
Open the server address given to you. If Connect to Sindri appears, enter the connection token supplied by its operator and select Connect. You do not need local solvers to use that server. Calculations and files belong to the server machine, including folders selected through Open existing run.
If you operate the server, see remote access configuration for trusted-network access and allowed run locations. Connection credentials are separate from optional AI-provider credentials.
Keep projects and results¶
Built-in examples are read-only starting points. Load Example creates an editable working copy; Save As writes a project to a permitted project location. Each run keeps its own captured inputs and results. Changing the project later does not change an earlier result.
Keep project folders and complete run bundles when transferring your work. Console names, tags and saved workspace state also live in its local database; copying a run bundle alone does not transfer all of that workspace state. For an upgrade, preserve the current state and follow the supplied runtime's instructions. Console store recovery is an operator procedure for restoring an existing compatible backup, not a general installer.
Optional capabilities¶
| Capability | What you need |
|---|---|
| Native sizing and numeric evaluation | Compatible runtime and the example's referenced catalogs/policies; no AI provider is needed |
| CAD exports | A configured supported FreeCAD runtime on the server; enabled in every Console starter except Evaluation baseline. Missing exports do not erase native results |
| 42 execution | A configured 42 runtime and execution-enabled scenario; a prepared handoff is not an executed simulation |
| Assistant and agent review | The runtime's optional agent capability and authorized provider configuration |
Check Console starters before selecting a specialist example. The evidence and limits page explains what a completed example does and does not establish.