What is Dopemux?
Is it one AI assistant?
It is an operator-facing workspace and CLI coordinating several systems. The inspected primary startup path launches Claude Code. It is not one universal autonomous agent or a replacement for every PM, memory, and execution system.
Is there a hosted account or paid plan?
This site describes the open-source local alpha and its software components. It does not offer signup, commercial hosting, consulting, or a paid subscription. Model or research providers can have their own account and billing requirements.
What license is declared?
The project metadata declares MIT. Read the repository license for its terms.
What does saved context actually preserve?
Will it restore every file and cursor?
The local snapshot saves a note, Git state, and approximate recent-file hints. Exact editor restoration is a placeholder, cursor values default to the file beginning, and several richer context fields are placeholders. Read Saved context for the inspected details.
Does it autosave every 30 seconds?
The inspected autosave method changes a flag and prints a message; it does not start a background saving thread. Use explicit saves.
Does one system own all memory?
No. ConPort handles structured context and decisions, dope-memory holds chronicle history, and dope-context provides derived retrieval. PM metadata and workflow transitions have separate owners too.
Will every tool work with my assistant?
Are all integrations available to every client?
No universal access is established. Client exposure and profiles differ, optional integrations need setup, and some declarations remain planned or gated. Catalog entries are not runtime receipts.
Is a database also an MCP server?
Not by default. Qdrant, PostgreSQL, and Redis back other services. A client typically reaches them indirectly through an exposed tool or application API. See MCP servers and infrastructure.
Does a profile validate live health?
Profile validation checks configuration. Applying a profile writes settings; you still need to inspect the connected services and the client’s actual tool exposure.
What should I expect during setup?
Does one start command launch everything?
The documented quick start separates Docker service startup from dopemux start. Required dependencies, local overrides, installed clients, and authentication still matter.
Do separate worktrees isolate the entire stack?
They separate local branch files. They do not prove isolation of shared credentials, databases, event streams, ports, or provider effects.
Does offline routing guarantee capacity or free inference?
No. It reports policy/configuration and quota metadata. Live provider admission, billing, and actual model identity require separate evidence.
Are the attention tools and cockpit live?
Does attention support treat ADHD?
No clinical claim is supported. Optional heuristics and pacing suggestions are experimental; reliable live input ingestion into the inspected local monitor was not established.
Is the terminal cockpit a live control dashboard?
The separate dopemux cockpit run interface is explicitly a static demo with no writes. Package-derived render snapshots also require explicit inputs. The operational dopemux start path is separate.
Is this production-ready?
The package is alpha. This site reports inspected source and configuration, with limits per feature. It does not establish production readiness or full-stack reliability. See Alpha status.
Source evidence
Inspected source at the pinned reference revision. Source presence does not establish runtime health.