Przejdź do treści
Biblioteka skilli
AI i agenci · Nauka i wyjaśnianie

flightdeck

/flightdeck

Wyjaśnia, co wtyczka Flightdeck rejestruje w sesji Claude Code, gdzie to widać, jakie zmienne środowiskowe sterują zbieraniem i egzekwowaniem oraz jak decyzje polityki MCP trafiają do sesji.

Repozytorium
flightdeck ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
27.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
2
Przestarzałość

Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Wyjaśnia, co wtyczka Flightdeck rejestruje w sesji Claude Code, gdzie to widać, jakie zmienne środowiskowe sterują zbieraniem i egzekwowaniem oraz jak decyzje polityki MCP trafiają do sesji.

Oryginalny opis (EN)

Explains what the Flightdeck plugin records about this Claude Code session, where it shows up, which environment variables control capture and enforcement, and how MCP policy decisions reach the session. Use when the user asks what Flightdeck sees, why a tool call was refused by an MCP policy, or how to turn capture off.

Jak działa

  1. What the plugin records
  2. Where the session shows up
  3. MCP policy enforcement
  4. Environment variables
  5. Failure behaviour
  6. Privacy
Sekcje z nagłówków SKILL.md, w oryginale · 104 linii, 836 słów
Podgląd SKILL.md
---
name: flightdeck
description: Explains what the Flightdeck plugin records about this Claude Code session, where it shows up, which environment variables control capture and enforcement, and how MCP policy decisions reach the session. Use when the user asks what Flightdeck sees, why a tool call was refused by an MCP policy, or how to turn capture off.
---

# Flightdeck

Flightdeck is a self-hosted control plane for AI agents. With this plugin
loaded, the current Claude Code session streams lifecycle, tool and LLM
events to the Flightdeck server configured for this machine, and the
session appears in the Fleet view next to production agents.

## What the plugin records

Every hook Claude Code exposes runs the same script, so the session is
reported from start to end:

- Session start and end, including sub-agent sessions spawned through the
  Agent tool (reported under their own session id, linked to the parent).
- Every tool call by name, successful or failed, with Claude Code's
  measured duration and `tool_use_id`, a structured error on failure
  (its text only while both capture flags are on; `<redacted>`
  otherwise), and a sanitised whitelist of arguments (`file_path`,
  `command`, `query`, `pattern`, `prompt`) while
  `FLIGHTDECK_CAPTURE_TOOL_INPUTS` is on. MCP tool calls carry their full
  arguments because the whitelist would empty them, plus the server
  identity Claude Code reports (`mcp_server`) when it sends one.
- Every LLM turn read from the session transcript: model, input and output
  tokens, cache tokens (with their one-hour share), thinking tokens,
  service tier, data residency, web search counts, stop reason, latency,
  and the prompt and response bodies while `FLIGHTDECK_CAPTURE_PROMPTS`
  is on. Each turn also carries the session's billing mode: a Claude
  subscription login is `subscription` (not counted as spend), an API
  key or a Bedrock / Vertex AI / Foundry session is `metered`.
- Context compaction and the MCP servers declared in `.mcp.json`.
- MCP policy decisions: when a server is warned or blocked by the
  Flightdeck MCP policy for this flavor, the session emits a
  `policy_mcp_warn` or `policy_mcp_block` event.

Prompt capture is on by default for this plugin because you are observing
your own session on your own machine. The Python sensor used for
production agents defaults the other way.

## Where the session shows up

Open the dashboard served by `FLIGHTDECK_SERVER` (default
`http://localhost:4000`). The session is stamped with:

- flavor `claude-code`
- agent type `coding`
- client type `claude_code`
- a context block with the native Claude Code session id, the Claude
  Code version from the transcript, how the session started (known
  values include `startup`, `resume`, `clear` and `compact`), the
  entrypoint (known values include `cli` and `sdk-cli`), whether a human
  is attending it, and cloud / CI markers when present

Filter the Fleet view by flavor `claude-code` to see only Claude Code
sessions. The session drawer shows tool calls, LLM turns, token totals and
the Prompts tab (empty with a clear notice when capture is off).

## MCP policy enforcement

Before each `mcp__<server>__<tool>` call the plugin evaluates the MCP
policy fetched at session start for flavor `claude-code`:

- `allow` entries let the call through silently.
- `deny` entries with `block` enforcement refuse the call. The tool result
  reads `MCP policy blocked tool call to <server> (<scope>, <path>)`.
- A server unknown to an allowlist-mode policy triggers Claude Code's own
  permission prompt. Approving it once is remembered on this machine.

Operators change the policy in the dashboard under MCP policies. The
plugin re-reads it at the next session start.

## Environment variables

| Variable | Default | Effect |
| --- | --- | --- |
| `FLIGHTDECK_SERVER` | `http://localhost:4000` | Control plane base URL; events go to `/ingest`, policies come from `/api`. |
| `FLIGHTDECK_TOKEN` | `tok_dev` | Access token. The default is the development seed token and prints a warning; set a real token outside local development. |
| `FLIGHTDECK_CAPTURE_PROMPTS` | `true` | `false` strips prompt, response and tool-result bodies while keeping metadata and token counts. |
| `FLIGHTDECK_CAPTURE_TOOL_INPUTS` | `true` | `false` strips the sanitised tool arguments. |
| `FLIGHTDECK_BILLING_MODE` | detected | `metered`, `subscription` or `local`; overrides the billing mode the plugin detects from `claude auth status` and the cloud-provider variables (set `metered` when a subscription runs on extra usage). |
| `FLIGHTDECK_QUIET` | unset | `1` silences the default-token warning. |
| `CLAUDE_SESSION_ID` | unset | Forces the session id reported to Flightdeck. |
| `CLAUDE_CODE_SESSION_ID` | set by Claude Code | Claude Code's own session id; reported as `context.claude_code_session_id` and used to key the per-session marker when a hook payload has no `session_id`. |

## Failure behaviour

The plugin never blocks Claude Code. If the server is unreachable it
prints one line to stderr per failed request and exits successfully, and
the next hook tries again. The `session_end` is posted by a detached
worker after the hook returns (Claude Code allows SessionEnd hooks 1.5
seconds); its failed-request lines go to
`$TMPDIR/flightdeck-plugin/session-end-worker.log` (Windows:
`%TEMP%\flightdeck-plugin\session-end-worker.log`), an owner-only file
truncated past 256 KiB. Policy evaluation fails open: with no cached
policy, tool calls proceed as Claude Code would normally decide, and MCP
servers bundled with other plugins are reported but not gated.

## Privacy

Everything the plugin captures goes only to the Flightdeck server you
configured, never to a third party. Turn either capture flag off to keep
content bodies on your machine; the session, tool names and token counts
still ship so the dashboard stays useful.

Wersje

W bazie nie ma innych skilli o nazwie flightdeck.

Migawka bazy z 13.11.2026 · wersja paczki 89001fee66b3 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100mcp-client-configuration-claude-desktop
    Rejestruje serwery MCP w plikach konfiguracyjnych Claude Desktop, ustawia zmienne środowiskowe i rozwiązuje problemy z połączeniem.
  • 100cc-inspect
    Diagnozuje środowisko uruchomieniowe Claude Code: zmienne środowiskowe, tożsamość sesji, katalog konfiguracji, ścieżki wtyczek, wersje narzędzi systemowych, stan Rune i szczegóły platformy.
  • 100furl
    Wyjaśnia, jak działa wtyczka kompresji kontekstu Furl w Claude Code i Codex: narzędzia MCP furl_compress i furl_retrieve, przepływ odzyskiwania treści oraz opcjonalne automatyczne hooki.
  • 100session-capture
    Tworzy znormalizowany zapis sesji z celem, wykonaną pracą, decyzjami, blokadami i wynikami weryfikacji.
  • 100auto-capture-claude-code
    Dodaje do skilla auto-capture automatyczne hooki końca sesji Claude Code, które zapisują transkrypty do Open Brain bez ręcznej interwencji.
  • 100create-plugin
    Tworzy pełną strukturę plików repozytorium działającego jednocześnie jako wtyczka Claude Code i Codex, z obsługą marketplace.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.