# Agent Client path sync fix **State**: The current diagnosis is that Obsidian Agent Client broke because its synced settings file stored machine-specific absolute paths inside `.obsidian/plugins/agent-client/data.json`. On this machine, the working ACP wrappers still exist at the system level, but the synced config had been overwritten to use a nonexistent vault-local `.obsidian/bin/` path. The config was changed back to portable command names, `claude-agent-acp` and `codex-acp`, and `nodePath` was cleared so the plugin can resolve commands through the login shell on each machine. **Decided**: - Treat the failure as a sync/config portability problem rather than an Agent Client code bug. - Prefer portable command names in the plugin settings over absolute machine-specific paths. - Leave `nodePath` blank unless a machine genuinely needs an override. **Rejected**: - Recreating a vault-local `.obsidian/bin/` wrapper setup, because that would preserve the brittle cross-machine path problem. - Treating the missing command as a missing installation on this desktop, because `claude-agent-acp` and `codex-acp` are present in `/opt/homebrew/bin`. **Open**: - Reload the `agent-client` plugin or restart Obsidian and verify that new Claude/Codex chats launch cleanly. - Check the laptop with `which claude-agent-acp` and `which codex-acp` to confirm the portable config resolves there too. - If the laptop lacks one of the wrappers, install the missing global package rather than reintroducing hardcoded synced paths.