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

How to review architect and advisor consults in a session with Claude Flightdeck

Check when the architect or advisor was consulted, how long each took, and what the inferred moments were.

Who it is forA developer who relies on an architect or advisor agent in Claude Code and wants to confirm when it was consulted and whether it helped.

The problemIt is unclear how often the architect was consulted, how long those consults took, and whether a server-side advisor was used at all.

The outcomeAn architect panel with a consult timeline, a running or last-consult duration, optional consult moments labelled as inferred, and the first line of a subagent architect's advice.

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. Read the architect panel's consult timeline and how long the last consult took
  4. Check which moments are marked (inferred); set moments to false in /config to hide them
  5. If your architect has a different name, change architectPattern in /config to match its agent type or server tool

Prompt for your agent

Install the scasella/claude-flightdeck plugin in Claude Code 2.1.287 or later, run a task that consults an architect or advisor, and open /flightdeck. Report the number of consults on the architect timeline and the duration of the last one. Verify that any moment labelled (inferred) is distinguished from measured consults.

Caveat. Server-side advice from a tool such as Claude Code's advisor is encrypted, so the pane shows only the count and timing of consults, not what they said.

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