You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Remove auto-snapshot from sidecar setup, instruct agents to snapshot explicitly
Setup now prints a prompt to run chunk sidecar snapshot create after
verifying the sidecar works. The sidecar skill is updated to make
snapshotting a required explicit step after validation is confirmed,
using --remote --sidecar-id <id> for verification.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Remove unused sidecarSetupSnapshot function after setup flow refactor
The auto-snapshot step was removed from sidecar setup in favor of an
explicit user-driven snapshot workflow; the helper function was left
behind and caught by the linter.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: webster <michael@webster.fyi>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: skills/chunk-sidecar/SKILL.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,14 +39,12 @@ Run `chunk sidecar current`. Three cases:
39
39
40
40
## Step 3: One-time setup
41
41
42
-
Skip this step unless the user explicitly asks to "prep the sidecar", "snapshot it", "set up the environment", or similar. This is a one-time flow that produces a reusable snapshot so future sessions boot fast.
43
-
44
-
1.`chunk sidecar env` — detects the tech stack and emits a JSON environment spec.
45
-
2. Review the spec with the user.
46
-
3.`chunk sidecar env | chunk sidecar build --tag <image-tag>` — writes `Dockerfile.test` and builds an image.
47
-
4.`chunk sidecar create --name <name> --image <image-tag>` — creates a sidecar from that image.
48
-
5. Install any extra deps over SSH: `chunk sidecar ssh -- bash -c "<install commands>"`.
49
-
6.`chunk sidecar snapshot create --name <checkpoint-name>` — captures the configured state and returns a snapshot ID.
42
+
Skip this step unless the user explicitly asks to "prep the sidecar", "set up the environment", or similar. This is a one-time flow that produces a reusable snapshot so future sessions boot fast.
43
+
44
+
1.`chunk sidecar setup --dir . --name <name>` — detects the stack, syncs files, and runs install steps on the sidecar. Prompts to create a sidecar if none is active.
45
+
2. Verify the sidecar is working correctly by running a validate command against it directly: `chunk validate --remote --sidecar-id <sidecar-id>`. Use the exact sidecar ID from step 1.
46
+
3. Once confirmed working, snapshot the sidecar: `chunk sidecar snapshot create --name <snapshot-name>`. This captures the configured state and returns a snapshot ID. **Always snapshot after confirming the sidecar is working — do not skip this step.**
47
+
4. Record the snapshot ID in `.chunk/config.json` under `validation.sidecarImage` so future sidecars boot from it: `chunk config set validation.sidecarImage <snapshot-id>`.
50
48
51
49
Future sessions boot from the snapshot: `chunk sidecar create --name <new-name> --image <snapshot-id>`.
0 commit comments