executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
moeRoutes Hivemind remote expert and mixture-of-experts workflows, including server setup, custom expert registration, and client-side expert routing.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this route when the task is about hivemind.moe.Server, ModuleBackend, RemoteExpert, RemoteMixtureOfExperts, RemoteSwitchMixtureOfExperts, custom expert registration, or the hivemind-server command.
hivemind.moe.server.Server or background_server.RemoteExpert and the MoE routing layers.declare_experts and get_experts.register_expert_class and custom_module_path.ModuleBackend.hivemind-server console command.dht.collaborative-training.references/api-reference.md for the verified server/client signatures.references/workflows.md for the standard server, client, and custom-expert flows.references/troubleshooting.md when the server cannot publish experts, clients cannot find experts, or a custom module fails to load.../../scripts/check_install.py from the generated skill tree to confirm the installed package and CLI entry points.hivemind-server is the package command for serving experts.background_server(...) is the fastest way to spin up a temporary expert host in tests or small demos.client_mode matters when a client can dial out but should not accept inbound connections.custom_module_path lets the server load extra expert definitions from a Python file.Server.create(...) accepts either explicit expert UIDs or generated patterns.--device cpu.hivemind-server say an expert is missing?"