[BUG] Session Logging/Allow Session Sharing re-enabled for all hosts

[termix-github-bot]

Platform

linux

Version

2.8.0

The Problem

The toggles for Session Logging/Allow Session Sharing automatically re-enable on every host. I have also confirmed this is not a graphical bug - my shell history is being logged.

Within admin settings, i have disabled the following:
Allow Session Sharing
Command History
Session Logging
Command History
(the admin settings toggles correctly remain disabled)

How to Reproduce

1. Edit any host
2. Disable toggles for Session Logging / Allow Session Sharing
3. Update Host
4. Edit host again and see the toggles have re-enabled

---

Note

Submitted via the Termix Discord Support Bot
Reported by sickboy227 on Discord
View Discord thread

[termix-triage-bot]

Auto-triage

The toggles for Session Logging and Allow Session Sharing on individual hosts automatically re-enable after being disabled and saved, causing session logs to continue being written despite user settings.

Field	Value
Type	Bug
Difficulty	3/5 (Moderate)
Priority	Urgent
Labels	bug ssh security platform-linux platform-docker

A maintainer will review shortly. If the auto-classification looks wrong, feel free to say so.

[ssladmin22]

Termix 2.8.0, Docker. Same UI symptom as #1356 but for Session Logging, and with real effect: after setting Session Logging off on a host and saving (and with Host Defaults → Session Logging off, instance-wide Session Sharing and Command History off), reopening the host shows the toggle on, and new .cast files are still written to /app/data/session_logs// for every terminal session (verified by echo marker text found in the new file). A newly created host shows the same behavior. There is no instance-wide control or env var to disable session logging. Request: fix the per-host persistence/initialization, and add an admin-level kill switch (like Command History) and/or an env var to disable session recording.

[termix-triage-bot]

This has been fixed and shipped in release-2.9.0-tag. Updating to the latest release will get you this fix. Thanks for the report!