Too many coding agent initializations at home directory

[AnningGao]

Good software! But when I tried to use ping-island on Linux servers, it will first create many coding agent directories in my home directory, e.g. .codex, .qoder, .openclaw, even though I only use one coding agent (Claude). Is it possible to only create directories that are necessary?

[DarkModest]

Hi @erha19,
I'd like to pick up this issue.

[erha19]

@DarkModest assign to you, thanks ~

[erha19]

Rechecked this against PR #255.

Current conclusion: #255 improves the local first-run hook installation path, but it does not fully fix this issue yet for the Linux/remote-server scenario described here.

The remote bootstrap path still builds its hook list from RemoteConnectorManager.remoteManagedHookProfiles(), which currently includes codex-hooks, openclaw-hooks, qoder-hooks, and qoderwork-hooks. During bootstrap it then prepares/writes directories and configs for that full list, so a remote home can still get paths like:

• ~/.codex
• ~/.openclaw
• ~/.qoder
• ~/.qoderwork

There is also existing test coverage in RemoteHookConfigurationTests.testRemoteManagedHookConfigDirectoryPathsResolveUnderRemoteHome() that still asserts those remote paths are present.

So I would keep this issue open until the remote bootstrap profile selection is filtered as well, and the remote hook configuration tests are updated to lock the intended behavior.

[DarkModest]

Hi @erha19 ,
I have no solution to solve this problem. Please assign this issue to somebody else.
I sincerely apologize for inconvenience.

[erha19]

确认当前远程 bootstrap 会把全部 managed client profiles 交给安装流程，因此即使远端没有对应客户端，也可能创建多个 agent 配置目录。这个行为应视为 bug。

本轮没有直接改成“按可执行文件猜测”，因为远端探测目前只覆盖少量基础能力，很多客户端支持自定义安装位置；贸然检测会造成已安装客户端漏配。已补 bug + question，并保留 good first issue / pr welcome。下一步需要确定产品契约：

• 在远程主机设置中由用户显式勾选要安装的集成；或
• 扩展远端 probe，返回每个受支持客户端的可靠发现结果。

确认其中一种后，可以让 bootstrap 只写入选中/已发现的 profile，同时保留非 Ping Island 配置内容。