Problem
Users with sub-agents (OpenClaw, Hermes, etc.) follow the setup instructions for each agent individually. Each setup overwrites the provider config and clears all routes on the previous agent.
There's no doc or onboarding guidance explaining that Manifest should only be configured on the primary agent. Sub-agents route through it automatically. Users don't know this, so they set up each agent separately and lose their config every time.
Reported multiple times.
What's needed
Docs: a section explaining that setup targets the primary agent only, and sub-agents inherit routing through its proxy endpoint.
UX: a hint in the setup modal when the user already has an agent configured, with a link to the sub-agent doc. Something like "Already set up a primary agent? Sub-agents route through it automatically."
User report
"I fully believe Manifest is a good idea, unfortunately, I am not able to use it simply because it keeps clearing ALL the routes whenever I tried to configure it with a second and third agent."
Problem
Users with sub-agents (OpenClaw, Hermes, etc.) follow the setup instructions for each agent individually. Each setup overwrites the provider config and clears all routes on the previous agent.
There's no doc or onboarding guidance explaining that Manifest should only be configured on the primary agent. Sub-agents route through it automatically. Users don't know this, so they set up each agent separately and lose their config every time.
Reported multiple times.
What's needed
Docs: a section explaining that setup targets the primary agent only, and sub-agents inherit routing through its proxy endpoint.
UX: a hint in the setup modal when the user already has an agent configured, with a link to the sub-agent doc. Something like "Already set up a primary agent? Sub-agents route through it automatically."
User report