8.1 Documentation versions
Available documentation
| Product | Documentation set | Reviewed against | Release status | Reviewed on |
|---|---|---|---|---|
| Community open-source Web | Current docs · 0.2.4 | 0.2.4 | Candidate · not yet released | 2026-10-21 |
| Community open-source Web | 0.2.3 release docs | 0.2.3 | Frozen · GitHub Releases / Docker Hub / npm | 2026-10-19 |
| Community open-source Web | 0.2.2 release docs | 0.2.2 | Frozen · GitHub Releases / Docker Hub / npm | 2026-10-18 |
| Community open-source Web | 0.2.1 release docs | 0.2.1 | Frozen · GitHub Releases / Docker Hub | 2026-10-18 |
These docs cover the 0.2.4 candidate, which has not been released. The release will be available through GitHub Releases, Docker Hub, and npm. For the currently released version, use the 0.2.3 installation guide. The docs cover the workbench, employee API / SDK / MCP, callbacks, apps, permissions, installation, and upgrades. See each page for its review date and limits.
This current candidate documentation opens by default. It is updated with the source code and its date is refreshed after each review; it is not a frozen copy of a release's documentation.
Pro and Enterprise are not available yet and only have planning pages: Pro, Enterprise. Independent cloud execution is a planned direction for Enterprise, without a separate Cloud product or documentation version.
Version-frozen documentation
When the first stable release with complete release evidence ships, a copy of the documentation will be frozen at the same time under /v/<version>/, for example /v/0.2.1/start/quickstart. Frozen text, screenshots and navigation do not change afterwards; a correction gets a new revision while the original link keeps working.
The bilingual documentation, navigation and screenshot references for 0.2.2 are frozen with its stable release under /v/0.2.2/; the root path continues to maintain current documentation. Earlier preview releases have no frozen copy. Versions 0.2.1-alpha.1 to alpha.3 did not save documentation when they were tagged, so documentation for them will not be recreated after the fact.
What "latest" means
"Latest" points to the newest documentation set that may be public and has passed review. Once a stable release exists, the default points to the newest stable release; while no stable release exists, the current preview documentation is the default. Previews do not replace an existing stable default.
A link to a frozen version always stays on that version; it will not jump to the latest documentation because you visited it before.
Reading version numbers
Version numbers follow semantic versioning: major.minor.patch, with suffixes such as -alpha.N for previews. See the software changelog for released changes. A machine-readable list is published as docs-manifest.json at the site root.