Troubleshooting

Most problems come from the folder Casper and your assistant use, or from a stale slide kit. Start here before reinstalling the app.

Casper and my assistant show different files

Symptom: You briefed the assistant but nothing new appears in Casper (or the opposite).

Fix:

1. Confirm both tools point at the exact same path — not a copy, not a subfolder, not a cloud sync conflict folder.
2. In Casper, check the workspace tooltip in the sidebar (loaded folder path).
3. In your assistant, open that same root — you should see slides/ at the top level.

If paths differ, use Change workspace… in Casper and reopen the correct folder in your assistant.

Slide kit sync failed or commands are missing

Symptom: /create-slide does not work, Guide is empty, or Casper shows “slide kit is not installed” / “out of date”.

Also try: in Cursor/Codex, /casper-help — confirms the kit is loaded and shows which slash command matches your goal.

Fix:

1. Open the correct workspace folder.
2. In the Casper sidebar, run Sync kit when prompted (or after switching workspace).
3. Wait until sync completes — your carousels in slides/ are not deleted. Old slash commands removed from the app are pruned from the managed kit on sync.

Sync only updates assistant skills and workflows under hidden kit folders (for example .agent/). Your owned zones stay intact — see What sync touches.

If sync keeps failing, check disk permissions on the folder and that you are not opening a read-only volume.

A deck appears but looks “orphan” or warns about the catalog

Symptom: A folder exists under slides/ but Casper shows a warning that the deck is not listed in project.json.

What it means: project.json is the workspace catalog (deck titles, folders, order). Your assistant normally maintains it when creating decks. A folder on disk without a catalog entry still opens, but metadata may be incomplete.

Fix: Ask your assistant to register the deck in the catalog, or run /create-slide for new decks so the catalog stays consistent. You do not need to edit project.json by hand.

Broken or missing images in preview

Symptom: Placeholder or broken image icon on a screen before export.

Fix:

1. Open Assets — confirm the file exists in assets/ or the deck’s local assets folder.
2. Check the path your assistant used (@assets/... vs slides/<id>/assets/...).
3. Re-brief with the correct path or upload the file in Assets and ask the assistant to reference it.

See Assets.

Production stages reset or look wrong

Symptom: Kanban columns are empty or stages do not match what you expect.

What it means: Stages live in slides/.production-board.json — separate from carousel screen files and from project.json.

Fix: Drag cards between columns in Production. If you switched workspaces, open the workspace that owns that project folder.

Export did not download

Symptom: You chose PNG/JPG/PDF but no file appeared.

Fix:

1. Allow the download/save dialog (macOS/Windows may block the first save).
2. On multi-screen decks, Casper downloads a ZIP — check your Downloads folder for <deck-id>.zip.
3. Try exporting again after the preview finishes loading every screen.

See Export for social.

I opened the wrong folder

Symptom: Empty Slides grid, missing decks, or example content only.

Fix: Use Change workspace… and pick the folder where your slides/ directory lives. If you are new, create or choose a dedicated project folder first — see Your folder.

Desktop app — Switch workspace or Open in IDE

On macOS/Windows, the menu bar or tray may offer:

• Switch Workspace… — same as Change workspace… in the sidebar.
• Open in IDE — opens the active folder in Cursor (or your system default) so you can brief the assistant in the same path.

Still stuck?

• Re-read Getting started — install → open folder → brief → review → export.
• Check FAQ for product boundaries (no browser app, no autopost).
• For engine/CLI questions, see the site footer — daily carousel work does not require the terminal.

What’s next