ADHD Progress Hub is designed to provide coding agents (such as Cursor, Codex, Claude Code, etc.) with a self-hosted "source of truth" for tracking abandoned plans, migrations, and setups. It is inspired by claude-adhd, and the project itself is tool-agnostic. It exposes capabilities through MCP over Streamable HTTP (with optional local stdio transport) and a REST interface, and optionally integrates OpenClaw notifications and a local conversation-record indexer (which only generates summaries).
Main uses and capabilities:
- Manage Threads (work items): divided into open / blocked / done / dismissed statuses.
- Maintain a Progress wiki: record progress in data/wiki/projects/<slug>/PROGRESS.md.
- Overlap check: determine whether work that is already half done is about to be duplicated.
- Reminders: support once / session / daily / random frequencies.
- OpenClaw bridge (optional): provides chat reminders and memory sync when away from the IDE.
Usage and deployment: For a persistent server installation, Docker Compose with a published image is recommended. Running from source with uv and local MCP over stdio mode are also supported (using only MCP tools, without starting the REST API, dashboard, or background scheduler). Published images are located at ghcr.io/uniskela/adhd-hub:latest or a specified X.Y.Z tag. The repository includes a Compose file that can build the current checkout. MCP endpoints: use http://<host>:8787/mcp for persistent/shared transport; use adhd-hub mcp-stdio for local subprocess transport. REST documentation is at http://<host>:8787/docs, and the UI is at http://<host>:8787/ui/.
Applicable scenarios: Continue tasks across multiple clients (Cursor Cloud, Dev LXC, Windows, etc.) during work such as Proxmox migrations, homelab setup, or refactoring, to avoid forgetting half-finished conversations. Suitable for developers who want to centrally manage scattered coding agent progress.
Limitations and notes:
- The default storage is SQLite + markdown wiki, with data located in the data/ directory.
- An authentication token (bearer token) must be set; /ui/ supports a separate dashboard password; browser sessions use a 12-hour HttpOnly SameSite=Strict cookie, while CLI/MCP use bearer authentication.
- Remote access requires a reverse proxy or tunnel and must be configured with HTTPS; it is recommended to bind only to 127.0.0.1 or Tailscale, and not expose it publicly.
- Environment variable changes require a restart; Web UI changes take effect immediately.
- For detailed installation guides, environment variable reference, OpenClaw setup, forge sync, etc., please refer to the official documentation.
