Configuration
Set the way you want the editor to open once, then launch it with a file or project path. The shared Turbo Haskell configuration file is $XDG_CONFIG_HOME/thc/config.toml, or ~/.config/thc/config.toml when XDG_CONFIG_HOME is unset.
[editor.defaults]
backend = "metal"
scale = 1.5
screenMode = 259
columns = 120
rows = 50
appearance = "dark"
wordStar = false
wideSectionTitles = false
macKeySymbols = false
hapticFeedback = false
blinkCursor = true
crtFilter = true
pixelateUnicode = true
bufferView = "current"
materialIcons = false
streamerMode = falseUse terminal, auto, metal, vulkan, or web for the display backend. remote serves the protocol over standard input/output. Scale runs from 1 to 8 in eighth steps. Screen mode 3 defaults to 80×25; 259 defaults to 80×50. Explicit columns and rows override those dimensions. The terminal takes its size from the terminal window.
wideSectionTitles = true widens Markdown section headings to two cells per grapheme. Wide headings use stretch without bold; normal-width headings remain bold, and italic is preserved in both modes. Options > Preferences > Wide section titles changes and saves the same Display setting. It is off by default; see display.
In text mode, macKeySymbols = true uses ⌃, ⌥, ⇧ and ⌘ in key labels. You can also set Options > Preferences > Mac key symbols, which saves the choice to the global configuration. ⌥ and ⌘ reserve two character cells; the terminal cursor is repositioned after each glyph even if its font draws it narrower. This changes labels, not bindings: terminal shortcuts still use Control/Alt, and Command remains owned by your terminal application. Native Mac windows and Mac browsers use symbol labels automatically.
Options > Preferences > Haptic Feedback is off by default. When enabled, native Mac dialog buttons give a haptic tick as the pointer crosses their edge. The checkbox choice stays with the resumable session; set hapticFeedback = true in [editor.defaults] to enable it for future sessions. The setting is inert in browser and terminal frontends and on other platforms.
Command-line options override environment variables, which override project defaults, which override global defaults. For example, THC_EDIT_BACKEND=web overrides backend = "metal", and --terminal overrides both. --mode selects its usual dimensions unless --size is also supplied. --no-crt, --classic-icons, --standard-keys, --no-blink-cursor and --no-pixelate-unicode override enabled defaults.
bufferView accepts current, changes, only-changes, side-by-side, or markdown. Markdown renders .md and .markdown files; other files open in Current when this is the default. The radio controls in the Window menu save this default for newly opened buffers.
Startup defaults apply when a session is created. Resuming keeps that session's editing state; the frontend can still use your chosen backend and scale. To change a running session, use Options > Preferences. An agent can read and update non-agent settings through editor_settings; its defaults object updates the startup section without changing the current session.
Project configuration
Put thc.toml in the project root. It uses the same namespaces as the global configuration and can live in version control:
[editor.defaults]
screenMode = 259
columns = 120
appearance = "dark"
[editor.agent]
context = """
This package implements the editor. Keep the public API small.
Run the editor checks for changes to input, layout or rendering.
"""Discovery starts at the named file's directory, the named directory, or the current directory when no path is given. The nearest thc.toml wins. Without one, the search stops at a Cabal package, cabal.project, or Git root; the UI creates thc.toml there. Without a project marker, it uses the starting directory. Only one project file is loaded; parent projects are not recursively merged.
[editor.defaults] is merged key by key over global defaults. Omitted values inherit; project false overrides global true. Project defaults apply at startup. The agent's editor_settings.defaults writer still edits the global file; it does not rewrite the project file.
Keybindings
Replace commands through the global configuration or a project's thc.toml. Profiles are terminal, graphical (Linux/Windows native and browser), and macos (macOS native and browser). Every profile is prepared on startup/reload; changing attachments selects the focused profile and context immediately:
[editor.keybindings.terminal.source]
"hide.file.save" = ["Ctrl+Shift+S"]
"hide.file.open" = []
[editor.keybindings.terminal.sidebar]
"hide.sidebar.expand" = ["Ctrl+E"]
"hide.sidebar.down" = []
[editor.keybindings.terminal.conversation]
"hide.edit.copy" = ["Ctrl+Shift+Y"]
[editor.keybindings.terminal.terminal]
"hide.terminal.stop" = ["Alt+F11"]
[editor.keybindings.macos.source]
"hide.edit.copy" = ["Cmd+Shift+J"]
"hide.edit.paste" = ["Cmd+Shift+K"]
[editor.keybindings.graphical.source]
"hide.file.save" = ["Ctrl+Shift+S"]Contexts are source, wordstar, wordstar-block, wordstar-quick, dialog, sidebar, conversation, messages, debugger and terminal. A global table supplies explicitly configured commands to all of those contexts where the command and chord belong to the input owner; a context entry takes precedence over the same global command. Dialogs inherit only their focus and editing/search actions, and omit chords owned by dialog controls. Within each table a project entry replaces the global configuration's entry. An override replaces all shortcuts for its command; [] explicitly unbinds it. Omitted commands retain their inherited defaults. Menu, context-menu and command status labels show the focused context's effective binding. Unbound commands retain their captions without a shortcut; their menu and status-bar actions remain available. Conversation code drafts keep their fixed Query and Steer status actions, with Ctrl+Enter advertised for the opposite action.
Source, conversation and debugger panes retain the standard command defaults. When WordStar is enabled for a text source, its wordstar table owns named commands such as Save, Open and Undo. Their function-key and existing named command defaults remain; other Ctrl character keys stay inactive unless assigned. Movement and selection use hide.cursor.left/right/up/down and hide.selection.left/right/up/down. Row edges, document edges and pages use hide.cursor.row-start/row-end/document-start/document-end/page-up/page-down and matching hide.selection.* IDs. Home/End keep row edges, Ctrl+Home/End keep document edges, and PageUp/PageDown keep the existing view page size. Shift extends selection; other existing modifier aliases retain their defaults. Adjacent deletion uses hide.edit.delete-backward and hide.edit.delete-forward. Arrow keys, Shift+arrows and Backspace/Delete keep their defaults. Word movement uses hide.cursor.word-left/right and hide.selection.word-left/right; word deletion uses hide.edit.delete-word-backward/forward. Ctrl+Left/Right and Ctrl+Backspace/Delete retain their source defaults, with Shift extending movement. Hex retains one-byte movement/deletion; plugin and rendered Markdown views retain one-grapheme movement and refuse deletion. WordStar adds Ctrl+S/D/E/X to horizontal/vertical movement and Ctrl+Y to hide.edit.delete-line; their Ctrl+Shift variants retain the same non-extending movement or line deletion. These commands can be replaced or unbound. Ctrl+Alt+E retains the Edit menu and Ctrl+Alt+X retains Exit. Ctrl+A/F and their shifted, non-extending aliases use hide.cursor.word-left/right, so replacing or unbinding those commands also replaces or removes the WordStar aliases. Ctrl+Alt+F retains the File menu. WordStar prefix starters use hide.wordstar.block-prefix (Ctrl+K) and hide.wordstar.quick-prefix (Ctrl+Q). Their second strokes have independent wordstar-block and wordstar-quick tables, with bare, Shift, Ctrl and Ctrl+Shift letter defaults. These tables do not inherit ordinary source or macOS defaults; explicit global entries still apply. Noncharacter source controls are defaults in these tables too. Escape cancels; an unknown or unbound step consumes the prefix without typing or replaying a removed command. Hex buffers use source.
[editor.keybindings.terminal.wordstar]
"hide.wordstar.block-prefix" = ["Ctrl+J"]
[editor.keybindings.terminal.wordstar-block]
"hide.edit.copy" = ["Y"]
"hide.edit.delete-selection" = []
"hide.edit.undo" = ["Z"]Select text, then Ctrl+J Y copies it; Ctrl+J Z undoes an edit. The old Ctrl+K starter, C copy step and selected-block deletion step are removed. Block marking uses hide.selection.block-start and hide.selection.block-end. Menu labels show the effective two-stroke shortcut; inspection and frontend input use the active single-stroke table. Compound labels do not become native menu accelerators. Alt menu mnemonics and macOS Command/Option ownership retain their earlier priority.
For example, [editor.keybindings.terminal.wordstar] with "hide.file.save" = ["Ctrl+Shift+J"] replaces F2 for WordStar sources only. For example, the wordstar table can rebind movement and selection:
[editor.keybindings.terminal.wordstar]
"hide.cursor.left" = ["Ctrl+Shift+J"]
"hide.selection.left" = ["Ctrl+Shift+I"]
"hide.cursor.up" = ["Ctrl+Shift+P"]
"hide.edit.delete-line" = ["Ctrl+Shift+U"]Removing a command's list consumes its former default keys instead of replaying hardcoded editing. A global Save override using Ctrl+Shift+S must explicitly release its WordStar owners with "hide.cursor.left" = [] in wordstar and "hide.cursor.row-start" = [] in wordstar-quick. Hex and read-only Markdown/plugin windows keep their existing byte-row or displayed-text coordinate and selection owners; read-only windows cannot delete, and Delete line is only available in editable text sources.
The sidebar additionally binds Up/Down and PageUp/PageDown to row movement, Enter to activate, Right to expand, Left to collapse, and F6 to return to source. Messages uses its own row/page movement, Enter to jump to source, and F6 to leave. PTY windows retain window/build shortcuts while ordinary keys, including Ctrl+C, Ctrl+Q and Ctrl+S, reach the process. Global Ctrl character chords are omitted from PTY maps, so a global Save override such as Ctrl+Shift+S still applies to the other contexts. A mixed global list retains its transferable PTY chords. Explicit terminal-context Ctrl character assignments fail validation.
Use canonical IDs in the command catalog, with Ctrl, Alt, Shift and graphical Cmd modifiers and names such as F2, Insert, Delete, Left and PageDown. Unknown contexts or commands, malformed chords and conflicts stop configuration loading. To assign an occupied key, remove or replace its previous command's binding too. Ordinary text, menu mnemonics, window navigation, completion controls, Escape, F10 and Ctrl+] remain reserved. Conversation Enter retains the configured Query/Steer and code-block submission behavior. Dialog dialog tables accept only Copy, Cut, Paste, Select all, Undo, Redo, Find, Replace, hide.dialog.focus-next, hide.dialog.focus-previous, hide.dialog.accept and hide.dialog.cancel, plus six commands for caret-only single-line fields hide.cursor.left/right, hide.cursor.row-start/row-end and hide.edit.delete-backward/forward. Clipboard and Undo/Redo apply to editable multiline text boxes; Find/Replace apply to a search dialog. Single-line fields such as Text to find and Save As Name use their existing grapheme movement/deletion and Home/End defaults, including modifier aliases. Remapping or [] consumes the old physical keys only while that field owns focus. Ctrl+U, ordinary typing and Ctrl/Alt button mnemonics retain their existing owners. Fields with selection, multiline text boxes, dropdowns, lists and buttons retain their current navigation controls. Defaults for clipboard/search are Ctrl+C/X/V/A, Ctrl+Shift+C/X/V/A, Ctrl+Z Undo, Ctrl+Y and Ctrl+Shift+Z Redo, Ctrl+F Find, and Ctrl+H/R Replace, with the macOS Cmd counterparts. Only permitted actions are projected to native/browser accelerators for the current field. For example:
[editor.keybindings.macos.dialog]
"hide.edit.copy" = ["Cmd+Shift+J"]
"hide.edit.paste" = ["Cmd+Shift+K"]Dialog focus defaults are Tab/Alt+Tab for the next control and Shift+Tab/Alt+Shift+Tab for the previous control. Terminal BackTab uses the same Shift+Tab binding. These commands also work in single-line fields and button-only dialogs; leaving an open dropdown commits its preview. Remapping or [] removes the old focus chords. The Next status hint shows the effective key and stays clickable when unbound. For example:
[editor.keybindings.terminal.dialog]
"hide.dialog.focus-next" = ["F13"]
"hide.dialog.focus-previous" = ["F14"]Dialog Accept/Cancel defaults are Enter/Escape, including their existing modifier aliases. Accept keeps the focused control's behavior: it commits or opens a dropdown, inserts a newline in an editable TextArea, or submits the current dialog button. An approval dialog's input field cannot approve it. Cancel reverts an open dropdown; otherwise it closes the dialog through its existing cancellation owner, including permission denial. Remapping or [] consumes the old Enter/Escape routes. Status hints and frontend projections use the effective command, even when unbound. For example:
[editor.keybindings.terminal.dialog]
"hide.dialog.accept" = ["F13"]
"hide.dialog.cancel" = ["F14"]Dialog editing remaps operate on that field's buffer and undo history. Ctrl+Tab search switching, the existing permission-dialog Alt+F3 cancel alias, Ctrl+U input clearing, text, button mnemonics and permission decisions retain their control ownership. Sensitive agent/approval controls keep their human authority regardless of a remap. Source accelerators are inactive while a modal owns input.
Typed commands published through the session's menu registry can use their public menu contribution ID in the same tables. For example, an extension that publishes example.manual can bind it with "example.manual" = ["Ctrl+Shift+J"] in [editor.keybindings.terminal.source]. Contributions have no automatic shortcut; the menu's descriptive key hint does not activate a chord. Unknown IDs fail initial loading or reload. A previously loaded ID becomes inert when its registration retires; a replacement registration receives its own exact lifetime. Bindings are rebuilt on the session worker as contributions change. [] removes the effective shortcut. Remote native, terminal and browser shortcut packets retain the exact registration from their displayed frame, so an old queued shortcut cannot invoke a replacement registered under the same public ID. Native accelerators, popup labels and inspection use the focused platform/context map. Contributions cannot enter the dialog editing whitelist or grant agent authority. Bare commands without a menu contribution remain outside this binding catalogue.
Choose Options > Reload keybindings after editing TOML. Loading and validation run on the session worker; the existing map stays active until a valid replacement is ready. A failed reload reports its error and keeps that map. Changing the working directory while loading requires another reload. Recovery loads current configuration; attaching to a running session retains its map.
Options > Inspect keybindings opens a read-only buffer containing every command's effective chords for the context focused when inspection was requested. Unbound commands appear as []. Both operations have canonical IDs hide.bindings.reload and hide.bindings.inspect and can themselves be bound. Agents cannot request a reload. Put remote project settings on the remote host. Native menus display their effective accelerator with explicit modifiers; additional chords use the same input resolver. Copy/cut/paste remaps use the system clipboard. Browser keyboard clipboard defaults use browser clipboard events only while their configured action still matches. Browser Edit-menu clipboard actions remain semantic commands. Remapped clipboard requests run after the host resolves their command, so they may require the visible clipboard button when browser permissions or user activation prevent access. Browser/OS reserved shortcuts (such as Reload and macOS Hide) cannot be intercepted reliably. Plain macOS Option characters retain composed text input and cannot be assigned to commands; Cmd+Alt chords remain distinct. Local graphical scale keys remain reserved.
Ctrl+Tab and Ctrl+Shift+Tab use hide.window.next and hide.window.previous. Remapping or unbinding these commands removes their old aliases without typing into the editor or sending PTY input. F6 retains its Files/Messages focus action; dialog Tab controls and Alt+Tab focus navigation keep their existing owners. WordStar Ctrl+A/F aliases use the configurable word movement commands.
macOS Command+Tab remains owned by application switching. WordStar prefix/block grammar and the remaining field controls stay outside this command catalogue; see configurable keybindings. Caret-only single-line movement/deletion does not introduce selection, clipboard or Undo behavior for those fields.
Environment
Options > Environment… lists the running editor's environment. Select a name and Edit, or choose New. Set its value and scope, then Apply; Unset variable removes it from the environment of future processes.

- Session applies immediately and lasts until the editor process exits.
- Project saves in the project's
thc.toml. - Global saves in the shared
thc/config.toml.
[editor.environment]
PKG_CONFIG_PATH = "/path/to/library/share/pkgconfig"
OLD_BUILD_OPTION = falseStrings are literal values: $PATH, ${NAME} and ~ are not expanded. Read the current value before extending a search path; use : on macOS/Linux and ; on Windows. false explicitly unsets a variable. On startup, project entries override global entries, which override the inherited shell environment. Saving a global entry respects an existing project override. Session changes can temporarily override either.
New builds, terminals, debugger adapters and agent providers inherit the updated environment. Already running processes retain their old values: start a new job or reconnect the affected provider. There is no need to restart the editor. Agent-provider-specific environment overrides still take precedence.
Agents use environment_get and environment_set, controlled individually by Options > Agent Permissions. Credential values are redacted in tool results, and agents cannot write credential variables. Editor session/transport variables, configuration locations and loader overrides are protected from changes through this facility. Streamer mode masks the value field. Do not commit secrets in project configuration; session scope avoids writing values to disk.
For dependencies shared by the project, prefer a checked-in build configuration. This editor's cabal.project already discovers Ghostty installed under .deps/ghostty; see Installation.
Terminal file drag helper
Saved-file export in the terminal delegates to an optional installed helper. hide searches PATH for ripdrag, then dragon-drop. These helpers open a graphical window from which you drag the file to another application. A graphical display is required; installing a helper is unnecessary for ordinary editing.
To select a helper explicitly, set THC_EDIT_FILE_DRAG_HELPER before starting hide:
THC_EDIT_FILE_DRAG_HELPER=/path/to/dragon hide .The value names one executable, with no arguments, shell expansion or quoting syntax. hide passes --and-exit and one canonical absolute file path as separate arguments. A renamed compatible helper can use the same override. The bare name dragon is not discovered automatically because other applications use it. An empty override disables helper export. An unavailable executable or failed helper reports an error in hide; closing the helper cancels the interaction.
This host-owned override cannot be changed through agent environment tools or project environment settings. Set it on the machine displaying the terminal. The editor sends an authorized binary snapshot to that frontend; the helper receives a temporary local copy, including when the editor runs over SSH.
Each frontend retains at most four export copies of at most 16 MiB each. Copies remain readable until that frontend exits, even after the helper closes, so a receiving application can finish reading. Closing or detaching the frontend cancels its active helper and deletes only its own temporary copies. One helper may be active at a time; close its window before requesting another export. Helper success means its window closed, not confirmation that a drop succeeded.
Agent context
Use [editor.agent].context in either file for guidance you want supplied to conversation agents. Global text comes first, then project text. The project text adds to the global context; an empty project string adds nothing.
Options > Agent Context selects Global or Project, then Edit opens the TOML in a normal editor window with save, undo and multiline editing. Use triple-quoted TOML strings as above. Save with F2 before sending your next query or steering message. Guidance is limited to 16,384 characters per scope.
The first query after connecting or resuming supplies the skill catalog and current context. Later queries and steering messages resend context only when its saved value changes, including when it is cleared. Queued queries use the context current when dispatched. Editing context does not submit a query or interrupt a running response by itself. Invalid configuration stops submission and retains the query for repair.
Agents can read the effective text and its source paths through agent_settings. They cannot edit this configuration through file or input tools. Context is sent to the provider, so use it for guidance rather than credentials. Tool permissions remain global: a project file cannot enable tools or override Agent Permissions.
Agent limits
Set the maximum active agents in the session and the maximum direct subagents per agent in the global configuration:
[editor.agents]
max_agents = 8
max_subagents = 4These are the defaults. max_agents accepts integers from 1 to 64 and includes the main human-managed agent. max_subagents accepts integers from 0 to 64; zero prevents agents from spawning direct subagents. Both limits must allow a spawn: a free child slot does not bypass the session total.
The discovered project thc.toml may lower either global ceiling. Omitted fields inherit the global value; larger project values do not raise it. Limits are checked for future spawns. Lowering a limit does not kill agents already running, but further spawns are blocked until both limits permit them. Invalid types, out-of-range values or malformed configuration block new spawns until repaired. Existing configuration writers preserve these settings and unknown sections; there is no agent tool for changing the limits. [editor.agent] remains the separate namespace for conversation context.
Streamer mode
Turn on Options > Preferences > Streamer mode before sharing your screen, or start with --streamer. Sensitive input values and session keys are masked on every frontend; their stored values are unchanged. --no-streamer turns it off. This is a user-controlled preference: agents can read its state but cannot change it through input or settings tools.
Views supplied to agents always redact sensitive values, whether or not Streamer mode is on. Source files are not scanned for secrets by this display option.
Agent Permissions
Options > Agent Permissions saves each tool's Enable, Prompt or Disable policy:
[editor.mcp.permissions]
read_buffer = "enable"
build_output = "enable"
buffer_apply_diff = "prompt"
terminal_start = "disable"Read-only tools default to Enable; other tools default to Prompt. Omitted tools retain that default. See session tools for the available services.
The editor stays responsive while loading and saving permissions. Each dispatch, approval and prepared diff adoption checks fresh policy. Unreadable, oversized or invalid configuration rejects the tool. A permission save takes effect before queued requests proceed; closing a loading dialog prevents its late reply from reopening it. External file edits are observed on the next read, with a finite read-to-adoption interval rather than atomic revocation.
The editor preserves unrelated settings and comments when saving its own entries. Additional compiler sections can share this file as they are introduced.
ACP Warden
The optional Warden checks proposed agent actions against the current task and global/project agent context loaded at task delivery. Changed guidance applies with the next query or steer. Set startup defaults in the global configuration; project configuration cannot override them:
[editor.warden]
mode = "off" # off, observe or enforce
budgetMs = 6000 # 1..30000 milliseconds
threshold = 0.8 # provisionalThese are the defaults. The threshold accepts a finite value from 0 to 1; 0.8 is provisional, not a calibrated correctness guarantee. Options > ACP Warden… changes the running session's mode. Select its inference destination separately through Tools > System One supplier…; see System-1 decisions. Agents cannot change either choice.
Off does no inference. Observe takes one bounded asynchronous sample at a time and skips busy work, without delaying or vetoing the action. Enforce requires a current judgment for the exact task, rules and action before editor MCP or native ACP filesystem/terminal effects. It cannot enable a disabled tool or replace human approval.
Task, rule text and action arguments go to the human-selected supplier. Known private values and oversized inputs refuse judgment. Enforce holds failed or stale judgments and requests without a supplier. A human-requested review also sends bounded recent outcomes and an available completed reply to that supplier; it prepares advice for you to edit and send. It never sends steering on its own. See conversations for the review, activity display and limits.
Autocomplete
Completion settings are independent of the main conversation. Choose them in Options > Autocomplete, or set global defaults and project overrides:
[editor.autocomplete]
provider = "acp" # off, acp, or copilot
executable = "codex-acp"
arguments = "[]" # JSON array of arguments
model = ""
effort = ""
copilotExecutable = "copilot-language-server"
copilotArguments = '["--stdio"]'
debug = false
contextRanking = "off" # off, local, or selected; ACP only
contextRankingBudgetMs = 6000An empty model or effort uses the ACP provider's default. Set debug = true to show the completion conversation in the bottom panel; ACP accepts intent hints there. Completion stays off until a provider is selected. The Options dialog updates the project table if it already exists, otherwise global settings. A project value in thc.toml takes precedence. Agents cannot change these settings or complete their own authentication.
Optional Context ranking (ACP) uses the System-1 supplier to choose up to two additional blocks from the same file. Host only (local) keeps ranking inside the editor process. Selected supplier (selected) also allows an endpoint or a connected browser selected through Tools > System One supplier…. The default is Off. Protected source files are ineligible for autocomplete.
The ranker sees short descriptors of bounded blocks, not the whole file. Blocks containing known private values are excluded; private local context skips ranking. Current local context and recent edits stay intact, and additional snippets are read-only: the completion agent can still propose edits only within its ordinary nearby range. A busy, unavailable or late ranker falls back to that ordinary context. The budget defaults to 6,000 milliseconds, permits 1–10,000, and includes model acquisition. The first request loads the model; later requests reuse it. Set a shorter budget if prompt fallback matters more than waiting for a cold model. Ranking runs on the completion worker; moving or editing cancels the pending selection. A load that exceeds the budget is canceled too; increase the budget before retrying. A browser cold start may need more than the default.
Copilot keeps its real document and cursor protocol. Its current interface has no additional-snippet field, so this setting affects ACP only.
System-1 decisions
Plugins can submit small classification and ranking questions to in-process Laya, a selected System One endpoint, or a connected browser’s WebGPU worker. This is separate from the conversational agent: it returns probabilities, not edits or commands. The consumer decides what to do with them.
Select the destination in the global configuration:
[editor.systemOne]
provider = "endpoint" # off, endpoint or laya
endpoint = "http://127.0.0.1:8008/v1/systemone"
model = "kev-latest"
tokenEnv = "" # optional, e.g. SYSTEM_ONE_TOKENThe default is off. Project configuration cannot override the destination. Selecting an endpoint does not connect until a plugin requests a decision. The URL must omit credentials, query and fragment; redirects are refused. A bearer variable must have a sensitive name such as SYSTEM_ONE_TOKEN or SYSTEM_ONE_SECRET, so the existing environment tools redact its value and refuse agent changes. A request marked host-process-only cannot use an endpoint, even on localhost.
Each request has a deadline of at most 30 seconds. The service admits one request at a time, rejects additional work as busy, and retains the slot until canceled work has finished releasing its resources. Changing the supplier expires pending results; it never forwards their context to the replacement. State is limited to 64 KiB of UTF-8, with 128 KiB across state, names and questions. Inputs that exceed a limit are refused rather than shortened.
To keep inference in the editor process, build the optional native Laya provider and select an immutable model bundle by its manifest digest:
[editor.systemOne]
provider = "laya"
bundle = "/absolute/path/to/laya-bundle"
manifestSHA256 = "<64 lowercase hexadecimal characters>"
allocationLimitBytes = 3221225472 # 3 GiB of tracked model/tensor allocations
threads = 4 # 1..8The first decision verifies the manifest and every payload before loading. The provider retains the tokenizer and model until selection changes or the session ends. The allocation envelope covers ORT model/tensor storage, not whole-process RSS. Unsupported or overlong token sequences are refused; input is never silently truncated. A build without native Laya reports that the provider is unavailable rather than sending its context elsewhere.
Tools > System One supplier… changes the running session's supplier. Choose Off, the supplier from global configuration, or the current browser's offer. Opening the menu does not load a model. Selection applies only to this session; edit the global configuration above to change the startup default.
A browser offers inference only when its local launcher has the optional runtime and model assets. The session owner must select that offer before any decision context is sent. Reconnecting or switching sessions retires the old offer; choose the new offer explicitly. A host-process-only request never goes to the browser. Browser assets are served by the local frontend, including when the editor session is on an SSH host.
Browser allocation limits cover owned WebGPU buffers, not the JavaScript/WASM heap or the whole browser. The worker verifies the model manifest and payloads, retains its model between requests, and drains active inference before reporting cancellation. Closing a connection expires its requests without claiming that the disconnected machine has stopped computing.
An endpoint's model name is reported provenance, not proof of its weights. Probabilities and confidence retain the provider's meaning. A consumer must apply its existing privacy and permission rules before submitting context, and judge whether the selected model is useful for its particular decision.