メニュー
When rendering UI that depends on whether a project is "active" or "stopped" — buttons, badges, conditional sections. The `project.status` DB field is stale after server restarts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
How the multi-backend adapter system works — AgentAdapter interface, ACP protocol, session resume, and how to add new provider adapters
When debugging why an agent has the wrong provider/model, or when modifying agent creation or delegation flows.
How to get agents to use group chats for peer coordination in flightdeck-based crews. Covers hub-and-spoke anti-pattern, auto-grouping triggers, and file-lock-linked groups. Use when setting up multi-agent crews with 3+ agents or diagnosing why agents aren't collaborating directly.
When fetching from the `/coordination/activity` API and you only need specific action types (e.g., `progress_update`, `task_completed`, `delegated`).
When fetching activity data for UI display, or debugging why activity-based features show empty/stale data.
Architecture decisions and patterns from Flightdeck development (Phases 2–4). Covers feature architecture, state management, component patterns, and API design.
| name | project-status-live-computation |
| description | When rendering UI that depends on whether a project is "active" or "stopped" — buttons, badges, conditional sections. The `project.status` DB field is stale after server restarts. |
When rendering UI that depends on whether a project is "active" or "stopped" — buttons, badges, conditional sections. The project.status DB field is stale after server restarts.
The projects table has a status field ('active', 'stopped', 'archived'), but it can become stale. After a server restart, reconcileStaleSessions() marks sessions stopped, but the project-level status field may not be updated consistently. This means project.status === 'active' can be true even when zero agents are running.
projectStatusProps()The projectStatusProps() function in packages/web/src/components/ui/StatusBadge.tsx computes effective status from real-time agent counts:
import { projectStatusProps } from '../ui/StatusBadge';
const effectiveStatus = projectStatusProps(project);
// effectiveStatus.variant: 'success' | 'warning' | 'error' | 'neutral'
// effectiveStatus.label: 'Active' | 'Idle' | 'Error' | 'Stopped' | 'Archived'
const isLive = effectiveStatus.variant === 'success' || effectiveStatus.variant === 'warning';
| Condition | variant | label |
|---|---|---|
runningAgentCount > 0 | success | Active |
idleAgentCount > 0 | warning | Idle |
failedAgentCount > 0 | error | Error |
activeAgentCount > 0 (fallback) | success | Active |
| None of the above | neutral | Stopped |
status === 'archived' | neutral | Archived |
Always use projectStatusProps() for UI decisions, not project.status. The badge already uses it — buttons, links, and conditional sections must match.
packages/web/src/components/ui/StatusBadge.tsx → projectStatusProps()packages/web/src/components/ProjectsPanel/ProjectsPanel.tsx → action buttons