Browse documentation
Command reference

gitvaulty cat

Decrypt one encrypted file directly to standard output without creating a plaintext file.

View source ↗

Decrypt one encrypted file directly to standard output without creating a plaintext file.

Usage

npx gitvaulty cat <path> [--force]

Pass the logical plaintext path without the .gitvaulty suffix. Relative paths resolve from your current working directory; absolute paths are also supported:

npx gitvaulty cat config/credentials.json | jq .
npx gitvaulty cat manifests/secret.yaml | kubectl apply -f -

From a subdirectory, use the filename relative to that directory:

cd secrets
npx gitvaulty cat --force accounts.yaml

Before 4.3.0, cat resolved relative paths from the repository root. Scripts that relied on that behavior while running from a subdirectory must use a current-directory-relative or absolute path, or run from the repository root.

Output contract

cat writes only the exact decrypted bytes to stdout. It does not decode text, change line endings, append a newline, or reject binary data. Diagnostics and repository agent-skill warnings go to stderr, so a successful pipeline receives an uncontaminated byte stream.

The command decrypts in memory. It does not create the logical plaintext path, modify .git/info/exclude, or retain a temporary plaintext file.

Safety behavior

GitVaulty refuses to write a secret directly to an interactive terminal:

Refusing to print a secret to an interactive terminal. Pipe the output or use --force.

Use --force only when displaying the plaintext is intentional. The guard cannot control what a downstream command does with the bytes; avoid tools that log, cache, or persist their input.

A missing encrypted source reports Encrypted file does not exist rather than an authorization error. An existing source must be registered and accessible to the current identity. GitVaulty applies the same path, authorization, regular-file, symlink, and concurrent-ciphertext checks used by guarded editing. A missing identity uses the shared restore/create/cancel flow only when interactive input and a separate diagnostic stream are available; otherwise it fails. Prompts and bootstrap notices use stderr, keeping stdout safe for pipelines.