If you have the descriptors, you can restore with Bitcoin Core importdescriptors.

It's a good question though, because I couldn't find an actual guide. Maybe we should make one.

There are many others including Core, Electrum, Blue Wallet, Nunchuck and Spector.

You don't need Sparrow, Nunchuk, or any third-party GUI coordinator to reconstruct or spend from a multisig setup. The Bitcoin protocol doesn't have a concept of "coordinators"—it only understands Script, Output Descriptors, and Partially Signed Bitcoin Transactions (PSBTs, BIP 174/370).

Here is the exact technical blueprint for how recovery works without coordinator software:

1. What You Actually Need: The Output Descriptor

The biggest pitfall in multisig is thinking that having your 2-of-3 seed phrases is enough. It isn't. Seeds derive individual keypairs, but they don't record: * The quorum threshold (e.g., 2-of-3 vs. 3-of-5). * The cosigner public keys and their sorting order (BIP 67 lexicographical sorting). * The specific derivation paths used (e.g., m/48'/0'/0'/2' for native SegWit).

To make your multisig truly coordinator-independent, you must back up your Output Descriptor (standardized under BIP 380–388). It looks like this: wsh(sortedmulti(2,[fingerprint/path]xpub1...,[fingerprint/path]xpub2...,[fingerprint/path]xpub3...))#checksum

With this string and your signing devices/seeds, your setup can be recovered in any software or directly from the command line indefinitely.

2. Recovery via Bitcoin Core (CLI / Headless)

If every coordinator disappeared tomorrow, you could load and spend from the multisig using standard bitcoin-cli:

1. Import the Descriptor: Create a watch-only descriptor wallet in Bitcoin Core and import your descriptor string:

   bitcoin-cli -named createwallet wallet_name="multisig_recovery" disable_private_keys=true blank=true

   bitcoin-cli -rpcwallet="multisig_recovery" importdescriptors '[{"desc": "<YOUR_DESCRIPTOR_STRING>", "timestamp": "now", "active": true}]'

2. Construct the Unsigned Transaction (PSBT):

   bitcoin-cli -rpcwallet="multisig_recovery" walletcreatefundedpsbt '[]' '[{"<DESTINATION_ADDRESS>": 0.5}]'

3. Sign with Signers / Hardware Devices: You can pass the base64 PSBT directly to your hardware signers (via SD card or USB) or sign via the command line using HWI (Bitcoin Core's open-source Hardware Wallet Interface):

   hwi -t <device_type> signtx <PSBT_BASE64>

4. Combine, Finalize, and Broadcast: Once you have signatures from your threshold (e.g., 2 of 3):

   bitcoin-cli combinepsbt '["<PSBT_WITH_SIG_1>", "<PSBT_WITH_SIG_2>"]'

   bitcoin-cli finalizepsbt "<COMBINED_PSBT>"

   bitcoin-cli sendrawtransaction "<FINAL_HEX>"

Best Practice for Your Backups Today

In Sparrow, go to Settings > Export and export your Output Descriptor (plain text) along with the configuration file. Keep a physical copy of this descriptor alongside each of your seed backups. As long as you have that descriptor and the quorum of keys, your funds can always be recovered using pure open-source primitives.

get ready to give blockchain instructions directly from your cli

This is the kind of thing you should test before funing.