Hades Backend Plugin

A standalone, opt-in, workspace-scoped project-knowledge plugin for Hades. It exposes MCP queries and explicit hades backend operations without adding background synchronization, memory integration, jobs, inbox handling, or lifecycle hooks. It is not a memory provider: memory.provider remains for Holographic, Supermemory, and other personal-memory providers.

Install, update, disable, and remove the plugin through the normal plugin lifecycle. Installation, update, enable, disable, and removal do not pair a project or modify unrelated configuration:

hades plugins install titagram/hades-backend-plugin --enable
hades plugins update hades-backend
hades plugins disable hades-backend
hades plugins remove hades-backend

hades update updates Hades core only. It does not install, update, pair, reconfigure, or synchronize this plugin.

Restart the affected Hades CLI, TUI, Desktop, or gateway after installing or enabling the plugin so its backend command is discovered.

Commands

hades backend set-token --url URL --project-id ID [--workspace PATH] [--token-stdin]
hades backend status [--json] [--live]
hades backend sync [--workspace PATH] [--domain docs|graph|source_index|evidence_metadata] [--dry-run] [--json]

Pair from the root of the project being linked. Copy a project token separately from the Backend dashboard; set-token collects it through a masked prompt. Never include it in a command, slash-command argument, or chat message. For non-interactive automation, --token-stdin is the only supported token input path and keeps the token out of argv.

A successful explicit set-token pairing idempotently enables this plugin's scoped MCP server in the active profile while preserving the rest of its configuration. Restart the affected CLI, TUI, Desktop, or gateway after that pairing before using MCP queries. Cancelling or failing pairing leaves MCP configuration unchanged.

One profile can bind many project roots, each to a distinct derived credential. There is no global/default Backend project and no newest-project fallback. status is local by default. sync is explicit, linked-workspace scoped, and never runs during pairing, startup, or ordinary conversation turns. It covers only project docs, source/index artifacts, graph data, and submitted evidence; it never syncs personal memory, jobs, inbox, logbook, cron, or user context.