CLI Cookbooks

End-to-end recipes for morse-cli: publish content, read it back, encrypt and decrypt, delegate write access, and script it in CI. These use the active context, so most commands need no object IDs. For the full per-command reference, see CLI Command Reference.

Prerequisites

Make sure the CLI is installed and your account is imported before continuing. See CLI Overview for setup.

Publishing your first entry

Create a profile, import a key, then create a publication and a collection. Each create command selects the new object as the active one, so the steps after require no IDs.
account import will prompt for your private key and a keystore password. The collection defaults to blob mode when --mode is omitted.

morse config add testnet --network testnet
morse account import
morse publication create --name "My Blog" --slug "my-blog-$(date +%s)"
morse collection create posts

echo "hello morse" > post.md
morse entry add hello --file post.md

Uploading 12 bytes to Walrus...
Added entry #0 "hello". (tx: D9Yfjk...)
  view: https://aggregator.walrus-testnet.walrus.space/v1/blobs/0iKeii...

A publication's name and slug are immutable on-chain (the slug is the registry's unique key), so there is no rename command.

Check the active context any time with morse status; switch the active publication (and collection) with morse use <slug> [collection].

See also: SDK Cookbooks → Creating a publication

Reading it back

entry get shows metadata; entry read fetches the public content itself. The view link printed by entry add opens the same bytes in a browser.

morse entry get 0
morse entry read 0
morse entry read 0 --out got.md

See also: SDK Cookbooks → Reading it back

Listing your content

List your publications, collections, and entries in the active context.

morse publication list
morse collection list
morse entry list
morse status

Publishing a new revision

Append a new public revision directly, or stage a draft first and promote it. Revisions are append-only; existing revisions are never edited in place. Two heads track progress: draftHead (work in progress) and publicHead (the live version).

Option A: publish direct

Skip the draft stage and append a new public revision in one step. This updates publicHead immediately.

echo "hello morse, edited" > post.md
morse revision publish-direct 0 --file post.md

Option B: draft then publish

Stage a draft revision first (updates draftHead only), then promote it to a public revision. By default, publish-from-draft reuses the draft's content; pass --file to replace it with new content. Useful when you want to review before going live.

echo "hello morse, draft" > draft.md
morse revision append-draft 0 --file draft.md
morse revision publish-from-draft 0 1

See also: SDK Cookbooks → Publishing a new revision

Encrypted content

Morse uses Seal for on-chain access control over encrypted content. When you add an encrypted entry, the CLI handles Seal key negotiation automatically.

echo "members only" > secret.txt
morse entry add-encrypted members --file secret.txt
morse entry decrypt 1 --out recovered.txt

See also: SDK Cookbooks → Encrypted content

Delegating write access

Morse separates ownership (OwnerCap) from publishing (PublisherCap). The owner issues a cap bound to a co-author's address, granting them write access. Once issued, the co-author can publish entries using their own key. Revoking the cap causes further writes to abort on-chain. See Access Control → Issuing publisher caps for details.

As the owner, issue a cap to grant write access and revoke it to remove access:

morse cap issue 0xCO_AUTHOR_ADDRESS
morse cap revoke 0xCAP_ID

As a cap holder, list your caps or permanently destroy a specific cap:

morse cap list
morse cap destroy 0xCAP_ID

To rotate a cap to a different address, destroy the old one and have the owner issue a new cap to the new address. Do not use morse cap transfer to send a cap to a different holder. The on-chain holder binding is immutable, so the recipient would own the object but be unable to use or destroy it.

See also: SDK Cookbooks → Delegating write access

Transferring ownership

The owner can transfer the publication's OwnerCap to another address, handing over full governance: the recipient becomes the new owner and can issue, revoke, and manage caps.

morse publication transfer-ownership 0xNEW_OWNER

See also: SDK Cookbooks → Transferring ownership

Deleting and tearing down

Deletion is bottom-up: remove entries first, then collections, then the publication. Each container must be empty before it can be deleted. Entry IDs are permanently retired on deletion and never reused. See Entries → Deleting an entry for details.

morse entry delete 0
morse entry delete 1
morse collection delete posts
morse publication delete

See also: SDK Cookbooks → Deleting and tearing down

Scripting and CI

Authenticate with env vars (no prompts), skip confirmations with --yes, and parse --json on stdout. Reads by object ID never need a key; slug-based reads still require an account address for resolution.

export MORSE_PRIVATE_KEY=suiprivkey1...
export MORSE_NETWORK=testnet

pub=$(morse --json publication create --name CI --slug "ci-$(date +%s)" | jq -r .publicationId)
echo "created $pub"
morse --yes publication delete "$pub"

morse publication get 0x00 || echo "exit $?"

Troubleshooting

Next steps