Open source · Alpha v0.1.0

Keep the
thread.

Development moves between tools.
DØPEMÜX is built to help you carry the context, coordinate the handoff, and see who owns what.

Read the quick start Explore the code

An operator workspace for your development environment.

One task. Distinct lanes.Illustrative workflow

~/example-workspace

Pick up the checkout fix.

A sample task, from context to handoff.

Local startupDopemux CLI

workspace entrypoint

Context & retrievalConPort / dope-context

decisions + references

Project workflowPM / task-orchestrator

scope + next action

Execution handoffExternal dopetask

work changes hands

Chronicle & receiptsdope-memory

historical record

Resume with a starting point.

The sample task brings its last decision and relevant code references into view. Retrieved context stays linked to its source.

last decisionPreserve the retry limit.

Conceptual example. No live services or task execution.

Look under the surface

A workspace with
more than one layer.

Follow a capability into the components behind it, understand the tradeoffs, and decide what belongs in your setup.

Capabilities

Context, workspaces, profiles & handoffs

Explore the pieces that carry a development session forward.

Software services

Meet the components.

Structured knowledge, historical receipts, retrieval, coordination, and the infrastructure beneath them.

Connections

Tools with a clear role.

Understand assistant integrations, task profiles, optional providers, and their current limits.

Alpha, openly

Know what the source establishes.

Code, configuration, experiments, and unresolved boundaries are different signals.

Context has a source.Work has an owner.A handoff has a history.

The space between tools

The task changed tabs.
Did the context follow?

A terminal, an assistant, a project board, a new session. The work is connected. The systems each hold a different part of the story.

Find your way back in.

Session restoration provides a starting point. Structured decisions and code retrieval help you recover the surrounding context.

Coordinate across tools.

The CLI brings startup, MCP coordination, and execution handoff into an operator-facing workspace.

Keep ownership visible.

PM state, context, retrieval, and historical receipts have distinct authorities. A useful view should preserve those differences.

Built around boundaries

A control surface.
Clear sources of truth.

DØPEMÜX coordinates a split-authority workflow. Each system keeps its own job, while the operator keeps the wider picture.

Read the system boundaries

Project state: Metadata, transitions, and decisions have separate owners.
Retrieved context: A derived view into code and docs, with source truth kept distinct.
Bridge routing: Connects systems; routing does not transfer authority.
Historical receipts: A chronicle of work, distinct from current project status.

For the hands-on curious

Start in your
own workspace.

This is an alpha. Expect evolving interfaces, configuration, and rough edges. The repository is the place to start, inspect, and contribute.

Read the quick start

Get the source

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

Then follow the guide for managed tool setup and dopemux start. Tool lifecycle, application services, and session startup are separate steps.

Python 3.11–3.13uvDocker for services

Read the source.
Keep your bearings.

GitHub repository Documentation Issues & contributions

Keep thethread.