Work with a thread to follow.

A starting point for work across tools

DØPEMÜX is an operator-facing workspace for development that crosses terminals, assistants, project tools, and context services. The primary inspected startup flow launches Claude Code with workspace setup and saved project context. Other integrations have their own configuration and exposure limits.

Its value is in the connective work: making a session’s starting point more explicit, selecting tools for the task, and keeping enough context around a change to understand the next action.

The site describes an alpha, not a turnkey hosted assistant. The features below distinguish inspected code from experiments and point to their current constraints.

Explore the capabilities

Choose a capability to see its purpose, mechanism, a concrete workflow, and the limits found in the inspected source.

Small actions that leave a clearer trail

Several useful paths do not begin with a large automated run. A manual snapshot can leave a note about an unresolved test. A profile inspection can reveal which tools the next session will see. A project-linked capture note can preserve a finding for later review.

dopemux profile list
dopemux worktrees list
dopemux save --message "Next: verify the failing parser case"
dopemux health --detailed

These examples show source-backed command syntax. Save requires an initialized project; diagnostics depend on local configuration. They were not executed as part of this website’s source research.

Follow a capability into the system behind it

Saved snapshots, structured decisions, historical receipts, and code retrieval are different kinds of context. The software-service directory explains the components behind those jobs. The server directory separates assistant-facing tool transports from backing databases and caches.

For a practical path through the pieces, start with the workflow guides. For the exact qualification language used here, read Alpha status.