CLI reference
This document contains the help content for the murk command-line program.
Conventions
Section titled “Conventions”These rules hold for every command.
- Vault. A command that reads a vault takes
--vault <VAULT>. The default is.murk. The environment variableMURK_VAULTsets the same option, and the flag wins when both are set. - Finding the vault. A bare name such as
.murkis looked up in the current directory first. If it is not there, murk searches the parent directories, up to the git root or HOME, whichever comes first. It does not search when the working directory is under neither. A name with a path separator is used as written.murk initandmurk envalways use the name as written. - Repeatable flags. A flag marked “(repeatable)” can appear more than once, as in
--tag a --tag b. - Exit codes.
0is success.1is a failure, or an unresolved warning from a check command such asmurk verify,murk doctorormurk scan.2is a usage error: the arguments are invalid, so murk did nothing.murk execandmurk agent execexit with the status of the command they run. - Options before the command.
murk execandmurk agent execpass everything after the command name to the command. Put murk options such as--onlyand--vaultbefore it.murk exec echo hi --only FOOrunsecho hi --only FOOand injects every secret.
Command Overview:
murk↴murk init↴murk env↴murk restore↴murk recover↴murk add↴murk generate↴murk rotate↴murk rm↴murk get↴murk edit↴murk ls↴murk export↴murk import↴murk describe↴murk info↴murk skeleton↴murk exec↴murk agent↴murk agent plan↴murk agent exec↴murk agent grant↴murk agent init↴murk agent ls↴murk agent revoke↴murk agent connect↴murk agent disconnect↴murk mcp↴murk policy↴murk policy show↴murk policy set↴murk policy clear↴murk circle↴murk circle authorize↴murk circle revoke↴murk group↴murk group create↴murk group ls↴murk group add↴murk group rm↴murk verify↴murk trust↴murk doctor↴murk scan↴murk diff↴murk setup-merge-driver↴murk completion↴murk completion generate↴murk completion install↴
Encrypted secrets manager for developers: one file, age encryption, git-friendly
Usage: murk <COMMAND>
Subcommands:
Section titled “Subcommands:”init— Initialize a vault or reuse its existing keyenv— Write a .envrc for direnv integrationrestore— Print the key encoded by a BIP39 recovery phrase (saves nothing)recover— Print the BIP39 recovery phrase for your age keyadd— Add or update a secretgenerate— Generate a random secret and store itrotate— Rotate secrets with new valuesrm— Remove a secretget— Get a single decrypted valueedit— Edit secrets in $EDITOR (experimental)ls— List all secret namesexport— Export all secrets as shell export statementsimport— Import secrets from a .env filedescribe— Set a secret’s description, example, tags and rotation or expiry policyinfo— Show public schema and key infoskeleton— Export schema-only vault with no secrets or recipientsexec— Run a command with secrets injected as environment variablesagent— Give AI agents scoped, time-limited access to secrets (experimental)mcp— Run an MCP (Model Context Protocol) stdio server for AI agents (experimental)policy— Manage the agent access policy (experimental)circle— Manage recipientsgroup— Manage recipient groups (experimental)verify— Verify vault integrity without exporting secretstrust— Review who signed the vault and what changed, then trust it on this machinedoctor— Check the surrounding repo for hygiene issuesscan— Scan files for leaked secret valuesdiff— Show secret and access changes vs a git ref (experimental)setup-merge-driver— Configure git to use murk’s merge driver for vault files named*.murkor.murk.*(experimental)completion— Generate or install shell completions
murk init
Section titled “murk init”Initialize a vault or reuse its existing key
Usage: murk init [OPTIONS]
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk -
--reuse-key— When another vault in this directory already has a key stored on this machine, store that key for this vault too, without asking -
--separate-key— When another vault in this directory already has a key stored on this machine, make a new key for this vault, without asking
murk env
Section titled “murk env”Write a .envrc for direnv integration
Creates .envrc in the current directory with a line that runs murk export. If .envrc already exists, murk appends the line. If it already has a murk export line, murk changes nothing. Run direnv allow afterward.
Usage: murk env [OPTIONS]
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk
murk restore
Section titled “murk restore”Print the key encoded by a BIP39 recovery phrase (saves nothing)
Usage: murk restore [OPTIONS]
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filename, for the restored-identity recipient checkDefault value:
.murk
murk recover
Section titled “murk recover”Print the BIP39 recovery phrase for your age key
murk uses the key from MURK_KEY, MURK_KEY_FILE or the stored key for .murk. SSH keys and plugin identities have no recovery phrase.
Usage: murk recover
murk add
Section titled “murk add”Add or update a secret
On a terminal, murk asks for the value with a hidden prompt. When stdin is piped, murk reads all of it as the value and drops one trailing newline.
Usage: murk add [OPTIONS] <KEY>
Arguments:
Section titled “Arguments:”<KEY>— Name of the secret
Options:
Section titled “Options:”-
--desc <DESC>— Description of the secret -
--example <EXAMPLE>— Example value -
--group <GROUP>— Who can read the secret:everyone,me(a private value for you only) or a group name (experimental). Omit it to keep an existing secret’s tier. A new secret is shared with everyone -
--tag <TAG>— Tag for grouping (repeatable) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk generate
Section titled “murk generate”Generate a random secret and store it
Usage: murk generate [OPTIONS] <KEY>
Arguments:
Section titled “Arguments:”<KEY>— Name of the secret
Options:
Section titled “Options:”-
--length <LENGTH>— Length in bytesDefault value:
32 -
--hex— Encode the value as hex instead of URL-safe base64 -
--desc <DESC>— Description of the secret -
--example <EXAMPLE>— Example value -
--group <GROUP>— Who can read the secret:everyone,me(a private value for you only) or a group name (experimental). Omit it to keep an existing secret’s tier. A new secret is shared with everyone -
--tag <TAG>— Tag for grouping (repeatable) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk rotate
Section titled “murk rotate”Rotate secrets with new values
New values come from a hidden prompt on a terminal, or from piped stdin. With a KEY, murk reads all of stdin as the value. With --all, it reads one line per secret, in name order. --generate and --values-from supply values another way. murk refuses --generate with --all.
Usage: murk rotate [OPTIONS] [KEY]
Arguments:
Section titled “Arguments:”<KEY>— Secret to rotate. Omit it when you use--all
Options:
Section titled “Options:”-
--all— Rotate all secrets in the vault -
--generate— Generate random values instead of prompting (refused with--all) -
--length <LENGTH>— Length in bytes for generated valuesDefault value:
32 -
--hex— Encode generated values as hex instead of URL-safe base64 -
--values-from <FILE>— Read new values from a dotenv file of KEY=value lines (-for stdin), matched by secret name -
--list— List the secrets that need rotation instead of rotating (exits 1 if any do) -
--json— Print the listing as a JSON object withverifiedandissues. The exit code is then 0 even when secrets need rotation -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk rm
Section titled “murk rm”Remove a secret
Usage: murk rm [OPTIONS] <KEY>
Arguments:
Section titled “Arguments:”<KEY>— Name of the secret
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk
murk get
Section titled “murk get”Get a single decrypted value
Usage: murk get [OPTIONS] <KEY>
Arguments:
Section titled “Arguments:”<KEY>— Name of the secret
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk
murk edit
Section titled “murk edit”Edit secrets in $EDITOR (experimental)
Usage: murk edit [OPTIONS] [KEY]
Arguments:
Section titled “Arguments:”<KEY>— Edit one secret. Omit it to edit all
Options:
Section titled “Options:”-
--scoped— Deprecated alias for--group me. Edits your private values instead of shared secrets -
--group <GROUP>— Edit this group’s values instead of shared secrets.memeans your private values. A group name is experimental -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk ls
Section titled “murk ls”List all secret names
Usage: murk ls [OPTIONS]
Options:
Section titled “Options:”-
--tag <TAG>— Filter by tag (repeatable) -
--json— Output as JSON -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk export
Section titled “murk export”Export all secrets as shell export statements
Usage: murk export [OPTIONS]
Options:
Section titled “Options:”-
--tag <TAG>— Filter by tag (repeatable) -
--json— Output as JSON -
--allow-reserved— Allow secrets named like loader, shell or tool variables (PATH, LD_, GIT_, MURK_*, …) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk import
Section titled “murk import”Import secrets from a .env file
Usage: murk import [OPTIONS] [FILE]
Arguments:
Section titled “Arguments:”-
<FILE>— Path to the .env file to importDefault value:
.env
Options:
Section titled “Options:”-
--force— Overwrite existing secrets. Without it, import stops if any secret already exists -
--group <GROUP>— Who can read the imported secrets:everyone,me(private values for you only) or a group name (experimental). Omit it to keep each existing secret’s tier. New secrets are shared with everyone -
--example <EXAMPLE>— Example value applied to every imported secret -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk describe
Section titled “murk describe”Set a secret’s description, example, tags and rotation or expiry policy
Each call replaces the description. It also replaces the example: omitting --example clears it. --tag replaces the tags only when given. --rotate-every and --expires change only when given.
Usage: murk describe [OPTIONS] <KEY> <DESCRIPTION>
Arguments:
Section titled “Arguments:”<KEY>— Name of the secret<DESCRIPTION>— Description text (replaces the current one)
Options:
Section titled “Options:”-
--example <EXAMPLE>— Example value. Omitting it clears the current example -
--tag <TAG>— Tag for grouping (repeatable, replaces existing tags) -
--rotate-every <DAYS>— Rotation interval, e.g.90dor90(days).neverclears it -
--expires <DATE>— Hard expiry date, e.g.2026-09-01.neverclears it -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk info
Section titled “murk info”Show public schema and key info
Usage: murk info [OPTIONS]
Options:
Section titled “Options:”-
--tag <TAG>— Filter by tag (repeatable) -
--json— Output as JSON -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk skeleton
Section titled “murk skeleton”Export schema-only vault with no secrets or recipients
Usage: murk skeleton [OPTIONS]
Options:
Section titled “Options:”-
-o,--output <OUTPUT>— New output file. murk refuses a path that already exists. Without this option, murk prints to stdout -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk exec
Section titled “murk exec”Run a command with secrets injected as environment variables
Usage: murk exec [OPTIONS] <COMMAND>...
Arguments:
Section titled “Arguments:”-
<COMMAND>— Command and arguments to runPut murk options such as
--onlybefore the command. murk passes everything after the command name to the command, somurk exec echo hi --only FOOrunsecho hi --only FOOand injects every secret.
Options:
Section titled “Options:”-
--only <ONLY>— Inject only these secrets (repeatable) -
--tag <TAG>— Filter by tag (repeatable) -
--clean-env— Start the command with only the injected secrets plus PATH, HOME and TERM on UnixOn Windows, murk keeps PATH and a fixed set of system variables.
-
--allow-reserved— Allow secrets named like loader, shell or tool variables (PATH, LD_, GIT_, MURK_*, …) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk agent
Section titled “murk agent”Give AI agents scoped, time-limited access to secrets (experimental)
Usage: murk agent <COMMAND>
Subcommands:
Section titled “Subcommands:”plan— Emit schema-only context safe to paste into an AI agent prompt (experimental)exec— Run a command with strict agent-safe defaults (experimental)grant— Mint a scoped ephemeral key that can read only the named secrets (experimental)init— Mint a scoped grant and print how to run the agent safely (experimental)ls— List active agent grants and their TTLs (experimental)revoke— Revoke an agent grant (experimental)connect— Addmurk mcpto an AI client’s MCP config and mint a scoped grant for it (experimental)disconnect— Remove murk’s entry from an AI editor’s MCP config (experimental)
murk agent plan
Section titled “murk agent plan”Emit schema-only context safe to paste into an AI agent prompt (experimental)
Usage: murk agent plan [OPTIONS]
Options:
Section titled “Options:”-
--tag <TAG>— Filter by tag (repeatable) -
--json— Output as JSON -
-o,--output <OUTPUT>— New output file. murk refuses a path that already exists. Without this option, murk prints to stdout -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk agent exec
Section titled “murk agent exec”Run a command with strict agent-safe defaults (experimental)
On Unix the command keeps only PATH, HOME and TERM from the inherited environment. On Windows it keeps PATH and a fixed set of system variables. murk strips MURK_KEY, requires --only and masks the injected values in the output.
Usage: murk agent exec [OPTIONS] --only <ONLY> <COMMAND>...
Arguments:
Section titled “Arguments:”-
<COMMAND>— Command and arguments to runPut murk options such as
--onlybefore the command. murk passes everything after the command name to the command, somurk agent exec echo hi --only FOOfails with a missing--only.
Options:
Section titled “Options:”-
--only <ONLY>— Inject only these secrets (repeatable, required) -
--allow-operator-key— Decrypt with a key that is not an agent grant: your own stored key from ~/.config/murk/keys, or a full recipient’s MURK_KEY or MURK_KEY_FILE. Without this, agent exec needs an agent grant key -
--allow-reserved— Allow secrets named like loader, shell or tool variables (PATH, LD_, GIT_, MURK_*, …) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk agent grant
Section titled “murk agent grant”Mint a scoped ephemeral key that can read only the named secrets (experimental)
Usage: murk agent grant [OPTIONS] --name <NAME> --only <ONLY>
Options:
Section titled “Options:”-
--name <NAME>— Grant name (used to revoke it later) -
--only <ONLY>— Secrets this grant can read (repeatable, required) -
--ttl <TTL>— Time to live, e.g. 30m, 2h or 7d, up to 365d. Reads fail closed after expiryDefault value:
2h -
--renew— Replace the grant with this name: revoke its key, mint a fresh one. Without this, murk refuses a name that still has a grant record, and an expired grant keeps its record until the next vault write -
--out <OUT>— Where to write the agent key: a path, or-for stdout -
--force— Replace a file already at –out (refused by default) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk agent init
Section titled “murk agent init”Mint a scoped grant and print how to run the agent safely (experimental)
With --allow-tag, murk first sets the agent allow-list to those tags.
Usage: murk agent init [OPTIONS] --name <NAME> --only <ONLY>
Options:
Section titled “Options:”-
--name <NAME>— Grant name (used to revoke it later) -
--only <ONLY>— Secrets the agent can read (repeatable, required) -
--allow-tag <ALLOW_TAG>— Set the agent allow-list to these tags before granting (repeatable) -
--ttl <TTL>— Time to live, e.g. 30m, 2h or 7d, up to 365d. Reads fail closed after expiryDefault value:
2h -
--out <OUT>— Where to write the agent key: a path, or-for stdout -
--force— Replace a file already at –out (refused by default) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk agent ls
Section titled “murk agent ls”List active agent grants and their TTLs (experimental)
Usage: murk agent ls [OPTIONS]
Options:
Section titled “Options:”-
--json— Output as JSON -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk agent revoke
Section titled “murk agent revoke”Revoke an agent grant (experimental)
The grant’s key can still decrypt old versions of the vault from git history, so rotate the secrets it could read: pass --rotate, or answer the prompt on a terminal.
Usage: murk agent revoke [OPTIONS] <NAME>
Arguments:
Section titled “Arguments:”<NAME>— Grant name
Options:
Section titled “Options:”-
--rotate— Rotate the secrets the grant could read, in the same run. murk stores a new value for each. It does not rotate them at the provider -
--values-from <FILE>— With –rotate, read new values from a dotenv file of KEY=value lines (-for stdin) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk agent connect
Section titled “murk agent connect”Add murk mcp to an AI client’s MCP config and mint a scoped grant for it (experimental)
Usage: murk agent connect [OPTIONS] --only <ONLY> [CLIENT]
Arguments:
Section titled “Arguments:”<CLIENT>— Client to configure: claude, cursor, vscode, zed, gemini, omp or codex. Omit it to configure every client that already has a config file or marker directory (such as.cursor/) next to the vault
Options:
Section titled “Options:”-
--only <ONLY>— Secrets the agent may read (repeatable, required) -
--allow-tag <ALLOW_TAG>— Set the agent allow-list to these tags before granting (repeatable) -
--allow-exec— Also enable themurk_exectool in the MCP server (writes--allow-execinto the client config) -
--ttl <TTL>— Grant time to live, e.g. 30m, 2h or 7d, up to 365d. Reads fail closed after expiryDefault value:
2h -
--name <NAME>— Grant name (used to disconnect/revoke it later)Default value:
mcp -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk agent disconnect
Section titled “murk agent disconnect”Remove murk’s entry from an AI editor’s MCP config (experimental)
With no CLIENT, murk clears every configured editor. The grant stays live unless you pass --rotate, which also revokes the grant named by --name and rotates the secrets it could read.
Usage: murk agent disconnect [OPTIONS] [CLIENT]
Arguments:
Section titled “Arguments:”<CLIENT>— Editor to disconnect. Omit for every configured editor
Options:
Section titled “Options:”-
--rotate— Revoke the grant and rotate the secrets it could read -
--name <NAME>— Grant name to revoke with –rotateDefault value:
mcp -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk mcp
Section titled “murk mcp”Run an MCP (Model Context Protocol) stdio server for AI agents (experimental)
Usage: murk mcp [OPTIONS]
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk -
--allow-exec— Enable the murk_exec tool, which runs commands with the grant’s secrets injectedOff by default. The tool runs arbitrary commands as this user. The injected secrets are limited to the grant, but the command itself is not sandboxed.
murk policy
Section titled “murk policy”Manage the agent access policy (experimental)
Usage: murk policy <COMMAND>
Subcommands:
Section titled “Subcommands:”show— Show the agent access policy (works without a key)set— Set the agent allow-list: agents may only receive secrets carrying one of these tagsclear— Remove the policy. Agent mode becomes unrestricted again
murk policy show
Section titled “murk policy show”Show the agent access policy (works without a key)
Usage: murk policy show [OPTIONS]
Options:
Section titled “Options:”-
--json— Output as JSON -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk policy set
Section titled “murk policy set”Set the agent allow-list: agents may only receive secrets carrying one of these tags
Usage: murk policy set [OPTIONS] --allow-tag <ALLOW_TAG>
Options:
Section titled “Options:”-
--allow-tag <ALLOW_TAG>— Tag agents are allowed to receive (repeatable, required) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk policy clear
Section titled “murk policy clear”Remove the policy. Agent mode becomes unrestricted again
Usage: murk policy clear [OPTIONS]
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk
murk circle
Section titled “murk circle”Manage recipients
With no subcommand, lists the vault’s recipients.
Usage: murk circle [OPTIONS] [COMMAND]
Subcommands:
Section titled “Subcommands:”authorize— Add a recipient to the vaultrevoke— Remove a recipient from the vault
Options:
Section titled “Options:”-
--json— Output the recipient list as JSON -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk circle authorize
Section titled “murk circle authorize”Add a recipient to the vault
Usage: murk circle authorize [OPTIONS] <PUBKEY>
Arguments:
Section titled “Arguments:”<PUBKEY>— Public key (age1…), ssh:path, ssh: (default ~/.ssh/id_ed25519.pub), or github:username (experimental)
Options:
Section titled “Options:”-
--name <NAME>— Display name for this recipient -
--group <GROUP>— Also add the new recipient to this group (experimental) -
--force— Accept changed GitHub keys. Without it, authorize stops when a user’s keys differ from the pinned set -
--allow-ssh-rsa— Allow ssh-rsa keys. They are refused or skipped by default, so prefer ed25519 -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk circle revoke
Section titled “murk circle revoke”Remove a recipient from the vault
Usage: murk circle revoke [OPTIONS] <RECIPIENT>
Arguments:
Section titled “Arguments:”<RECIPIENT>— Recipient pubkey, display name, or github:username
Options:
Section titled “Options:”-
--rotate— Rotate the secrets they had access to in the same session -
--values-from <FILE>— With –rotate, read new values from a dotenv file of KEY=value lines (-for stdin) -
--force— Revoke every key of a multi-key GitHub user without confirmation -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk group
Section titled “murk group”Manage recipient groups (experimental)
Usage: murk group <COMMAND>
Subcommands:
Section titled “Subcommands:”create— Create a new recipient group (you become its first member)ls— List groups and their membersadd— Add a member to a grouprm— Remove a member from a group, or delete the group entirely
murk group create
Section titled “murk group create”Create a new recipient group (you become its first member)
Usage: murk group create [OPTIONS] <NAME>
Arguments:
Section titled “Arguments:”<NAME>— Group name
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk
murk group ls
Section titled “murk group ls”List groups and their members
Usage: murk group ls [OPTIONS]
Options:
Section titled “Options:”-
--json— Output as JSON -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk group add
Section titled “murk group add”Add a member to a group
Usage: murk group add [OPTIONS] --member <MEMBER> <NAME>
Arguments:
Section titled “Arguments:”<NAME>— Group name
Options:
Section titled “Options:”-
--member <MEMBER>— Recipient pubkey or display name to add -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk group rm
Section titled “murk group rm”Remove a member from a group, or delete the group entirely
Usage: murk group rm [OPTIONS] <NAME>
Arguments:
Section titled “Arguments:”<NAME>— Group name
Options:
Section titled “Options:”-
--member <MEMBER>— Recipient pubkey or display name to remove (omit to delete the group) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk verify
Section titled “murk verify”Verify vault integrity without exporting secrets
Usage: murk verify [OPTIONS]
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk
murk trust
Section titled “murk trust”Review who signed the vault and what changed, then trust it on this machine
Needed once per vault on a new clone, whenever a teammate’s first signed write arrives, and whenever murk refuses a vault (an unfamiliar signer, an unsigned or rolled-back vault). Shows the signer’s key and signing-key fingerprint, the recipient changes since this machine last trusted the vault, and asks before recording it. An unsigned vault is signed with your key.
Usage: murk trust [OPTIONS]
Options:
Section titled “Options:”-
--yes— Accept without asking, for scripts. Review the vault first -
--print-key— Print your own trusted-signer entry (for MURK_TRUSTED_SIGNERS) and signing-key fingerprint (for teammates to confirm), then exit -
--re-add <KEY>— Trust a key this machine recorded as removed from the vault again (its public key, or its name in the vault). Repeat for each key. A vault signed by or listing a removed key is never trusted without it -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk doctor
Section titled “murk doctor”Check the surrounding repo for hygiene issues
Usage: murk doctor [OPTIONS]
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk
murk scan
Section titled “murk scan”Scan files for leaked secret values
Usage: murk scan [OPTIONS] [PATHS]...
Arguments:
Section titled “Arguments:”<PATHS>— Files or directories to scan (defaults to current directory)
Options:
Section titled “Options:”-
--vault <VAULT>— Vault filenameDefault value:
.murk
murk diff
Section titled “murk diff”Show secret and access changes vs a git ref (experimental)
Lists recipients, signer, signing keys, policy, grants and group members that changed, then the secrets. The vault at the ref is verified first. murk never shows a revision that this machine’s trust pin refuses.
Usage: murk diff [OPTIONS] [GIT_REF]
Arguments:
Section titled “Arguments:”-
<GIT_REF>— Git ref to compare againstDefault value:
HEAD
Options:
Section titled “Options:”-
--show-values— Show actual values (not just secret names) -
--json— Output JSON: {“secrets”: […], “changes”: […]} (values only with –show-values) -
--vault <VAULT>— Vault filenameDefault value:
.murk
murk setup-merge-driver
Section titled “murk setup-merge-driver”Configure git to use murk’s merge driver for vault files named *.murk or .murk.* (experimental)
Adds *.murk merge=murk and .murk.* merge=murk to the .gitattributes at the root of the working tree, and sets merge.murk.* in git config. Changes nothing when git config already sets a merge.murk.driver that murk did not write, or when the git attributes already give vault files another merge attribute.
The driver merges three sides that murk reads as vaults. It merges a file that cannot be a vault as text. When a side is or could be a vault but murk cannot read every side, the driver exits 1 and writes both sides into the file between conflict markers. Valid JSON could be a vault only when it has a top-level recipients, secrets, meta, vault_name or vault_id key. Other text could be a vault when it starts with { or uses one of these names as a JSON key.
Usage: murk setup-merge-driver
murk completion
Section titled “murk completion”Generate or install shell completions
Usage: murk completion <COMMAND>
Subcommands:
Section titled “Subcommands:”generate— Print completions to stdoutinstall— Install completions under your home directory
murk completion generate
Section titled “murk completion generate”Print completions to stdout
Usage: murk completion generate <SHELL>
Arguments:
Section titled “Arguments:”-
<SHELL>— Shell to generate completions forPossible values:
bash,elvish,fish,powershell,zsh
murk completion install
Section titled “murk completion install”Install completions under your home directory
Writes ~/.zfunc/_murk for zsh, ~/.local/share/bash-completion/completions/murk for bash, ~/.config/fish/completions/murk.fish for fish, ~/.config/elvish/lib/murk.elv for elvish and ~/.config/powershell/_murk.ps1 for PowerShell. It replaces a file that is already there and needs HOME. For zsh and bash, murk then prints the lines to add to your shell startup file.
Usage: murk completion install <SHELL>
Arguments:
Section titled “Arguments:”-
<SHELL>— Shell to install completions forPossible values:
bash,elvish,fish,powershell,zsh