Settings and reference

Guide index

Arrange the workspace and adjust its appearance here, or use the reference sections for shortcuts, profile locations, backups and advanced settings.

Contents

• Arrange the workspace
• Theme and terminal appearance
• Session history and task durations
• Keyboard and pointer reference
• Profiles and storage
• Back up the right data
• Advanced preferences
• Use the System Log
• Understand local and external data
• Prepare a useful problem report

Arrange the workspace

Logonomic remembers your panel layout and window position between starts.

Show and hide panels

Use Show Sidebars/Hide Sidebars in the title bar to give your current view more room. To collapse just one side panel, click its title or — button; click the title or + to expand it. Scroll the side column to reach panels that do not fit.

Title-bar shortcuts reopen Timeline, Worktree, Search, Tracked Files Treemap, Paths and Token Usage. Closing these views keeps their underlying data. System Log stays available as a tab.

Closing a terminal can end its session, and closing a modified file can ask you to save or discard edits. Their close actions are covered in Terminals and Git, files and diffs.

Move side panels

Drag a panel's title to another position or side column, then release at the insertion marker. Alternatively, press Ctrl+E to show arrow buttons in the panel headers. Use them to move panels up, down or into an adjacent column; press Ctrl+E again to hide the buttons.

Arrange middle tabs and splits

Drag a tab along its strip to reorder it, into another group to move it, or onto an edge or split target to place views beside or above each other. The highlighted target previews the placement. Drag the dividers to resize the views.

A terminal keeps running as you move it or switch to another tab. If a saved view refers to a file or repository that has moved, correct the path and reopen the view from its usual action.

Terminal Overview has separate grouping, tile size and arrangement controls. See Terminals to arrange its tiles or restore their automatic layout.

Window controls and full screen

In terminal Overview, press F11 to enter or leave full screen, or use the exit control at the top edge. Esc remains available to the terminal. Outside Overview, Esc exits ordinary full screen.

Theme and terminal appearance

Open the title-bar Settings gear. Beside Theme, choose the sun button (Light) or moon button (Dark). The selected button is highlighted. Logonomic saves the choice in the active profile. Double-clicking the animated application mark also toggles the theme.

In the same Settings menu, open Terminal settings (all terminals) to change fonts, colors, cursors, scrollback and input behavior across terminals. See Terminals for the individual settings.

The initial Copy on selection (default) is off and its choice is saved. A live terminal's Copy on selection (this terminal) overrides that default for the live run; see Selecting and copying.

To give provider accounts distinct colors across launchers, sessions, usage and the timeline, use the account controls in Launchers, accounts and add-ons.

Session history and task durations

The Settings gear provides Retained sessions, Default implementation duration and Default review duration. Edit a value and press Enter or Apply. The information button beside each value opens its explanation. An error appears beside the setting if it cannot be saved.

Retained sessions defaults to 1000 stopped sessions. Interrupted sessions keep their context and messages under this count even when they cannot resume. Applying a lower count removes the oldest eligible stopped sessions. Live sessions and context needed by retained tasks or native cleanup are protected, so the retained count can exceed the setting. 0 keeps only protected context. Timeline history has its own retention.

Implementation tasks default to 30 minutes and review tasks to 5 minutes. Choose a whole number of minutes, seconds or milliseconds. Settings displays the largest unit that represents the saved duration exactly; use milliseconds for any value from 1 through 2147483647. Applying a new default affects new structured tasks. An admitted task keeps its chosen duration, and an explicit per-task duration takes precedence.

A disabled, malformed or unsupported duration setting stays unavailable and shows the reason. An explicit valid task duration remains available. Other purpose settings and optional data remain independent. The file settings remain available; see Advanced preferences.

Session recording and Git attribution

In the Settings menu, below Terminal settings (all terminals), use Record local resume identities and Ask agents to add Git session trailers. The switches are independent and both on by default.

The information button beside each switch opens the Local resume identities or Git session trailers explanation. Closing the explanation returns to Settings.

Local recording keeps provider-confirmed identities for exact resume without changing Git messages. Git attribution keeps identities for commit links when Git supports trailers. With local recording off, usable Git attribution still keeps new identities; if Git attribution is unavailable, enable local recording to keep them independently. Turning both off stops automatic recording for new sessions. Existing records and explicit exact resume remain available.

Trailer instructions are given to newly launched agents. A running agent keeps the instructions it already received, but its authenticated attribution query applies the current setting before each commit. If identity storage is unavailable, Settings reports the problem, refuses the change, and shows the saved values again. Resolve the storage problem first. These switches do not delete existing records.

Keyboard and pointer reference

Keyboard shortcuts act on the focused area. Click the terminal, editor or view you intend to use first.

For more inputs, see terminal controls, editor and diff controls, timeline navigation, or mobile gestures.

Profiles and storage

A Logonomic profile holds your settings, history, notes, integrations and local state. All installations use the same default profile unless you select another one at startup.

Default profile

On Windows, configuration files, layout, text logs, discovery settings, notes and orchestration data are stored under:

%LOCALAPPDATA%\Varinomics\Logonomic\

Application preferences also use the registry:

HKEY_CURRENT_USER\Software\Varinomics\Logonomic

On Linux, the default locations are:

XDG_CONFIG_HOME, XDG_DATA_HOME and XDG_CACHE_HOME replace the corresponding .config, .local/share and .cache base directories when set. Use those actual locations when backing up or restoring your data.

Separate profiles

Both retail editions, Logonomic and Logonomic Pro, support separate profiles.

Start Logonomic with an absolute profile path:

& 'C:\Program Files\Varinomics\Logonomic\logonomic.exe' `
    --user-data-dir 'C:\Users\your-name\Logonomic Profiles\Work'

For a Linux .deb installation:

/opt/varinomics/Logonomic/logonomic --user-data-dir /home/your-name/logonomic-profiles/work

For an AppImage, pass the same option after the AppImage's filename.

The form --user-data-dir=<absolute-directory> also works. Supply the option once; a repeated option, relative path or missing argument is an error. Logonomic creates the directory if needed.

To use the profile from a Windows shortcut, add the option after the executable in its Target field and quote paths containing spaces. Include the option each time you start that workspace: omitting it opens the default profile. Logonomic Free always uses the default profile.

An explicit profile contains:

A new, empty profile starts with empty Logonomic settings and history. It does not copy them from the default profile.

Windows profile permissions

Choose a local directory protected for your Windows user, preferably within your personal storage. Network shares and shared writable directories are not accepted. Logonomic also checks ownership, access permissions and path redirection.

If a profile path is rejected, read the reported path and permission error. Use a protected user directory rather than granting broader access.

What profiles do and do not isolate

Separate profiles let you keep work contexts apart or try a clean configuration. They still act on the repository directories you select: two profiles using the same worktree can change the same files.

External tools also keep their own accounts and profiles. To use a different provider account, configure it through the launcher; changing Logonomic profiles does not sign the external tool out.

Back up the right data

Make a profile backup

1. Save your work, end terminal sessions and close Logonomic. End any sessions still running in Soter as well. A filesystem backup cannot preserve a live shell, and copying active stores can capture inconsistent data.

2. Copy the data for the profile you use:

   • Default Windows profile, including Logonomic Free: copy %LOCALAPPDATA%\Varinomics\Logonomic\. In Registry Editor, export the HKEY_CURRENT_USER\Software\Varinomics\Logonomic branch alongside it.
   • Default Linux profile, including Logonomic Free: copy both the Logonomic configuration directory and Logonomic.conf preferences file from the locations above, plus the Varinomics/Logonomic data directory.
   • A separate profile: copy its config, data, local-data and settings folders together, preserving their layout beneath the profile root.

3. Record the edition, application version and original locations with the backup. Preserve repository files and provider histories separately.

Caches and runtime state are recreated by the application; they are not needed to restore saved work.

Restore a profile backup

Use a complete backup made while Logonomic was closed. On the same computer and user account:

1. Close Logonomic and end its terminal sessions. Keep a backup of the current files and preferences before replacing them.
2. Restore each backed-up directory or file to its original location, replacing that directory as a whole instead of mixing files from different backups. Preserve the user-only access permissions. For a default Windows profile, replace the Logonomic registry branch with its saved export using Registry Editor; preserve the current branch first.
3. Start Logonomic with the profile you restored. For the default profile, including Logonomic Free, start normally without --user-data-dir. For a separate profile, use its usual --user-data-dir argument.
4. Check your notes, launchers and saved sessions. If the restored data cannot be read, close Logonomic, retain the backup and error details, and contact support.

Keep backups private: they may contain prompts, notes, repository paths, diagnostics and account information. Moving a backup to another computer or user account can make machine-protected records unusable. Reconnect affected services through their normal setup procedures; copying a profile does not transfer a desktop activation.

Restore a token-usage export

For a copy listed in Token Usage's Saved usage history…, follow Restore saved usage in the current profile. That recovery works in every edition, including Logonomic Free, without creating another profile.

For a command-line token-usage recovery export, follow Make or restore an external backup. This targeted backup excludes notes, sessions and external CLI credentials. Retail editions restore into a fresh profile and open it with --user-data-dir. Logonomic Free restores into a working copy inside its fixed profile after preserving the previous configuration. Close Logonomic and its surviving runtime owners first, then start normally after restoration succeeds. The complete filesystem-backup procedure above remains available in every edition.

Advanced preferences

Use the on-screen controls for everyday choices such as discovery paths, launchers, account colors, terminal settings and Companion pairing. The settings below are intended for more specific configuration and diagnosis.

Application preference storage

For a separate profile in either retail edition, preferences live in:

<profile>/settings/Varinomics/Logonomic.ini

The default profile uses the Windows registry or Linux Logonomic.conf path listed above. Close Logonomic before making manual changes, then restart it.

Observation intervals accept integers from 1 to 86,400,000 milliseconds (24 hours). Invalid values produce a configuration error. Short intervals increase work; they do not make network refreshes or UI operations finish within that time.

For example, this INI configuration keeps text logs for 60 days and preserves the Git wrapper on PATH:

[logging]
text_log_retention_days=60

[git]
prefer_direct_binary=false

In the default Windows profile, create the corresponding values under HKEY_CURRENT_USER\Software\Varinomics\Logonomic: text_log_retention_days in the logging subkey and prefer_direct_binary in the git subkey. Removing an override restores its default at the next start.

Stopped-session retention

The retention setting is stored separately:

<configuration-directory>/orchestration/settings.ini

For an explicit profile, use <profile>/config as the configuration directory. Logonomic creates the file at the first retention check.

[orchestration]
history_session_limit=1000

This is a non-negative count of stopped sessions. Setting it to 0 retains only protected context. Live sessions and protected current context can exceed the budget. A change applies at startup or the next session update that checks retention.

Invalid settings or failed writes preserve history and produce a diagnostic. Before lowering the limit, read Sessions and coordination. The setting does not change provider conversation retention, diagnostic logs, usage totals or the timeline's separate execution history.

Saved interface choices

Logonomic saves theme, window geometry, panel arrangements and per-view choices automatically. Use the UI to adjust them, including Logonomic's own terminal settings.

Interface state is held in the active profile's ui_state.json. Editing it while Logonomic is running can lose your changes when the application next saves. For launcher, add-on and session configuration, use the procedures in Launchers, Sessions and Command reference.

Use the System Log

Open System Log for application errors, failed commands and storage diagnostics. Session Log lists session activity and diagnostics. Conversation text and command output belong in the terminal; Session Log is not a transcript.

Filter messages

Enter text in Filter to narrow the visible messages. When several streams are available, use the stream selector to choose one.

The Level selector includes the selected level and all levels above it in this table:

Logonomic remembers your selection. If an expected message is missing, clear the text filter, check the stream and broaden the level.

Follow, wrap, copy and open

• Toggle auto-scrolling to the latest entry follows incoming messages. Scroll away to inspect older output, then re-enable it to follow again.
• Toggle line wrapping fits long messages to the panel.
• Clear the log view clears the displayed entries.
• Copy selected logs to clipboard copies selected rows.
• Open the full log file opens the selected stream's complete log as a document.

Diagnostic text logs live in the active configuration directory. The default retention is 30 days, with pruning at startup. Logs still in use by a running process are kept.

Understand local and external data

Logonomic keeps workspace information locally, including repository paths, launcher configuration, session metadata, usage and notes. The tools you run can keep their own histories and credentials elsewhere.

Git operations contact your configured remotes; hosting integrations contact GitHub or GitLab; agent and quota actions use the selected provider. Companion shares workspace information with a paired device and uses a relay service when you choose a relay connection.

Removing local configuration does not remove the thing it refers to. Removing a discovery path leaves the repository on disk; removing a launcher leaves its executable installed. Forgetting a session removes its Logonomic history, while the provider's conversation remains under the provider's controls.

Prepare a useful problem report

Include enough detail to reproduce the problem:

1. Logonomic edition, version and operating system. Run your Logonomic executable with --version to print its version.
2. Whether you use the default profile or --user-data-dir.
3. The action, selected repository/worktree and provider involved.
4. The exact error or disabled-action tooltip and the time it appeared.
5. The shortest sequence of steps that reproduces it.
6. Relevant System Log entries and terminal output.

For startup failures, copy the displayed summary and details. After a crash, describe which original terminals are available in Soter and include any diagnostic location named by Logonomic. See Recovery and troubleshooting.

Review logs and screenshots for private paths, prompts, notes, account labels and command arguments before sharing them. Send the relevant entries rather than authentication files or an entire profile.