coilyco-flight-deck/agentic-os

Fork 0

warp doctor: settings.toml content drift on live-state fields (zoom_level, cloud_conversation) #224

New issue

Closed

opened 2026-06-16 20:19:54 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-06-16 20:19:54 +00:00

Owner

Context

While disabling ssh warpification (commit e2b0e2b), ward exec warp apply replaced the Preview ~/.warp-preview/settings.toml symlink with a real file (resolving the prior "must be a real file" doctor FAIL). With a real file now in place, ward exec warp doctor compares content and reports a new FAIL:

FAIL  settings.toml - content drifted from canonical template: /Users/kai/.warp-preview/settings.toml

Root cause

The running Warp persists live UI state back into settings.toml, diverging from the hardcoded template:

zoom_level - template pins 150, Warp wrote Kai's live 125.
cloud_conversation_storage_enabled - already documented in the template as a Warp-rewrites-on-launch field (PENDING note).

These are volatile, Warp-owned fields. Pinning them in the managed template guarantees perpetual doctor drift.

Options

Drop zoom_level (and other live-UI fields) from the managed template, letting Warp own them; doctor should ignore Warp-owned volatile keys.
Or teach warp doctor an allowlist of volatile keys to skip during content comparison.

Not blocking

The ssh-warpification fix is landed and correct; this is pre-existing host drift, only now visible because the file became real.

## Context While disabling ssh warpification (commit e2b0e2b), `ward exec warp apply` replaced the Preview `~/.warp-preview/settings.toml` symlink with a real file (resolving the prior "must be a real file" doctor FAIL). With a real file now in place, `ward exec warp doctor` compares content and reports a new FAIL: ``` FAIL settings.toml - content drifted from canonical template: /Users/kai/.warp-preview/settings.toml ``` ## Root cause The running Warp persists live UI state back into settings.toml, diverging from the hardcoded template: - `zoom_level` - template pins `150`, Warp wrote Kai's live `125`. - `cloud_conversation_storage_enabled` - already documented in the template as a Warp-rewrites-on-launch field (PENDING note). These are volatile, Warp-owned fields. Pinning them in the managed template guarantees perpetual doctor drift. ## Options - Drop `zoom_level` (and other live-UI fields) from the managed template, letting Warp own them; doctor should ignore Warp-owned volatile keys. - Or teach `warp doctor` an allowlist of volatile keys to skip during content comparison. ## Not blocking The ssh-warpification fix is landed and correct; this is pre-existing host drift, only now visible because the file became real.

coilysiren added the

label

2026-06-17 07:04:24 +00:00

coilysiren added

and removed

labels

2026-06-17 08:39:10 +00:00

coilysiren added the

consult

label

2026-06-18 06:16:41 +00:00

coilysiren commented

2026-06-18 06:42:13 +00:00

Author

Owner

Goose triage - 2026-06-17

Tier: P3 (score 68) - P2 priority: real backlog issue needing action
Mode: consult - Ambiguous root cause requires product decision on volatile key handling

_{Auto-generated by ward exec goose-triage (qwen3-coder:30b), edited in place on each run. Labels are the conclusion; this is the why.}

**Goose triage** - 2026-06-17 - **Tier:** `P3` (score 68) - P2 priority: real backlog issue needing action - **Mode:** `consult` - Ambiguous root cause requires product decision on volatile key handling <sub>Auto-generated by `ward exec goose-triage` (qwen3-coder:30b), edited in place on each run. Labels are the conclusion; this is the why.</sub>

coilyco-ops added

headless

and removed

consult

labels

2026-06-24 06:13:20 +00:00

coilyco-ops commented

2026-06-24 06:28:18 +00:00

Member

🔒 Reserved by ward agent --driver claude — container ward-agentic-os-issue-224-claude-fbfe3909 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-06-24T06:28:16Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `ward-agentic-os-issue-224-claude-fbfe3909` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-06-24T06:28:16Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-06-24 06:36:33 +00:00

fix(warp): doctor skips Warp-owned volatile settings keys

coilysiren closed this issue

2026-06-24 06:36:33 +00:00

coilysiren referenced this issue from a commit

2026-06-24 06:36:33 +00:00

Merge issue-224: warp doctor volatile settings keys (closes #224)