Cypher Page

Write a little. Share what matters.

Cypher Page CLI 0.4.0: keep drafts local until you share

Cypher Page CLI version 0.4.0 was released on November 18, 2026. It adds a way to save a cleaned local draft, review it, and choose when to share it over Veilid. This is a command-line release; the graphical app is still in development.

Save a draft before sharing

Importing a Markdown file saves an independent, cleaned snapshot on your device. It does not share the page. When you are ready, use the local ID shown by list with publish --local to share that saved version. Editing the original file later does not update the snapshot. These operations use your local collection and may initialize local services or the system keychain, so they are not a network-isolated mode.

File publication also saves a local snapshot first. If a publication attempt fails, inspect list and retry a retained ID with publish --local instead of running file publication again; each new file invocation creates another local identity. File publication requires working local-page storage. The 0.4.0 list output includes local IDs and statuses, so scripts parsing older address-only rows need updating. An unconfirmed attempt may have written remote data. A confirmed remote success followed by a local bookkeeping error is a different case and may already have shared the page. An ID recorded as published is not sent again by publish --local; use update or clear to change it.

Back up local work carefully

Version 0.4.0 encrypted backups include saved local documents and their IDs, titles, statuses, and addresses alongside ownership credentials and titles. They do not include fetched copies or your original Markdown files, so keep those files separately. Use a strong, unique backup passphrase.

Version 0.4.0 restores V1 backups made by 0.3.0, but version 0.3.0 cannot restore V2 backups. Before either backup or restore, stop other Cypherpage processes using the same local collection. Restore skips existing owners and identical local records; conflicts are rejected before writes, but a later storage failure can leave a partial import. There is no general rollback guarantee. If the system keychain is unavailable, the explicit --allow-insecure-fallback flag permits less-secure file-based device-key storage. Under that fallback, device secrets are protected only by filesystem permissions rather than the system keychain; protect the selected storage and backups accordingly.

Try the CLI

The registry install compiles the published source crate and requires Rust 1.89 or newer plus native build tools:

cargo install cypherpage --version 0.4.0 --locked

You can also build from the v0.4.0 source tag. There is no prebuilt cross-platform executable or graphical installer. See the CLI installation and workflow guide, the 0.4.0 GitLab release notes, and the version 0.4.0 crate on crates.io.