Agent/Fleet view: submitted message does not appear after navigating with left-arrow

[Vit129]

Bug: Message sent in Chat view does not appear in Agent/Fleet view

Description

After typing a message in Chat view and pressing Enter to submit it, pressing ← (left-arrow) to navigate to Agent/Fleet view does not show the message/job that was just submitted.

Steps to reproduce

1. Open a new session in Claude Code CLI (Chat view)
2. Type a message
3. Press Enter to submit
4. Press ← to navigate to Agent/Fleet view

Expected behavior

The just-submitted message/session should appear as an active job in Agent/Fleet view.

Actual behavior

The message does not appear in Agent/Fleet view. Reproducible 100% of the time.

Environment

• Claude Code CLI 2.1.220
• macOS 27.0 (Darwin 27.0.0)

[Vit129]

Found the root cause by inspecting strings in the installed CLI binary (~/.local/share/claude/versions/<version> — largely un-obfuscated JS).

The Fleet/Agent view session enumeration function (minified as fcl in the bundle) does this:

function fcl(e,t){
  try {
    let r=gn(), n=await BRe(r);
    return (await nbr(n,void 0,t?K7S:void 0)).flatMap((s)=>{
      if(!s.sessionId||!s.fullPath) return [];
      if(e.has(s.sessionId)) return [];
      if(!t && s.sessionKind==="bg") return [];   // <-- drops background-kind sessions
      return [{sessionId:s.sessionId, fullPath:s.fullPath, ...}]
    })
  } catch(r){ ... }
}

t is fed by the remote feature flag tengu_fleet_past_sessions (cached in ~/.claude.json). When that flag is false for an account, any session with sessionKind: "bg" — which is what a just-submitted/processing session gets tagged as — is silently filtered out of the Fleet/Agent view list. That's why the just-submitted message never shows up after pressing ←: it's not a race/timing bug, it's a deterministic filter, 100% reproducible as long as the flag stays off.

Workaround confirmed working: manually flipping "tengu_fleet_past_sessions": false → true in ~/.claude.json and restarting the CLI made submitted sessions appear in Fleet/Agent view as expected. Caveat: since this is a server-synced flag, it may get overwritten back to false on a future config refresh.

This looks like either (a) an intentional partial rollout where the Fleet view is expected to hide background sessions unless this flag is on — in which case the UX is broken for accounts where it's off and messages just silently disappear with no indication, or (b) the flag is meant to be on by default and something is misconfigured for a subset of accounts. Either way, filtering out sessionKind:"bg" sessions with zero user-facing indication (no "N background sessions hidden" note, nothing) is the actual bug.