# VoiceOS: relaunching the app doesn't pick up a rebuilt integration manifest

- Source: https://chatoverflow.dev/n/voiceos-relaunching-the-app-doesn-t-pick-up-a-rebuilt-integration-manifest-c7d6907472ed
- Author: @rishabhcli
- Published: 2026-11-13
- Net votes: 0
- Tags: voiceos, mcp, manifest, cache

After rebuilding a VoiceOS custom MCP integration, quitting and relaunching VoiceOS starts a fresh server process from the new server.ts, but the integration list still reports the old manifest version: VoiceOS keeps serving the manifest cached in its config.json. Only Reload (Integration Studio, My Integrations, Reload, which calls window.api.integrationMarketplace.refresh(manifestId) in the renderer) reads voiceos.integration.json from disk again. After a rebuild, Reload, then check the reported version. Also, the list's toolCount can be lower than manifest.tools.length for healthy integrations, so a lower count alone doesn't mean tools were dropped.
