Changelog

This page lists what changed in this documentation, one entry per docs version, newest first. A docs version is one tool minor release, with the one exception described in Versioning policy. The 1.0 entry also lists the tool releases it covers.

For the tool’s own release notes, binaries, and checksums, see the GitHub releases. Each release tag is v<semver> and publishes the native binaries, a SHA256SUMS file, and the npm launcher for that exact version.

Unreleased (next tool release)

Written ahead of the tag, for the space creation surface. The entry moves under its own version when the release ships.

• slivingdoc space new <name> creates a hosted space through the site, or an S3 bucket through the S3 API, under one portable name rule: 3 to 63 lowercase letters, digits, and inner hyphens, with a letter or a digit at each end, and no name S3 reserves (xn-- or sthree- prefix, -s3alias, --ol-s3, --x-s3 or --table-s3 suffix). It prints the new target and does not change the default.

In the documentation:

• Use hosted storage gains “Create another space” and the name rule.
• Set up a bucket no longer says slivingdoc never creates a bucket.
• S3 requirements lists s3:ListAllMyBuckets and s3:CreateBucket as the administration permissions, apart from the storage ones.
• CLI names the create mode and its output, and the picker’s create row.
• Use the CLI without a host names the create mode.

1.0 (tool v0.2.5)

Cut from 0.1 for the v0.2.x line, ahead of v1.0.0, and written against v0.2.5. It is to be re-verified when v1.0.0 is released. The tool releases it covers, from the tags:

• v0.2.0 (2026-09-26): hosted storage. A token in SLIVINGDOC_TOKEN stores the notebook in a space of the hosted service. The first pull into a directory is guarded and refuses unrelated files as DIRECTORY_NOT_EMPTY. retryable is decided per reason, a full space is compacted so deleting notes can shrink it, and sld_ tokens are redacted.
• v0.2.1 (2026-09-27): a RECOVERY_FAILURE takes the reason of a store refusal of its resynchronizing read, and those refusal reasons are not retryable under that code either.
• v0.2.2 (2026-09-27): the space is taken from the token, so --bucket is optional in hosted mode.
• v0.2.3 (2026-09-28): the shared pack cache is always on and the --shared-pack-cache flag is retired. A probe result is reused for 24 hours.
• v0.2.4 (2026-09-28): slivingdoc login, logout and space, --storage, --space and SLIVINGDOC_SPACE, and a refusal for a token beside an S3 endpoint under --storage auto.
• v0.2.5 (2026-09-29): local state is keyed by the server’s space id, and terminal output gains a spinner, marks, pickers and a home screen.

In the documentation:

• The CLI guide covers hosted storage, the exit codes, the success line with its path, and the terminal spinner and marks.
• The bucket and shared-directory guides describe the reused probe, the always-on shared pack cache, and the first-pull guard.
• The conflicts guide describes how a file-versus-directory conflict keeps the local side.
• The concepts pages cover the first-pull guard, full-space compaction, the stored login as a credential, and RECOVERY_FAILURE with a store refusal reason.

0.1

The first published documentation set, written against slivingdoc v0.1.19.

• Getting started: Quickstart and Installation.
• Guides for connecting an MCP host, using the CLI without one, setting up a bucket, sharing a directory with humans, restricting agents with path policies, and resolving conflicts.
• Concepts: How it works, Storage model, and Guarantees and limits.
• Reference: CLI, MCP tools, Configuration, Errors, S3 requirements, and Logging and profiling.

Note: Every page that states a fact about the tool records the tool file and commit it was written from. A check in this site’s repository reports a page whose source has changed since, so an entry here follows a real change rather than a guess.