🎯 Use case
This file lives under “utils/”, which covers cross-cutting helpers (shell, tempfiles, settings, messages, process input, …). On the API surface it exposes getStandaloneAgentName — mainly functions, hooks, or classes. It composes internal code from state and teammate (relative imports). What the file header says: Standalone agent utilities for sessions with custom names/colors These helpers provide access to standalone agent context (name and color) for sessions that are NOT part of a swarm team. When a session is part of a swarm, these functions return undefined to let swarm context take.
Generated from folder role, exports, dependency roots, and inline comments — not hand-reviewed for every path.
🧠 Inline summary
Standalone agent utilities for sessions with custom names/colors These helpers provide access to standalone agent context (name and color) for sessions that are NOT part of a swarm team. When a session is part of a swarm, these functions return undefined to let swarm context take precedence.
📤 Exports (heuristic)
getStandaloneAgentName
🖥️ Source preview
/**
* Standalone agent utilities for sessions with custom names/colors
*
* These helpers provide access to standalone agent context (name and color)
* for sessions that are NOT part of a swarm team. When a session is part
* of a swarm, these functions return undefined to let swarm context take
* precedence.
*/
import type { AppState } from '../state/AppState.js'
import { getTeamName } from './teammate.js'
/**
* Returns the standalone agent name if set and not a swarm teammate.
* Uses getTeamName() for consistency with isTeammate() swarm detection.
*/
export function getStandaloneAgentName(appState: AppState): string | undefined {
// If in a team (swarm), don't return standalone name
if (getTeamName()) {
return undefined
}
return appState.standaloneAgentContext?.name
}