>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3588796. --> Reported by: [ajv009](https://www.drupal.org/user/3653917) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The migrate-site statusline displays session analytics (dollar cost, token usage, phase progress) injected into the Claude Code status bar. It is currently configured only in <code>.ddev/claude-code/.claude-seed.json</code>, so it appears in DDEV mode but not when <code>migrate.sh</code> runs in host mode (<code>exec claude ...</code>). In host mode, Claude reads <code>.claude/settings.json</code> from the project root, which has no <code>statusLine</code> entry, so no statusline appears.</p> <p>This issue is blocked-on-decision. Two source documents contradict each other on whether the gap is a defect or a deliberate design choice:</p> <ul> <li><strong>FOR_LATER Issue #1</strong> treats the host-mode gap as an oversight and proposes a one-line fix: add a <code>statusLine</code> block to <code>.claude/settings.json</code> pointing at the existing <code>migrate-statusline.mjs</code> script. The script already uses <code>stdin.workspace.current_dir</code> to resolve <code>docs/migration/</code> paths, so it works from any cwd. Blast radius is described as tiny &mdash; one file, one key.</li> <li><strong>UNSORTED Thread 1</strong> (verbatim user note, written later): "Have a custom claude status bar plugin, that inject our session analysis into it, like dollar cost, tokens being eaten, and so on. SO available for the ddev version. NOT for host as it will be system wide issue." That is, project-level <code>.claude/settings.json</code> would cause the migrate-site statusline to render in every Claude Code session run from within this project's filesystem on the host machine.</li> <li><strong>CLAUDE.md</strong> establishes original design intent: "DDEV-only by design."</li> </ul> <p>Applying FOR_LATER's proposed fix without confirmation risks making a system-wide change the user explicitly said they did not want. Declining to do it risks leaving a real gap open. The cost of the wrong choice is zero functional harm but potentially surprising statusline behavior in every Claude Code session on the host.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Run the migrate-site skill via <code>migrate.sh</code> in host mode (no DDEV).</li> <li>Observe the Claude Code status bar.</li> <li>Expected (per FOR_LATER #1): statusline shows session analytics. Actual: no statusline appears.</li> <li>Compare to a DDEV-mode run, which does show the statusline because <code>.ddev/claude-code/.claude-seed.json</code> sets it up.</li> </ol> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Do not begin implementation until the user clarifies intent. The blocking question is:</p> <blockquote><p>FOR_LATER Issue #1 proposes adding a <code>statusLine</code> block to <code>.claude/settings.json</code> to show the migration statusline in host mode. The UNSORTED note says "NOT for host as it will be system wide issue." Which is your current intent: DDEV-only (close this issue), or extend to host mode (apply the one-line fix)?</p></blockquote> <p>If the user says <strong>DDEV-only</strong>: mark this issue closed/declined. No file changes.</p> <p>If the user says <strong>host-mode wanted</strong>: add the following block to <code>.claude/settings.json</code> (verbatim from FOR_LATER Issue #1):</p> <pre>"statusLine": { "type": "command", "command": ".ddev/claude-code/statusline/migrate-statusline.mjs", "padding": 2, "refreshInterval": 5 }</pre><p>The DDEV seed config can stay as a fallback (project settings override user settings in Claude Code's precedence hierarchy).</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Ask the user the blocking question above and obtain explicit direction.</li> <li>If DDEV-only is confirmed: close the issue with a note that the contradiction has been resolved in favour of UNSORTED Thread 1.</li> <li>If host-mode is wanted: apply the <code>statusLine</code> block to <code>.claude/settings.json</code>.</li> <li>Verify in host mode that the statusline appears during a <code>migrate.sh</code> run.</li> <li>Verify behaviour matches the user's expectation in non-migrate-site Claude Code sessions launched from this project root (either no statusline, or user accepts the system-wide appearance).</li> <li>Update <code>CLAUDE.md</code> to remove the "DDEV-only by design" line if the host-mode path is taken, so future readers do not re-open this contradiction.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>If the host-mode path is taken: the migrate-site session analytics statusline (dollar cost, token usage, phase progress) becomes visible in the Claude Code status bar during host-mode runs, and potentially in every other Claude Code session launched from within this project root. Otherwise: none.</p> <h3 id="summary-api-changes">API changes</h3> <p>None.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None.</p> <h3 id="summary-internal-references">Internal references</h3> <ul> <li>Source markdown: <code>RESEARCH-2026-04-28/99-final/ISSUES/Sprint-7-Organizational-Debt/01-P2-11-statusline-host-mode-conflict.md</code> (id: P2-11)</li> <li>FOR_LATER Issue #1 (proposes the fix): <code>RESEARCH-2026-04-28/00-existing-issues/for-later-issues.md</code></li> <li>UNSORTED Thread 1 (opposes the fix): <code>RESEARCH-2026-04-28/00-existing-issues/unsorted-issues.md</code></li> <li>Tension documented: <code>RESEARCH-2026-04-28/99-final/consolidated-issues.md</code> &sect; "Issues That Contradict / Complicate &mdash; Tension 1"</li> <li>Current statusline config: <code>.ddev/claude-code/.claude-seed.json</code></li> <li>Project settings target: <code>.claude/settings.json</code></li> <li>Statusline script: <code>.ddev/claude-code/statusline/migrate-statusline.mjs</code></li> </ul> <h3 id="summary-open-questions">Open questions</h3> <ul> <li><strong>BLOCKING &mdash; do not begin work until resolved:</strong> Is the user's current intent DDEV-only (close this issue) or extend to host mode (apply the one-line fix)? The UNSORTED note was written after FOR_LATER #1 and appears to be the more recent settled intent, but explicit confirmation is required because the FOR_LATER fix would make a project-wide change the user may not want.</li> <li>If host-mode is chosen: does the user accept that the migrate-site statusline will render in every Claude Code session launched from inside this project root, not just during <code>migrate.sh</code> runs?</li> </ul>