Run a claimed development instance
Attach a source checkout to a development instance that already has an owner, a known login, and a working model provider.
An unclaimed server is not a development environment. It is a waiting room. This path deliberately reuses an instance that already has a human owner, working credentials, and a configured model provider.
Operator contract
Reuse the claimed default development instance
Being built or reverified. Do not depend on it yet.
- Support scope
- A Nautilo source checkout attached to an existing, claimed default instance with a known owner and working model configuration.
- Risk
- medium
- Topology
- Local Compose infrastructure, Nautilo server, Workbench, and—when requested—the Electron desktop, all using the default instance.
Prerequisites
- A Nautilo source checkout with its dependencies installed.
- Docker and Bun are available on the development machine.
- The default instance is already claimed by a known owner.
- You know the owner login and its model-provider configuration is usable.
Outside this guide
- Fresh packaged installation and first-time server claiming.
- Creating an owner, inventing credentials, or configuring the first model key.
- Remote Droplet deployment or another cloud topology.
- Cloud deployment, backup, recovery, and automatic high-availability operations.
Inspect the target before stopping anything
Run the read-only inventory from the source checkout you intend to test:
bun run dev:list-instancesStop the proven old server process
After the inventory proves the target, run:
bun run server:stop --instance defaultStart the development stack
NAUTILO_PROFILE=source-default bun run dev-stack --instance default --i-know-what-i-am-doing --electron--electron starts the desktop UI. Omit it when you only need the server and
browser Workbench. NAUTILO_PROFILE gives this source-built Electron process
its own local auth, cache, and single-instance lock; it does not create another
Server. Use a cloned named instance
when you deliberately need an isolated database.
Validate the setup state
Leave the stack running and execute this in a second terminal:
bun run dev:setup-status --instance default