Configuration

Skryba Desktop has no preferences database and no credential form. Its configuration is executable discovery, the spawned process environment, and one build-script destination override.

Runtime executable discovery

PATH is read from ProcessInfo.processInfo.environment. Well-known directories are appended as documented in spawn contract. There is no variable for an explicit binary path.

Runtime credential file

Optional path: ~/.config/skryba/env.

Syntax:

# comment
KEY=VALUE

Rules implemented by SkrybaCLI.environment():

• unreadable or absent file is ignored;
• blank lines and lines whose trimmed form begins # are ignored;
• split at the first =;
• trim key and value;
• ignore empty keys and lines without =;
• never overwrite a key already present in the launch environment.

The merged dictionary is passed unchanged to the CLI. Select BRAMA_URL with BRAMA_TOKEN_ROLE=ROLE#FIELD, or SKRYBA_MODEL_SERVICE_URL with SKRYBA_MODEL_SERVICE_KEY_FILE naming an owner-only bearer file; both use SKRYBA_MODEL and optionally SKRYBA_JUDGE_MODEL. The URL choice binds the credential route: crossed declarations are refused before a bearer is sent. Only the Brama route accepts paired SKRYBA_AGENT_ID and SKRYBA_AGENT_AUTH_SECRET_ROLE=ROLE#FIELD. Role references resolve through stado credentials get --role, not through vault item names. BRAMA_TOKEN and SKRYBA_AGENT_AUTH_SECRET are retired and are not read.

Without Stado, SKRYBA_CREDENTIALS_FILE explicitly selects an owner-only JSON file mapping role → field → value for the Brama token and optional signing secret; it does not replace the direct service's bearer file. Desktop passes these declarations to the CLI unchanged and shows its refusal rather than retrying another route. See credential boundary.

Detector keys and URL overrides, and SKRYBA_DATABASE_SCHEMA, are also CLI-owned settings. The fleet database holds styles, languages, drafts, writing-style rows and detector scores. See the CLI configuration and database contracts for resolution and refusals.

Build and install

Variable	Default	Meaning
WISENT_RELEASE_VERSION	CFBundleShortVersionString from App/Info.plist	release version; must contain exactly three dot-separated numeric components
WISENT_BUILD_NUMBER	git rev-list --count HEAD	bundle build number
WISENT_UPDATE_FEED_URL	unset	optional Sparkle feed; when set it must use HTTPS
WISENT_CODESIGN_IDENTITY	first Developer ID Application, then Apple Development identity	explicit signing identity
SKRYBA_INSTALL_AFTER_BUILD	yes	set exactly no to stop after building/signing without installation
SKRYBA_INSTALL_APP_PATH	$HOME/Applications/Skryba.app	installed bundle destination

The build script builds the release product, assembles resources and an optional Sparkle framework, requires a stable signing identity, verifies the signed bundle, and—unless installation is disabled—replaces the destination and registers it with Launch Services.

Workflow values

Candidate count, chunk size, temperature, quality threshold, detector list, policy path, the chosen style and language names, the generator choice and its local checkpoint, adapter, revision, device, precision and token budget, the catalog form's list, command, name and instruction, and every writing-style field — sources, word bounds, shape or objective, destination, name, lead words, row limit, and the train form's checkpoint, adapter destination, revision, device, precision, rank, epochs and learning rate — are in-memory UI draft fields. They reset to source defaults on app launch and are not persisted; the styles and languages themselves persist in the CLI's fleet database. Nothing here is a credential, and no field names the ster binary: the CLI finds it by search.