From d0e44568ec539187e7c6bc7c3572d0f05dd67b88 Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Tue, 20 Oct 2026 08:10:52 +0000 Subject: [PATCH] docs: explain offline kit checks Kit authors lacked guidance for checking local sources without a daemon or sign-in. Document offline validation and inspection, including the policy checks they skip. --- content/manuals/ai/sandboxes/customize/kits-v2.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/content/manuals/ai/sandboxes/customize/kits-v2.md b/content/manuals/ai/sandboxes/customize/kits-v2.md index 59c45f0a50..64216dc889 100644 --- a/content/manuals/ai/sandboxes/customize/kits-v2.md +++ b/content/manuals/ai/sandboxes/customize/kits-v2.md @@ -662,14 +662,21 @@ and OpenCode reads `OPENCODE_CONFIG`. Don't use `setup.startup` for settings the agent must read during initialization; startup commands don't gate the entrypoint. -## Packaging and distribution +## Validate and inspect kits -The `sbx kit` subcommands validate, inspect, and publish kits: +Use these commands to check a kit before sharing it: - `sbx kit validate ` — check that a kit directory or ZIP is well-formed. - `sbx kit inspect ` — display kit details. Add `--json` for machine-readable output. + +Add `--offline` to validate or inspect a local directory or ZIP without starting +the daemon or signing in. Offline checks skip kit source and signature policies; +they don't establish whether the kit is permitted to load. + +## Packaging and distribution + - `sbx kit pack -o ` — package a directory as a ZIP file for sharing. - `sbx kit push ` — publish to an OCI registry (for example,