Skip to content
Hansardhansard

Harness settings

Open Settings → Harnesses in the local viewer to inspect the user-level configuration of Codex, Claude Code, Grok Build, Antigravity, and OpenCode. The page compares memory and history cleanup for detected harnesses. Expand a harness to see its other settings, then Sources and details for configuration paths, setting keys, and defaults.

Read the values

Section titled “Read the values”
  • Configured means the value was read from a supported local setting.
  • Documented default identifies a known default when that setting is absent.
  • Unknown means the setting could not be determined. Missing support, unreadable configuration, and unsupported syntax do not imply that a feature is disabled or that history is retained indefinitely.

Configuration file paths and setting names identify where to make changes. Use Refresh after editing a provider’s configuration. The page reads live configuration and does not require an archive reimport.

These are user-level settings on the device running the viewer. A running agent can use different values because of project configuration, profiles, environment variables, session flags, app preferences, or managed policy. The page does not modify provider settings, launch agents, or return raw configuration files. It is available through local viewer connections, including local read-only viewers.

Retention and memory

Section titled “Retention and memory”

Claude Code’s local transcript cleanup period defaults to 30 days. Its auto memory files are excluded from the age-based sweep. In Claude Code 2.1.248 and later, Desktop and Cowork transcripts have a separate retention setting; managed policy can override it. See the Claude Code application data reference for current rules and version qualifications.

Codex local memory generation requires the memories feature to be enabled. An empty Hansard memory view can mean that Codex has not generated memory files yet. The page distinguishes the feature switch from the settings that control memory generation and use. See Codex memories.

Provider retention affects what remains available for a future import. Hansard keeps sessions it has already archived even when the provider deletes the originals. Run a full initial import and keep the watcher running to capture new history before it is pruned.