Start small. Inspect as you go.

Understand the setup you are choosing

DØPEMÜX is a developer/operator workspace, not a hosted turnkey assistant. Package metadata specifies Python 3.11–3.13, version 0.1.0, and an alpha development status. The documented install path uses uv; service-backed paths use Docker.

The primary startup flow launches Claude Code, so the installed client, appropriate authentication, selected providers, and required services matter. Optional tools have additional prerequisites. This website did not execute the installation recipe or validate account access.

Get the source and project environment

git clone https://github.com/DDD-Enterprises/dopemux-mvp
cd dopemux-mvp
uv sync --frozen --extra dev

Run Dopemux from the resulting project environment. If you have not activated that environment, uv run dopemux --help is a way to invoke the installed command through uv; that environment wrapper is guidance, not an installation result measured here.

Inspect the repository’s toolchain and current setup documentation before changing global settings or adding optional integrations.

Preview the managed tool lifecycle

Start by inspecting the managed MCP lifecycle and its read-only plan. Current operating instructions require the fleet to be managed through dopemux mcp, rather than starting it through a separate manual route.

dopemux mcp --help
dopemux mcp start --dry-run --json
dopemux mcp doctor

The start preview reports a lifecycle plan for supported, scoped sidecars. Doctor provides read-only diagnostics. These are source-backed command examples, not commands exercised for this website. Review the plan, project identity, configuration, and required permissions before authorizing a real start, which changes the supported sidecars.

dopemux mcp init generates project configuration and writes files, so select the intended project and inspect its help before using it. A managed MCP start is not whole-stack provisioning. Other required application services, storage, credentials, and providers follow their current component documentation.

The separate dopemux start command launches a development session. Neither startup path proves that every application service is available. Use the component directory and current repository instructions to understand the prerequisites.

Choose the project before initialization

Inspect dopemux --help and the current initialization help in the project environment. The registered init command can write project configuration and hooks. Select the intended project directory deliberately before initializing it.

Keep source edits and configuration changes reviewable. This guide does not silently install shell integration or global client settings.

Inspect a profile, then apply it

dopemux profile list
dopemux profile show <name>
dopemux profile validate <name>
dopemux profile use <name>

Choose a profile present in your installation. Applying it writes settings and uses a configuration-backup path. Validation checks the configuration, not live tool health. The optional automatic restart path is not recommended here because flag compatibility was not established.

Read the detailed profile guide.

Launch the session

dopemux start

The inspected path restores a named or latest local context snapshot, configures the workspace, attempts MCP startup and retrieval bootstrap, applies role instructions, and launches Claude Code. Existing instances may prompt you to select a separate worktree.

Startup attempts do not prove that every dependency is healthy. Retrieval-indexing failure can be non-blocking. Verify the tools and scope that the actual client receives.

Leave a concrete next step

dopemux save --message "Next: verify the failing parser case"
dopemux restore --list

Save and restore require an initialized .dopemux project directory. The snapshot includes Git state, your note, and approximate recent-file hints. It does not restore exact editor state, and the inspected autosave method has no background save thread.

For a separate historical breadcrumb, use a tagged capture note. A snapshot and an activity record serve different jobs.

Inspect trouble before repairing it

dopemux health --detailed
dopemux routing freeflow doctor --offline --json

Service checks and offline routing reports answer different questions. Offline metadata does not prove live provider admission. Repair and cleanup are separate flags with effects, so inspect the finding before authorizing a change.

The separate dopemux cockpit run interface is a static demo, not live control. For current limitations and transport disagreements, see Alpha status.