Extra tools
Shared project requirements belong in .devcapsule/devcapsule.toml. Personal
tools that only you need—such as a cloud CLI, a database client, or a language
toolchain you are evaluating—belong under /opt/xtras inside the capsule:
/opt/xtrasis writable by the capsule user withoutsudo./opt/xtrasis a symlink to/home/devcapsule/xtrasinside the checkout's persistenthomedirectory, so everything installed there survives stopping, removing, recreating, or upgrading the container./opt/xtras/binis prepended toPATHfor the IDE, login shells, and coding agents.
Install a tool into its own subdirectory under /opt/xtras following the
vendor's user-space instructions, then link its executable into
/opt/xtras/bin:
# Replace my-tool with the directory and executable you installed.
ln -s /opt/xtras/my-tool/bin/my-tool /opt/xtras/bin/my-tool
Because /opt/xtras lives inside the checkout's home slot, each checkout
gets its own /opt/xtras under your active configuration home
unless you rebind home with devcapsule project config bind home host-directory:PATH or devcapsule project state adopt --from PATH home. You
manage installation and updates yourself: files in /opt/xtras are not
recorded in the project lock, are not copied to other machines, and are not
verified against future base images. devcapsule project info lists the
xtras entry alongside its host backing directory (<home backing>/xtras).