Loading...
PyStator·Server values come from the API (admins can patch pystator.cfg in the table below).·Browser blocks store defaults in localStorage — use Save browser settings after editing.
Effective values from the API process: environment overrides pystator.cfg. Passwords are masked. Log in as Admin to edit the config file from this table.
These fields map to AppSettings in lib/settings.ts. Every persisted key is editable below: API URL, database test bundle (with an on/off switch), discovery defaults, DLQ test bundle (with an on/off switch), and the FSM editor preference.
Base URL this browser uses for API calls (stored in localStorage). Server default comes from PYSTATOR_API_URL / [api]. App: PyStator
Optional credentials stored in this browser for the Test connection action only. The running API uses PYSTATOR_DATABASE_URL (see server runtime above).
When off, values are kept in storage but hidden to reduce clutter.
Server-side execution policy is configured with PYSTATOR_ALLOW_INLINE_CODE_ACTIONS, PYSTATOR_ALLOW_INLINE_CODE_IMPORTS, and [features] (see server runtime). The control below is stored only in this browser.
Stored in localStorage as features.inlineCodeActionsEditor. There is no separate browser toggle for imports; that is server-only today.
Defaults stored in this browser for discovery tools and tests. The API worker uses [discovery] in pystator.cfg (editable in server runtime when you are an admin).
Shadow mode
Compare inferred candidates without enforcing them in production traffic.
Browser-only credentials for Test connection and Load statistics. Production worker settings use PYSTATOR_WORKER_DLQ_* (see server runtime).
Show connection fields, test, and statistics actions.