DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to follow subagents as cards or swimlanes with Claude Flightdeck

See each subagent's task, live context, output tokens, steps and clock, and expand any one for detail.

Who it is forA developer running a Claude Code session that spawns several subagents who needs to see which ones are running, stalled or hitting max_tokens.

The problemSubagents run in parallel and their progress is hard to follow from the transcript alone, especially when one stalls or hits its token limit.

The outcomeAn agents panel showing cards side by side while they fit, or swimlanes on one time axis beyond that, with the max_tokens warning in red and expandable detail for each agent.

What you need first

  • Claude Code 2.1.287 or later
  • A terminal at least 144 columns wide for the pane to open on start, or any width with /flightdeck

Steps

  1. Install the plugin with /plugin marketplace add scasella/claude-flightdeck and /plugin install flightdeck@claude-flightdeck
  2. Run /reload-plugins and /flightdeck
  3. Start a session that spawns subagents and watch the agents panel fill with cards
  4. Press ctrl+x tab, then 1, 2 and so on to expand a card or lane and read its last three tool calls and the start of its answer
  5. Set maxCards in /config (1 to 6) if you want swimlanes to appear sooner

Prompt for your agent

Install the scasella/claude-flightdeck plugin in Claude Code 2.1.287 or later, start a task that spawns at least two subagents, and open /flightdeck. Report how many agents appear as cards or swimlanes and flag any agent showing max_tokens in red. Verify the expanded view of one agent shows its last three tool calls.

Caveat. Per-agent context is the latest request's full input and is labelled ctx, not cost, because the API reports no per-agent cost.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page