# Syside 1.0.0-beta.1: try out new features earlier

**URL:** <https://forum.sensmetry.com/t/syside-1-0-0-beta-1-try-out-new-features-earlier/586>\
**Category:** News & Announcements\
**Created:** [October 5, 2026, 10:17am UTC](https://forum.sensmetry.com/t/syside-1-0-0-beta-1-try-out-new-features-earlier/586 "2026-10-05T10:17:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zygimantas](https://yyz2.discourse-cdn.com/flex008/user_avatar/forum.sensmetry.com/zygimantas/32/49_2.png) [@Zygimantas](https://forum.sensmetry.com/u/Zygimantas)\
**Post date:** [October 5, 2026, 10:17am UTC](https://forum.sensmetry.com/t/syside-1-0-0-beta-1-try-out-new-features-earlier/586/1 "2026-10-05T10:17:41Z")

</div>

Hi everyone,

We’ve just published **Syside 1.0.0-beta.1** on [GitLab Releases](https://gitlab.com/sensmetry/public/syside/-/releases/v1.0.0-beta.1). This is our first look at Syside v1, shared early with Syside users. You need a valid license key to access beta releases.

Get started here:

1. [VS Code Extension — Syside](https://docs.sensmetry.com/preview/extension/)
2. [Python Library & CLI — Syside](https://docs.sensmetry.com/preview/python-lib/)

**What’s in 1.0.0-beta.1**

- **One Syside VS Code Extension.** We have deprecated Syside Modeler as a standalone VS Code extension and moved to the “Syside: SysML v2 Automate Systems Engineering” extension for v1 and further support. The language features (completion, validation, formatting, navigation) are free and require no license. An inserted license key unlocks diagrams, editable table and matrix views, and the Python Library integration. The status bar in VS Code now tells you whether you’re on `Syside: Free` or `Syside: Paid`.
- **Same diagrams in VS Code and the CLI.** The new extension now uses the same built-in visualization engine as `syside viz` in the VS Code UI, so diagrams look the same wherever you make them, and you no longer need Java installed. You also get the ability to jump between diagrams and text, pickers for model depth, diagram type and layout selection, and a button that copies the matching `syside viz` command. Your `[viz]` options in `syside.toml` now apply in the VS Code UI generated diagrams too.
- **Support for Sysand projects.** The new `syside project` command and the `syside.project` Python API let you work with SysML v2 projects to manage scope and improve performance.
- **CLI is now part of the same `pip install syside` installation.** We’ve stopped publishing separate CLI downloads. The Syside Python Library & CLI (Python 3.12+) is how you use Syside from the command line and in CI. We’ve also extended the list of CLI reference commands in the documentation.
- Plus improvements to validation and formatting, and the bundled standard library is updated to the 2026-08 version.

Full beta release changelog: [changelog](https://gitlab.com/sensmetry/public/syside/-/releases/v1.0.0-beta.1#changelog).

**Before you upgrade: breaking changes**

- **Coming from Syside Modeler?** Uninstall it, then install the Syside VS Code Extension. Your `syside.modeler.*` settings still work, and the extension will offer to rename them to `syside.*`.
- `syside.restart` and `syside.openLog` are now `syside.lsp.restart` and `syside.lsp.openLog`.
- The Python Library no longer has `syside.preview`. Use `syside.LockedModel` and `syside.UnlockedModel` instead.
- Names from indirect Sysand dependencies are only visible if you declare them as direct usages.
- New validations added to ensure your models’ correctness. Follow these docs to fix them: [Migrate to Syside v1 — Syside](https://docs.sensmetry.com/preview/about/migrate-to-v1/)

The [GitLab Release page](https://gitlab.com/sensmetry/public/syside/-/releases/v1.0.0-beta.1) has the full notes, links to the docs, and install instructions.

**What we’d ask of you**

Install it, run it against your own models, and tell us about anything that breaks or feels off. We especially want to hear about moving over from Syside Modeler, the new visualization engine, performance, and your CI setups now that the CLI comes through `pip`.

You can report issues through our usual channels (the support email or this forum). Please mention that you’re on the **beta**.