Settings
Settings open from the topbar and group the configuration into four blocks, by what they affect: your account, this application on this machine, the open project and help.
Account
Section titled “Account”Account and plan
Section titled “Account and plan”Who you are and which plan you have. Aseptic works without an account; what needs an identity are the AI surfaces (see Capabilities).
- Plan. The plan is granted by the identity provider once the payment is confirmed, not by the app. After going through checkout there is nothing to do: the window checks the status for a couple of minutes and activates it on its own. If it took longer than expected, Refresh my plan forces it, and if it still doesn’t change, signing in again is usually enough.
- Seats. On a team plan, how many there are and how many are in use. Handing them out is done in the web portal, not here.
- Open my account on the web goes to the portal, with your AI usage against your quota, the machines that sync, the downloads and seat management.
Only shown with a hosted team catalog: it stores the key the team’s scenarios are encrypted with. It reaches every machine in the organization on its own —whoever already has it leaves it encrypted for the rest— and this tab shows where things stand; it can be copied as a backup. It never leaves the team’s machines. A Git catalog has no key to store: the repository itself is what authorizes.
Sync your personal settings
Section titled “Sync your personal settings”Carries the theme, the palette, the panel layout and the language to the other machines where you use your account. Nothing from the project travels: no scenarios, no micros, no credentials.
It is end-to-end encrypted with a key only you hold: it is created on the first machine (Create key) and pasted into the next ones (Key from another machine). Without that key what was published cannot be read — not from the server either, which is why losing it means starting over rather than recovering anything.
With the key in place, the block states where you stand —up to date, with unpublished changes, or with another machine that published something newer— and it is resolved with Publish this machine’s or Fetch the published ones. Stop syncing disconnects this machine without touching what has been published.
The same exists in the CLI (aseptic sync), because preferences live in the engine and
not in the window.
Application
Section titled “Application”Appearance
Section titled “Appearance”- Color palette and theme (light/dark), which apply instantly.
- Font (system or monospace) and interface zoom.
- Language.
- Compact rails (icons only).
Behavior
Section titled “Behavior”- Automatic saving in the editors (mocks, scenarios, micros). If disabled, you save with the Save button.
- Close to tray: closing the window keeps Aseptic running in the background.
- Fetch the branch on import of a scenario, when the repo is on another one.
- Follow the log tail by default when launching a scenario.
- Log line limit on screen (the file keeps everything; the limit is only what’s kept in memory).
- Metrics history of the Status tab.
Shortcuts
Section titled “Shortcuts”The keyboard shortcuts reference, also available at any time with the
? key.
Project
Section titled “Project”- Workspace — the folder with the micros’ repos.
- docker-compose — the one bundled with Aseptic (recommended) or your own. The mock server port and the OpenAPI token are set in the Mocks section itself, in its settings panel.
Credentials
Section titled “Credentials”The secrets you reference as ${creds.key} in manifests, dependencies and databases. They
are saved outside Git (settings.local.yml). See The workspace and
.aseptic/.
Catalog
Section titled “Catalog”Export or import the whole catalog (micros, scenarios and startup customization) in
a single file, to move it to another machine. From the CLI: aseptic bundle export|import.
Support
Section titled “Support”The form to report a problem to the team and the button that copies the support details (version, account and installation) to paste into an email.
Privacy
Section titled “Privacy”The status of the diagnostic telemetry (opt-in), the installation ID and the legal texts. Your micros’ logs and business data are never sent.
The installed version and the updates check (Aseptic also checks on startup). See Install.
Git connections
Section titled “Git connections”They are not in Settings: they live in the Git menu in the top bar (the branch icon), next to the rest of the repository actions. They link accounts (GitHub, GitLab or another) so Aseptic can update the micros’ repos. Access is read-only (fetch and branch switching; never push). It’s used when importing a micro from Git and when switching branches.