Skip to main content
Start here when a Capsule command or app does not behave the way you expect.

capsule command not found

Install cpsl in the active environment:
or:
Then verify:
If which capsule points at the wrong environment, activate the virtual environment you installed into.

capsule serve says you are not authenticated

Run:
capsule login authenticates you as the builder. It is required for serve, deploy, and workspace resource commands.

Secret missing in the runtime

Create the workspace secret:
Declare it on the app:
For local-only testing, also export the environment variable before capsule serve.

Import error after deploy

Make sure the dependency is in the runtime image:
Installing a package locally is not enough. The Capsule runtime installs packages from cpsl.Image(...).

Page does not show in the sidebar

Check that the page is registered before the module finishes importing:
For React pages, check the component path:

Data handler returns empty integration state

If a page needs user credentials, gate it and read integrations from RequestContext.
The user still needs to connect the integration in the hosted app.

Filesystem path is missing

Create the filesystem and mount it:
Then create subdirectories inside the runtime before writing:

Local and hosted behavior differ

Check SDK And Runtime Versions. Hosted runtimes can use the platform-pinned SDK version even if your local virtual environment has a different cpsl installed.